Skip to content
iMessage APIs
Operations6 min read

When a customer replies angry

A complaint by email gives you a day to compose yourself. A complaint by text feels like it needs an answer in ninety seconds, and that pressure is where businesses make it worse.

Open a two-way channel and you will get complaints on it. That is not a failure of the channel — it is the channel working. A customer who tells you is a customer you can keep; the silent ones just leave.

But messaging changes the dynamics of a complaint in three ways, and each one is a trap.

The three traps

PressureThe mistake it produces
It feels urgentReplying in 30 seconds with something defensive
It is short-formCompressing an explanation into something that reads as dismissive
It is a threadA back-and-forth that escalates over six messages

The playbook

1. Acknowledge fast, resolve slow

Speed matters, but what needs to be fast is the acknowledgement, not the answer. A holding reply within a few minutes removes the urgency without committing you to anything.

Bell HVAC

iMessage

Your guy left the filter cover off and there's dust all over the hallway. Not impressed.

That's not okay and I'm sorry. Let me find out what happened — can I call you in the next 20 minutes?

yes please

2. Get off the thread

The single most useful move. A complaint resolved by voice within the hour usually ends the matter; the same complaint handled across nine text messages usually does not. Text is a poor medium for tone, and tone is most of what a complaint is about.

Ask, do not just call

'Can I call you?' respects that they chose to text. Calling unannounced after an angry message reads as escalation, and some people text specifically because they do not want to talk.

3. Never let automation touch it

If you run an AI agent on the line, anger is a hard escalation trigger. An agent handling a complaint correctly is not a bet worth taking, and a customer who realises they were being placated by software has moved from a service problem to a trust problem. This is the firmest of the agent handoff rules.

What to say and what not to

  • Do apologise for the experience before you know whose fault it is. It costs nothing and de-escalates immediately.
  • Do name a next step with a time attached. Vagueness reads as a brush-off.
  • Do not explain the cause in the first reply. It reads as excuse-making even when it is accurate.
  • Do not mention policy. Nobody has ever been calmed by a policy.
  • Do not send a review request to this customer. Suppress it — automatically, not by remembering.

That last one is an integration job rather than a discipline job. A flagged service issue should suppress the review play automatically, because the person who remembers is not the person the automation asks. See connecting iMessage to your CRM.

After it is resolved

One message, a few days later, confirming it stayed fixed. It is short, it costs nothing, and it converts a recovered complaint into the strongest loyalty you can buy.

Bell HVAC

iMessage

Hi Marcus — just checking the system's been running right since Thursday?

all good, and thanks for sorting it out so fast

customer serviceescalationhandoff