A support team writes a set of replies that are relentlessly cheerful. Every message contains an exclamation mark and an offer to help with anything else at all.
A customer whose order has been lost for a fortnight receives one of them. The cheerfulness reads as indifference, and a recoverable situation becomes a public complaint.
The tone was not wrong in general. It was wrong for that moment, and nobody had written down which moments need something different.
1. Define the voice in four words, not four pages
Plain, warm, direct, brief is a usable instruction. A brand voice document nobody reads produces replies that follow whatever the writer felt like that day.
2. Write for the worst day, not the best one
Any tone that would be offensive to somebody having a terrible experience is the wrong default, because those customers receive the same messages as everybody else.
3. Be clearly automated
Customers who discover they were deceived about who they were speaking to remember it. Being open about it while being useful is the better trade.
4. Drop the forced enthusiasm
Exclamation marks, superlatives and an eagerness to delight all read as insincere at scale. Customers want the answer and the absence of friction.
5. Keep it short
Long replies signal that nobody read the question. Brevity is the single most reliable indicator of competence in support writing.
6. Match the customer's register
Somebody writing briefly wants brevity. Somebody writing at length with detail wants acknowledgement of that detail. A fixed register mismatches half of everybody.
7. Never argue and never defend
Where something went wrong, say so plainly. Explanations that read as excuses cost more goodwill than the original failure.
8. Write the escalation line carefully
The sentence handing somebody to a person is read by an already frustrated customer, and it sets up everything afterwards, which is the ground in handover questions between bot and agent.
9. Write the out of hours message honestly
An honest tomorrow morning is better than a vague shortly, particularly in the hours described in weekend and holiday cover questions.
10. Handle cancellation and complaint moments deliberately
These are where voice matters most and where scripts are usually weakest, which is the ground in subscription questions that lead to cancellations.
11. Decide how it opens and how it closes
The first line sets whether somebody feels met or processed, and the last line decides whether they know what happens next. Both are written once and used thousands of times, which makes them worth more attention than any individual reply the team will ever send.
11. Use the customer's words back
Repeating the specific thing they said, in their words, is what makes somebody feel read. It is also cheap and rarely done.
12. Ban the phrases that signal a script
Unfortunately, as per our policy, we value your business and anything similar. Customers recognise these instantly as the sound of not being helped.
13. Write the not knowing line properly
Admitting that something cannot be answered, and saying immediately what will happen instead, is the most frequently used sentence in any automated system. Written badly it reads as a dead end, and written well it reads as somebody taking responsibility for getting an answer.
13. Review real transcripts monthly
Voice drifts and edge cases appear. Reading twenty real conversations tells you more than any guideline document, and drafts can be refined with the ai reply generator.
14. Make consistency the goal rather than personality
One recognisable voice across every channel and hour is worth more than a memorable one, which is what how to give your chatbot a consistent brand voice sets out. See features, start at try, and the sector view sits under small business.