Communication clarity
What makes a support update clear?
A clear update tells somebody what is happening, what it means for them, and when they will next hear from you. It is written for the person receiving it rather than for the queue. It should survive being read on a phone by somebody who has not seen the earlier messages.
- Clear, professional, customer-appropriate updates
- 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.
Internal vocabulary left in: queue names, ticket states, service names the customer has no way to know.
An update that reports activity without saying what it means. "We are investigating" tells somebody nothing they did not already assume.
No next contact, so the only way to find out what is happening is to ask again.
What a strong one looks like
What the grader is actually looking for
The same ticket, done in the way that scores.
The outcome first, then the detail, so the first line is useful on its own.
Plain nouns for the thing that broke, and the customer's words where they had a word for it.
A stated next step with a time attached, which is the single thing that most reduces follow-up messages.
Questions
Asked about this one
How much technical detail belongs in a customer update?
Enough to explain what changed for them and no more. The mechanism belongs in the resolution note, where another engineer will read it. A customer needs to know whether their data is affected, whether to retry, and when they will hear next.
Is a short update worse than a long one?
No. Length is not a measure of care. Three accurate sentences with a next contact time score better than six paragraphs that leave somebody unsure what to do.
Related guides
- Tone & empathy
- Diagnostic quality
- 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.