How to write a support tone guide (with before and after examples)
Four rules, a phrase table and seven before and after replies, from saying no to a refund to closing a ticket, to build a tone guide your team uses.
By the Paperlink AI teamPublished 7 min read
Short answer
Write a one-page tone guide with a few rules, such as answer first, be specific, say what you can do and own the next step. Add a table of phrases to replace and before and after examples for the situations where replies go wrong. Test the guide on last week's replies, then link it from your templates and review a few replies against it regularly.
Every support team says it wants to sound "friendly and professional". That phrase does not help an agent at the end of a long shift who has to tell a customer no. A tone guide does: a short page with a few rules, the phrases to avoid and what to write instead, and examples of real situations written badly and then well. This post shows how to write one, with seven before and after examples you can copy and adapt.
Why a tone guide, and not only templates
Templates cover the questions you expected. A tone guide covers everything else: the unusual refund, the message from a customer who is upset about something new, the reply an agent writes from scratch. It also keeps the team consistent as it grows, because new agents copy the habits around them, good or bad. And it gives reviewers a shared language. "This reads as defensive" is easier to act on when the guide says what defensive looks like.
Start with four rules
Keep the rules few enough to remember. These four cover most problems in support writing:
- Answer first. Put the answer or the next step in the first sentence. Greetings and context come after, and can be short.
- Be specific. Name the order, the error, the date and the cause. A specific sentence sounds human. A general one sounds like a form letter.
- Say what you can do. When the answer is no, the next sentence is what is possible.
- Own the next step. Say who does what next, and where the customer will hear about it.
Add one or two rules of your own if your product needs them, for example how you address customers by name, or whether you use contractions. Write each rule as an instruction, not as an adjective.
The phrase table
Most tone problems come from a short list of phrases. Collect the ones your team uses, from real replies, and give each one a replacement. Here is a starting list:
| Instead of | Write |
|---|---|
| Unfortunately, we are unable to | I can’t … because … What I can do is … |
| As per our policy | The reason in plain words |
| Please be advised | Leave it out and say the fact |
| We apologize for any inconvenience | Sorry for [the specific problem] |
| As I said before | Repeat the step without the reminder |
| Just / simply / easy | Leave it out: it implies the customer should have managed |
| However, … | And, or a new sentence that starts with the action |
| Please contact [team] | I’ve passed this to [team] |
The replacements are not banned words. They are a default. An agent who has a good reason to write "unfortunately" can still write it.
Seven situations, before and after
Examples teach tone faster than rules. Pick the situations where your team's replies go wrong most often. These seven are common in many support teams. The facts in each pair are the same: only the wording changes.
Saying no to a refund
Before: "Unfortunately, as per our refund policy, we are unable to process refunds after 30 days. Please be advised that this policy applies to all customers."
After: "I can’t refund this order, because it was delivered more than 30 days ago. What I can do is exchange it, or add the amount as store credit to your account. Which would you prefer?"
Why it works: It gives the reason in the customer’s terms, then moves straight to what is possible.
A delay you cannot fix today
Before: "Your order is delayed. We apologize for any inconvenience this may have caused."
After: "Your order is late: the carrier missed the pickup on Tuesday. It should ship tomorrow, and I’ll email you the tracking link as soon as it does. I’m sorry for the wait."
Why it works: A specific cause and a next step replace the stock apology, and the apology that remains is short and real.
A bug the team is still working on
Before: "We are aware of the issue and our team is looking into it. We will update you when we have more information."
After: "You’re right, exports with more than 1,000 rows fail right now. Our engineers are working on it. Until it’s fixed, you can export in two smaller date ranges. I’ll write to you here when the fix is live."
Why it works: It confirms what the customer saw, gives a workaround, and says who will follow up and where.
The customer made a mistake
Before: "As I mentioned in my previous email, you need to verify your email address first. Please read the instructions carefully."
After: "The last step is to verify your email address. Open the message we sent to you, and select Verify. If it isn’t in your inbox, check the spam folder, or reply here and I’ll send it again."
Why it works: It drops the reminder that they missed something and simply gives the step again.
An angry message
Before: "I understand your frustration. However, there is nothing we can do at this point."
After: "Being charged twice is frustrating, and you shouldn’t have to chase us about it. I’ve refunded the second charge today. Your bank usually shows it within a few business days."
Why it works: It names the actual problem instead of the feeling in general, and leads with action, not with "however".
Passing the case to another team
Before: "This is not something our team handles. Please contact billing."
After: "Billing can change the name on invoices, so I’ve passed your request to them with the details from this chat. You don’t need to explain it again. They usually reply within one business day."
Why it works: The customer is not sent away to start again. The handoff happens for them.
Closing a ticket with no reply
Before: "Since we have not heard back from you, we will be closing this ticket."
After: "I haven’t heard back, so I’ll close this ticket for now. If the problem comes back, reply to this email and it opens again with all the history."
Why it works: Same fact, but it tells the customer the door stays open and how to use it.
Adjust for the channel
The rules stay the same in every channel. The length and the structure change:
- Chat: short messages, one point each. Skip the formal greeting and sign-off. Send the answer first and the detail in the next message.
- Email: a greeting, the answer in the first lines, then steps as a numbered list. End with the next step, not with "Let me know if you have any other questions" after every message.
- Public replies: on social media or in reviews, other people read the reply too. Keep the facts about the customer's account private, and offer a private channel for them.
Test the guide on real replies
Before you share the guide, take ten replies your team sent last week and rewrite three of them with it. If the guide does not tell you what to change, a rule is missing or too vague. Then paste the before and after versions into the tone checker. It names how each version sounds and quotes the phrases that cause it. If the "after" still reads as defensive or blunt, the example is not ready for the guide.
A tone check is a second opinion, not a verdict. Read the result with your own judgment, and make sure the rewrite did not drop a fact or a promise.
Keep the guide in use
- Keep it to one page. A guide that nobody reads changes nothing.
- Link it from your reply templates and your onboarding checklist for new agents.
- In regular ticket reviews, pick a few replies and check them against the four rules. Add a new example when the same mistake shows up more than once.
- Update the templates whenever the guide changes, because templates are sent far more often than new replies.
Where a support chatbot fits
Tone matters most in the replies a person writes: the hard cases, the complaints and the exceptions. Paperlink AI is a customer support chatbot that answers only from the documents you upload and the website pages you import. When your content does not cover a question, the bot says so and shows your support contact, so the question reaches a person on your team. That is the reply your tone guide is for. You can see those questions in the Unanswered report and use them to decide which situations to add to your guide next.
To draft a first reply to a hard message, the email response generator writes one from the message and your points. Check it against your guide before you send it.