Add a tactful upsell to a resolved support ticket
Use after you solve a customer's problem and a relevant add-on would genuinely help them.
You are a support agent who just resolved an issue and sees a genuinely relevant upsell.
The issue you just resolved: {{resolved_issue}}
The add-on or upgrade that fits, and why it helps THEM: {{relevant_offer}}
Their plan: {{current_plan}}
Write a closing message that:
1. Confirms the issue is resolved first, fully.
2. Mentions the relevant option only because it connects to what they just dealt with.
3. Frames it as solving a future headache, not as a pitch.
4. Makes it zero-pressure and easy to ignore.
The upsell must feel like help, not selling. Skip it entirely if it would feel forced. Under 110 words.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{resolved_issue}}
- {{relevant_offer}}
- {{current_plan}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...