Respond to an angry customer complaint
Turn a complaint and the facts of the case into a reply that acknowledges the problem, states what happened and offers a concrete remedy, no hedging.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Requiring the reply to name the specific problem instead of a generic apology forces the model to demonstrate it actually read the complaint, which is what a frustrated customer is checking for first.
- →Explicitly banning weasel words like "mistakes were made" targets the exact pattern that makes customer-service replies feel evasive, which a plain instruction like "be empathetic" does not prevent.
- →The instruction to admit an unknown cause rather than imply one closes off the model's tendency to smooth over a gap in the facts with a plausible-sounding but unverified explanation.
Part by part
- acknowledge the specific problem they described
- Specificity is what proves the message was read. A generic apology signals a template, which is itself the second complaint.
- state plainly what happened based only on the facts given
- Confines the explanation to what is known. An invented cause in a customer reply is a commitment you may have to retract publicly.
- Avoid weasel words and passive voice that obscure who did what
- The instruction that changes the tone most. Passive constructions are how a reply avoids responsibility while appearing to accept it.
- say plainly that we're still looking into the cause
- The honest alternative to a plausible explanation. Customers accept not-yet-known far better than they accept being told something that turns out to be wrong.
Common mistakes
Write an apology to an angry customer.With no facts, the reply apologises for an unspecified inconvenience and promises unspecified improvement. It reads as automated, which usually escalates rather than resolves.
Make this reply sound more empathetic.Empathy added as tone produces phrases like "we understand your frustration" standing in for actually addressing the problem. Specificity reads as care; sentiment words read as a script.
Write a reply that avoids admitting fault.Produces exactly the passive, evasive register this prompt exists to prevent. Customers detect it reliably, and it converts a service failure into a trust failure.
Questions
Why does passive voice matter so much here?
Because "an error occurred" and "we sent the wrong file" describe the same event and read completely differently. The passive form is how a reply avoids saying who is responsible while appearing to take responsibility.
What if we do not know the cause yet?
Say that. A stated unknown with a commitment to follow up holds up; a plausible cause that turns out to be wrong means a second, worse message correcting the first.
Should the remedy be offered before it is approved?
No — the prompt takes the remedy as an input for that reason. A reply promising something the business has not agreed to creates an obligation someone else has to honour or withdraw.
Does the prevention line always belong?
Only when the facts support it. "We have added a check" is powerful when true and hollow when it is boilerplate, and customers who complain more than once notice which one they were given.