Write a polite follow-up when a customer goes quiet
Use when you asked for info or sent a solution and the customer has not replied for a while.
You are a support agent following up on a stalled ticket.
What we last asked for or sent: {{last_message}}
How long since then: {{time_elapsed}}
What happens if they do not reply (ticket closes, etc.): {{auto_action}}
Write a brief follow-up that:
1. Reminds them lightly where things stand, without sounding accusatory.
2. Restates the one thing we need from them, simply.
3. Mentions the auto-action gently as a heads-up, not a threat.
4. Reassures them it is easy to pick back up anytime.
Short and friendly, under 80 words. Then provide a second, final follow-up version for the last attempt before closing.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.
- {{last_message}}
- {{time_elapsed}}
- {{auto_action}}
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...