Tone & empathy
What does good tone look like in a support ticket?
Good tone is tone matched to the person in front of you, not a fixed register applied to everybody. The same sentence that reassures a frustrated customer reads as padding to an engineer who wants the fault. Scored on whether the reply met the customer where they were and lowered the temperature, not on whether it was polite.
- Matched tone to the customer persona; de-escalated well
- One of the 11 dimensions every ticket here is graded against
What a weak answer looks like
The ways this is usually lost
Named failures rather than general warnings, because a warning nobody can recognise in their own work changes nothing.
An apology paragraph before any sign the problem was understood. Sympathy that arrives before comprehension reads as a script.
The same opening on every ticket regardless of who sent it or how urgent it was.
Matching an angry customer's register back at them, or going so formal that the reply sounds like a legal notice.
What a strong one looks like
What the grader is actually looking for
The same ticket, done in the way that scores.
One line showing the problem was understood, in the customer's own terms, before anything else.
Register that fits the sender: shorter and more technical for an engineer, more explicit about next steps for somebody who is stuck and anxious.
Heat taken out by saying what happens next and when, which is what actually calms somebody, rather than by apologising harder.
Questions
Asked about this one
Is empathy the same as apologising?
No, and the two often work against each other. An apology before the problem has been understood reads as a script, and a customer who has already explained the fault twice hears it as a delay. Showing you understood what went wrong does more to de-escalate than any number of apologies.
Should tone change between customers?
Yes. That is most of what is being scored. An engineer reporting a reproducible bug and a non-technical user locked out of an account need different replies. Sending both the same one is the most common way this is lost.
Related guides
- Diagnostic quality
- Communication clarity
- SLA discipline
- Resolution correctness
- Documentation
- Judgement on the AI's suggestion
- Ticket admin accuracy
- Priority judgement
- Escalation judgement
- Technical depth
- Technical support interview questions, answered from realistic tickets
See this scored on a realistic ticket: work one free, read a worked ticket, or see what a graded record shows. Every guide is listed on the guides index, and if something here is wrong or unclear, tell us.
Free to start · no sign-up
You do the work. We hand you the record.
Your first ticket is free.