Calm, empathetic reply to an angry customer
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Reply to a customer in their own language with natural phrasing, the right level of formality and a back-translation so you can check it.
Write a customer support reply in {{language}}.
The customer's message (in their language or English):
{{customer_message}}
What the reply must say (in English):
{{reply_points}}
Company: {{company}}
Formality: {{formality}}
Channel: {{channel}}
Requirements:
- Write natively in {{language}}, not as a literal translation. Use the greeting, closing, honorifics and level of politeness a good local support team would use in this channel.
- Keep names, product terms, prices and dates exact. Use local conventions for dates, times and currency formatting only if the reply points ask for conversion.
- Do not add promises, facts or apologies beyond the points given.
- Keep it as short as the English would be.
Output:
1. The reply in {{language}}.
2. An English back-translation, so I can check meaning.
3. Any cultural or phrasing notes that matter (for example, a phrase deliberately softened or a word with two possible meanings).
4. If the customer wrote in a different language than {{language}}, mention it.Asking for a back-translation lets you verify meaning even if you do not speak the language, and the 'no extra promises' rule stops translation drift. For sensitive cases, have a native speaker review.
Licensed CC0 (public domain) Version 1 · history
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Say no to a refund or policy-exception request clearly and kindly, explain the reason, and offer real alternatives so the customer feels respected.
Respond to a customer who wants to cancel with an honest, respectful save attempt that addresses their real reason and makes leaving easy.
Reply to an unhappy customer with a sincere, specific apology and a clear remedy, not canned phrases.
Condense a long, messy ticket history into a crisp escalation note with impact, timeline, what has been tried and what you need.
Analyze a batch of tickets to find top issue themes, root causes, deflection opportunities and product or documentation fixes worth making.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.