A customer writes an angry message on a Friday afternoon. The order was wrong, the replacement was late and nobody replied to the last email.
The agent replies with the returns policy, an apology for any inconvenience caused, and a request for the order number that appeared in the customer's first message.
The next message is considerably angrier and the customer has now written a review. The underlying problem was solvable in one paragraph. The reply was what turned it into a complaint.
Script 1: the opening line that works
Start with the specific thing. You ordered a blue one, we sent grey, and then the replacement did not arrive. Naming it exactly proves the message was read.
Script 2: the apology that lands
Apologise for the actual failure rather than for any inconvenience. Vague apologies read as a formula and specific ones read as a person.
Script 3: state what happens next, with a time
I am sending a replacement today and it will reach you by Wednesday. Certainty is what calms somebody down, far more than sympathy does.
Script 4: what to do when the answer is no
Say no clearly, give the reason once, and offer whatever is actually available. Softening a refusal into ambiguity produces three more messages.
Script 5: when the customer is factually wrong
Correct it without making them wrong. Here is what the record shows, and here is what I can do about it, rather than a correction followed by a refusal.
Script 6: when the customer is abusive
A clear, calm statement that the team will continue helping and that the conversation needs to stay civil. Agents need explicit permission to send this.
Script 7: the second reply on the same thread
Acknowledge that this is the second time. Anybody who has had to write twice is angrier about that than about the original problem.
Rule 1: escalate when the customer asks
Immediately and without resistance. Making somebody argue for a manager is the single fastest way to lose them permanently.
Rule 2: escalate when the resolution needs authority
Rather than letting an agent negotiate toward something they cannot actually approve, which is the ground in escalation rules that people actually follow.
Rule 3: escalate anything legal, safety related or about a vulnerable person
Without judgement and without delay. Agents should never have to decide whether something qualifies.
Rule 4: escalate after two exchanges without progress
A thread that has gone back and forth twice is not going to resolve on the third attempt from the same person.
Rule 5: never make the customer repeat themselves
An escalation that arrives without the history is worse than no escalation, because it resets the conversation and the anger with it.
Rule 6: set the tone rules as examples, not adjectives
Three good replies and three poor ones, which is the practical version of tone and brand voice questions from support leads.
Handle the routine volume so agents have time for the difficult ones
An assistant that answers the repetitive questions instantly, recognises frustration and hands over immediately with the full conversation attached leaves a team the time and the attention that a Friday afternoon complaint actually deserves. Draft replies with the ai reply generator. The volume problem is set out in the same twenty questions every single day and the delay cost in the hidden cost of slow support replies and how. See features, start at try, and the sector view sits under small business.