Why support needs its own tone guidelines
The brand's voiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience. is usually written for marketing: the website, the adverts, the emails. The brand identity and voice guide explains that tone is how the voice flexes for the situation without changing its principles, and that the brand guide should list the recurring situations with an example for each. Support meets more of those situations than any other team, and meets them under time pressure, so it needs that list taken much further.
The service and support hub treats tone as a standard alongside response and resolution times. It draws on Nielsen Norman Group's writing on tone of voice: tone is a set of choices along dimensions such as formal or casual and serious or funny, and a support team needs those choices made once rather than by each agent. The support channels and self-service guide adds the practical rule: write a short tone guide with examples for common situations, and show it in real replies rather than adjectives. This tutorial builds that guide.
Tone guidelines sit between three existing documents. The voice description says what the brand sounds like. The editorial style guide holds the house rules for spelling, names, numbers and dates. The service recovery and complaints guide sets the recovery sequence, from acknowledging the problem to following up. The tone guidelines repeat none of them: they say how a reply should sound when it carries out the recovery sequence, follows the house style and speaks in the brand's voice. A business with many branches applies the same tone to public review replies, and the guide to managing reviews across many locations turns it into a short reply guideline that each branch manager works from.
Before you start
- Have the brand voice and the house style. The voice principles and the editorial style guideThe house rules a writer checks while drafting, so spelling, names, numbers, formatting, links and sources are handled the same way by everyone. are the base the support guidelines adapt. If the brand has no written voice, write a short one first; tone guidelines cannot fix a voice that does not exist.
- Collect real replies. Gather a fortnight of sent replies from every channel the team answers in: email, chat, messaging, social replies and call notes where calls are summarised. Include replies customers thanked the agent for and replies that led to a complaint or a second contact.
- Know your standards. The response, resolution and tone standards in the support channels guide set what a good reply must achieve. Tone guidelines describe how it should sound while achieving it.
- Involve agents from the start. Two or three experienced agents who will use the guidelines every day should help write them. Guidelines written only by marketing tend to sound good and fail in a difficult conversation.
- Agree an owner. Someone in the support team owns the guidelines, with the brand owner consulted on changes that touch the voice.
The steps
Start from the brand voice and the house style
List the voice principles and mark each one for support use. Some carry over directly: a brand that is plain-spoken in its adverts should be plain-spoken in its replies. Some need a service reading: a playful voice may suit a delivery confirmation and be wrong for a refused refund. Note the house-style rules agents most often break, such as product names, dates and prices, and link the style guide for the rest rather than copying it.
Collect real replies, good and bad
Read the fortnight of replies with the agents and sort them into three piles: replies that sound right, replies that sound wrong, and replies where the team disagrees. The disagreements are the most useful, because they show the decisions nobody has made yet. Note what each good reply does well in plain words, such as "says what will happen next" or "names the problem in the customer's words", rather than in adjectives.
Choose the tone settings once
Using the dimensions the hub describes, decide where the team sits by default: how formal or casual, how serious or light, how brief or full, how warm or matter-of-fact. Write each setting as a sentence with a reason, for example "We write as one person talking to another, not as a company: first names, contractions, no legal phrasing unless we are quoting terms." Record the exceptions too, such as complaints escalated to a manager or replies to business customers, where the setting moves.
Write tone by situation
List the situations that recur in the replies you collected and write the tone for each. Most teams need at least these: a simple question answered; bad news, such as a delay or a fault; a refusal, such as a request outside the policy; an apology for the business's mistake; an angry or upset customer; a customer who has contacted more than once about the same problem; and a thank-you or compliment. For each, say what the reply must do first, what it must never do, and how the default settings shift. An apology, for instance, names the specific failure and takes responsibility in plain words, as the recovery guide sets out, rather than apologising for "any inconvenience".
List the words and phrases to avoid
Every support team has phrases that read as indifferent, defensive or evasive once a customer is upset. Collect them from the replies marked wrong and write each with what to say instead. Typical entries are phrases that blame the customer ("as stated in our terms"), phrases that promise nothing ("we will look into it"), internal jargon (queue names, system names, ticket statuses) and filler that delays the answer. Keep the list short enough to remember; a list nobody can recall is not followed.
Set the shape of a good reply
Agree a default structure, because structure carries tone as much as words do. The inverted pyramid works for most replies: the answer or the outcome first, then what the customer needs to do or what happens next, then any background. A customer who reads only the first lines should still know where they stand. Add the rules that apply to every reply, such as using the customer's name once, restating the problem in their terms, giving a specific next step with a time where the business can promise one, and signing with a real name.
Add approved and rejected examples
Under each tone setting and each situation, put one approved reply taken from real replies, lightly edited, and where useful one rejected version with the reason it was rejected. Examples do the work adjectives cannot: "warm but brief" means something different to every agent, while two replies side by side show it. Remove anything that identifies the customer before an example goes into the guidelines.
Say how tone shifts by channel
The same reply reads differently in chat, email, a messaging app and a public social thread. Chat replies are shorter and come in turns; email replies carry the whole answer at once; public replies are read by everyone who sees the thread and should move personal details to a private channel quickly, as the support channels guide advises. Write a line or two per channel on length, greetings and sign-offs, and on what never goes in a public reply. For social replies, align with the brand voice and cadence guide, which sets the voice for the social feed itself.
Test it on a week of real replies
Before publishing, ask agents to use the draft for a week and to flag every reply where the guidelines did not help or pointed the wrong way. Read a sample of that week's replies against the guidelines with the agents who wrote them. Change the rules that produced awkward replies, and add situations that came up but were missing. The test also shows whether the guidelines are short enough to use mid-conversation.
Publish it where agents work and keep it current
Put the guidelines in the tool agents already use, next to the saved replies and the help centre, not in a shared drive. Give it a version date and a change logA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced.. When quality reviews show the same correction repeatedly, it becomes a rule with an example; when a new situation starts to recur, it gets its own entry; when the voice or the house style changes, the guidelines change with it. Treat tone as a KPIA metric tied directly to an objective. only through the quality review, never by counting words, because a scored phrase list rewards agents for sounding compliant rather than helpful. If an outside team answers customers on the business's behalf, hand it this document itself rather than letting it write scripts of its own, as the guide to working with an outsourced customer service team explains.
What the guidelines hold: a contents table
| Section | What it records | Who decides |
|---|---|---|
| Scope and owner | Who the guidelines are for, the channels covered, the owner, the version date | Support lead |
| Inherited voice | The brand's voice principles with a note on how each applies in replies | Brand owner with the support lead |
| Tone settings | Default formality, seriousness, length and warmth, with reasons and exceptions | Support lead with agents |
| Situations | Tone for simple answers, bad news, refusals, apologies, angry customers, repeat contacts and thanks | Agents, approved by the support lead |
| Words to avoid | Phrases that read as blame, evasion or jargon, each with an alternative | Agents |
| Reply shape | Answer first, next step, background; rules for names, times and sign-offs | Support lead |
| Examples | An approved reply, and where useful a rejected one, under each rule | Agents, approved by the support lead |
| Channels | Length, greeting, sign-off and public-reply rules for each channel | Support lead with the social owner |
| Links | Brand voice, house style, recovery sequence, saved replies, help centre | Owner |
| Change log | Each change, the reason and the date | Owner |
Two neighbouring documents follow from the guidelines rather than sitting inside them. Saved replies for common questions should be written in the guidelines' tone and edited for each case before sending. Teams that draft replies with AI need the same decisions in a form a model can follow, which the brand voice guide for AI drafting builds; the AI in customer service guide adds that drafts should follow the service tone and that agents check every draft before it is sent. Which questions suit a saved reply and which a draft is weighed in the comparison of saved replies and AI reply drafts. An assistant that answers customers directly carries the tone in its standing instructionsThe business's rules placed before every question an AI assistant answers: scope, sources, refusals, when to hand over and what never to promise., with approved and rejected examples taken from these guidelines, as the tutorial on writing instructions for an AI assistant shows. Where customers are answered in other languages, the localisation style guide tutorial records how address and register work in each language, and the support guidelines link to it. Help articles follow the craft in the writing for the web guide and should sound like the replies that link to them.
A boiler servicing firm writes its support tone guide (illustrative)
Zentravo Heating Care writes tone guidelines for its support team
Zentravo Heating Care, an invented boiler servicing and repair firm, has 9 agents answering phone, email and chat. The support lead and 3 agents read 160 replies from a fortnight and sort them: 71 sound right, 52 sound wrong and 37 split the team. Most of the split replies are about engineer visits cancelled on the day, where some agents apologise at length and others state the new slot with no apology at all.
The team sets the default tone as plain and calm rather than cheerful, because many customers write in with no heating or hot water. It writes 8 situations, including a cancelled visit, a repair refused under the warranty terms and a customer with no heating in cold weather, each with an approved reply. The avoid list has 12 phrases, among them "as per our policy" and "we apologise for any inconvenience". The reply shape puts the new visit slot or the decision in the first sentence.
During the test week agents flag 14 replies where the guidelines did not help; 9 involve landlords writing on behalf of tenants, which becomes a ninth situation. Over the following month, the share of emailed replies that draw a follow-up question from the same customer within a week falls from 31% to 22% in the team's own records, and the quality review's tone line is marked as met in more reviewed replies than before.
Common mistakes
- Writing adjectives instead of decisions. "Friendly and professional" tells an agent nothing. Write the settings as sentences with reasons and show them in examples.
- Starting from scratch. Support tone inherits the brand voice and the house style. A separate voice for support makes the brand sound like two companies.
- Leaving out the hard situations. Guidelines that only cover simple answers fail exactly when tone matters: bad news, refusals, apologies and angry customers.
- No examples from real replies. Invented examples are too tidy. Take them from replies the team actually sent, with customer details removed.
- Scripts instead of guidelines. Replies copied word for word read as nobody having read the customer's message. Guidelines fix the decisions and leave the words to the agent.
- Ignoring the channel. A reply that works by email can be too long for chat and wrong for a public thread.
- Publishing it and walking away. Corrections that recur in quality reviews are missing rules. Add them, with the example, and record the change.
