When someone is angry, the first thing they are testing is not whether you can fix the problem. It is whether you understood it. Most replies fail that test in the opening sentence, usually by explaining, apologising generically, or asking for an order number.
The method below is four moves in a fixed order, and the order is the whole thing. Get the sequence right and most angry conversations come down within two messages. Get it wrong and you spend six. If what you need is the wording rather than the method, the complaint response templates cover twenty-five specific situations.
The four moves, in order
1. Reflect the specific thing back. Not "I understand your frustration." Name what happened. *"Your installation was booked for Tuesday morning, nobody arrived, and you took the day off work for it."* This is the single highest-value sentence in the entire exchange, because it proves you read the message.
2. Validate the feeling, separately from the facts. *"That is a wasted day and I would be angry too."* You can say this before you know whose fault anything is. You are agreeing that the experience was bad, not that you caused it.
3. Take ownership of the next step, with a name and a time. Not "we will look into this." *"I am handling this personally and you will have an answer from me by 2pm today."* Anger thrives on uncertainty about what happens next.
4. Only now, solve it. The remedy lands completely differently after steps one to three than it does instead of them.
Most people are not angry about the problem. They are angry about having to chase it. Steps one to three remove the chasing.
What never to say
Each of these is common, and each one reliably makes things worse.
| Do not say | Why it lands badly | Say instead |
|---|---|---|
| "Calm down" | Instructs them about their emotions. Guarantees escalation. | "I can hear how annoying this has been." |
| "Unfortunately, our policy states..." | Policy as the first word reads as a wall. | "Here is what I can do, and here is the limit I am working inside." |
| "As I mentioned in my previous email..." | Scores a point. Wins nothing. | Just restate it, without the scoreboard. |
| "I'm sorry you feel that way" | A non-apology, widely recognised as one. | "I'm sorry this happened" or "I'm sorry you have been left waiting." |
| "That's not our department" | Makes your org chart their problem. | "I'll find the right person and stay on it until they reply." |
| "You should have..." | Assigns blame to someone already upset. | "The order shows address X, which is why it went there. Here's how we fix it." |
| "We never received that" | Flatly contradicts them. | "I can't find it on my side, which may be our fault. Can you resend it?" |
| "Please bear with us" | Vague, open-ended waiting. | "I'll have an answer by [time]." |
| Any use of "but" after an apology | Deletes the apology that preceded it. | Full stop. Then a new sentence. |
Acknowledgement is not liability
This is where most teams freeze, and the freezing produces the vague wording that infuriates people.
- •Empathy describes their experience. *"I'm sorry you've been waiting three days for a reply."* Always available, always safe.
- •Apology for conduct describes yours. *"I'm sorry we missed your appointment."* Use it when it is true.
- •Admission of liability accepts legal responsibility and a consequence. *"We are responsible for the damage to your property."*
Only the third needs care, and only in matters involving injury, property damage, insurance, regulated services or anything heading towards a formal dispute. For the ordinary run of late orders and bad service, teams hedge far more than the risk warrants, and the hedging itself is what sounds evasive.
If you are genuinely unsure, the safe construction is: acknowledge the experience, commit to establishing the facts, give a date. *"That should not have happened to you. I'm establishing exactly what went wrong and I'll have the answer to you by Thursday."*
The structure, written out
Four moves, four sentences, in order:
[Specific thing that happened, in their words.] [That is genuinely bad / I would be angry too.] [I am doing X, personally, by Y time.] [Here is the remedy.]
Everything below is that structure in a different register.
Worked examples by channel
Email: a furious first message
They wrote: *"This is the THIRD time I've been promised a callback. Absolutely appalling service. I want someone to actually do their job."*
Hi [Name],
>
Three promised callbacks and three times nobody rang. That is a fair description of appalling and I am not going to argue with it.
>
I am picking this up myself rather than putting you back in a queue. Your issue is [restate the underlying issue in one line, so they know it did not get lost between the three attempts].
>
I will call you today between [time] and [time] on [number]. If that window does not work, reply with one that does and I will keep to it. If I do not ring, [escalation route] and you have my word that is the last promise anyone makes you on this.
>
[Name]
Why it works: it agrees with the strongest word in their message rather than softening it, and it replaces three vague promises with one specific one plus a fallback if that fails too.
Email: angry but factually wrong
They wrote: *"You charged me twice and nobody will refund it. This is theft."*
Hi [Name],
>
Being charged twice with nobody fixing it would be enraging, so let me go through exactly what I can see on the account.
>
There are two entries on [date] for [amount]. The first is the charge for order [number]. The second is a pre-authorisation your bank places and releases, which is why it usually disappears from the statement within [period] rather than appearing as a refund.
>
I may be wrong about that, so: if it is still showing after [date], send me a screenshot and I will refund [amount] from our side and reclaim it myself rather than leave you out of pocket while we work it out.
>
[Name]
Why it works: it validates the feeling in the first line, explains without using the word "actually", admits it might be wrong, and gives them an unconditional route out. Nobody is told they were mistaken.
Live chat: the pace is different
In chat the customer is watching the typing indicator. Silence reads as being ignored, so acknowledge before you investigate.
Them: this is ridiculous, I've been waiting 20 minutes and the last person just disconnected
>
You: Twenty minutes and a dropped chat - sorry, that is a bad run. I'm here and I'm not going anywhere.
>
You: Give me two minutes to read what happened before you got to me, so you don't have to type it all again. I'll come straight back.
>
*(within two minutes)*
>
You: Right, I've got it: [one-line summary]. Here's what I can do...
Why it works: the promise to read the history, and then actually reading it, is the opposite of what they expect based on the last twenty minutes.
WhatsApp: short lines, fast, human
The method is identical. The format is not. No greeting paragraph, no sign-off, no three-sentence blocks.
That's three days with no reply - sorry, that's on us.
>
I've got your order [number] in front of me now.
>
[Specific action], done today, with you by [date].
>
I'll message you myself when it's moved, you won't need to chase.
Why it works: the last line is the one that matters. On a channel people use to chase, promising they will not have to chase is the de-escalation.
Public reply when they have gone to social
Reply once in public, briefly, then move. Other people are reading.
[Name], three missed callbacks is not acceptable and I'd like to sort it today. I've sent you a DM so we can get your details without posting them here. Anyone else affected by [issue], it's fixed as of [date].
Then come back and close the loop publicly when it is resolved. Responding to reviews and public feedback covers that in full. A public thread that ends with "we've DMed you" and nothing else looks like it was quietly dropped.
Harder situations
They are angry at a previous colleague. Do not defend and do not throw the colleague under a bus. *"I can't undo how that went, and I'm not going to make excuses for it. What I can do is make sure this one goes differently."*
They are repeating themselves and will not move on. They usually do not feel heard yet. Try a summary and a check: *"Let me make sure I have all of it: [list every point they have raised]. Have I missed anything?"* Asking what you missed, rather than moving to the fix, is often what ends the loop.
They are threatening a review or legal action. Do not react to the threat, in either direction. Acknowledge it neutrally once and carry on solving: *"That's your right. Separately from that, here's what I can do today."* Never offer a remedy in exchange for a review being withheld.
They are abusive, not just angry. Draw one clear line, once, and mean it. *"I want to help and I'll keep working on this. I'm not able to continue if the messages stay personal. Shall we carry on?"* Then follow through. A boundary you do not enforce teaches the opposite of the lesson.
You are the one getting annoyed. Write the reply, send it nowhere, wait ten minutes, then reread it looking only for scoreboard phrases: "as I said", "actually", "as previously advised". Delete those and it is usually fine.
When to hand it to a human, and when to hand it on
If any part of your first-line support is automated, these are the signals to route to a person immediately rather than offering another article: profanity or capitals, the third message in one thread, the words "manager", "complaint", "legal", "refund" alongside frustration, or any repeated question the automation has already failed to answer once. An automated reply that arrives after a customer has already said they are angry is itself an escalation event. Self-service is excellent at the first question and poor at the fourth.
For handing over to a colleague: brief them before the customer reaches them. The most reliable way to restart an argument you had just calmed is to make someone retell it to a more senior person who has not read the thread.
Making fewer customers angry in the first place
Most anger in support queues is not caused by the original fault. It is caused by the chase: no acknowledgement, no date, no way to check the status without asking a human.
Three things reduce the volume more than better wording does. Acknowledge every inbound message automatically, with a real timeframe. Publish the answers to the questions people chase most, so checking does not require a conversation. And when you say you will come back by Thursday, come back by Thursday, even if the answer is "still working on it".
If the same frustration keeps arriving, giving customers one structured place to find the answer themselves removes the wait that caused it, which is a more durable fix than a better apology.
Frequently asked questions
What do you say to an angry customer first?
Name the specific thing that happened, in their words, before anything else. Not "I understand your frustration" but "your delivery was due Tuesday and it is Friday." Everything else works better after that sentence and worse without it.
Should I apologise to an angry customer even if we did nothing wrong?
Apologise for the experience, not for a fault you did not commit. "I'm sorry you've been left waiting" is true regardless of cause. Save "we got this wrong" for when you did.
How do I calm an angry customer down over the phone?
Let them finish without interrupting, even if the first thirty seconds are hard to listen to. Then summarise what you heard and check you got it right. The summary is what does the work. After that, one concrete commitment with a time attached.
What if the angry customer is wrong?
Explain without the word "actually", admit you might be wrong, and give them a route out that does not require them to concede anything. Most people stop arguing when they are no longer being asked to lose.
Should an automated system handle angry customers?
It should recognise them and get out of the way. Detecting frustration and routing to a person quickly is useful. Trying to resolve an angry customer with an article is how a complaint becomes a review.
When should I escalate to a manager?
When the customer asks, when it is the third contact on one issue, when the remedy exceeds your discretion, when there is a legal or safety dimension, or when you notice yourself writing defensively.
Generate your FAQ page
Paste your product description and get a complete FAQ page - free, no sign-up.
Try Answrii free →