SUPPORT WRITING GUIDE
How to reply to an angry customer without sounding defensive
Replace blame and rebukes with a clear answer to the customer’s concern, then use Vellix to review the wording while keeping the response decision yours.
Two fictional defensive replies, rewritten
Before
As it clearly says on the product page, there are four glasses in the box.
After
There are four glasses in the box.
Fictional context: the customer is annoyed that earlier replies sent links instead of answering the quantity question. Four glasses is the verified answer for this exercise. Remove the rebuke and give that answer directly.
Before
The guide works fine. You must be opening it incorrectly.
After
You can’t open the guide you paid for. What error message appears when you open the file?
Fictional context: a customer says the purchased guide will not open. The cause is unknown and no error message has been provided. Acknowledge the reported problem and ask for the missing diagnostic detail. Check the thread first so you do not request it twice. These examples are not customer messages or measured Vellix outputs.
Identify the concern you need to answer
Before editing the tone, write a short private summary of what the customer needs. In the first example, they need the quantity in the box. In the second, they need help opening a file they paid for. Each reply now has a specific job.
Intercom’s published support guidance recommends staying patient and calm and avoiding assumptions about a customer’s knowledge. Use that as a writing principle when choosing your response. It is not a prediction of how a customer will react.
Start with the answer you have, or acknowledge the specific problem and give the next action you can take. A general line about understanding frustration should not replace the answer.
Remove the argument from the draft
Read for phrases such as “as I already explained”, “you obviously” or “you must have”. Check whether they add useful information or simply criticize the customer. In the examples above, the product-page rebuke and the unverified blame can both go.
Keep any explanation the customer needs. If an earlier answer matters, state the relevant detail again in plain language. You can refer to a previous message without commenting on whether the customer should have understood it.
If your team has confirmed a mistake, state it and the approved next step. Do not use a neutral-sounding sentence to avoid an explanation the customer is owed.
Review the answer and the tone separately
Intercom’s PREACH framework treats answer accuracy and tone as separate review areas. Its tone guidance includes empathy suited to the situation and language that sounds human.
The file example acknowledges the customer’s reported experience. It leaves the cause open. Before sending a reply like this, check what the customer already provided and what your team can actually investigate.
Read the draft aloud. Check whether the reply gives a clear answer or next action, whether any sentence sounds like a rebuke, and whether the approved decision remains intact. A calm reply can still be direct and firm.
Sources and editorial note
Examples are fictional. Sources for the platform guidance are linked below.