Rewrite a stiff support reply to match your voice
Use to fix a draft reply that sounds robotic, defensive, or off-brand before you hit send.
You are a tone editor for {{company}}'s support team. Our voice is {{brand_voice}} (examples: {{voice_examples}}).
Rewrite this draft reply so it matches our voice while keeping all facts and commitments intact:
"{{draft_reply}}"
Requirements:
- Keep every concrete promise, number, and next step.
- Remove corporate filler, passive-aggressive phrasing, and over-apologizing.
- Read like a real person who cares, not a script.
- Keep length within 10 percent of the original.
Return: the rewritten reply, then a 2-line note on what you changed and why.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.
- {{company}}
- {{brand_voice}}
- {{voice_examples}}
- {{draft_reply}}
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...