Template
How to write a chatbot tone of voice that sounds like you
A visitor asks if you cover their town. The reply sounds like a call centre that has never met you.
Chatbot tone of voice is the words you'd actually text, how short the bubble is, and when a person takes over. You'll leave with lines you can paste in this afternoon.
The better chat is one you'd send yourself. They get the postcode question in your phrasing, and a time you'll ring.
Chatbot tone of voice, taken from texts you already sent
Open the last ten replies you were glad you sent. Texts are better than brochures. Look for the words you repeat when you are being straightforward: "pop your postcode over", "I can do Thursday", "I'll price that and come back to you".
Those phrases are the tone. A bot that says "Your enquiry has been logged and a representative will action it" has left the building, even if the information is similar.
Write a one-line portrait before you write the replies:
- Are you "I" or "we"? Sole traders should say "I" unless the site always says "we".
- Do you use first names?
- Do you say "cheers", "thanks", or nothing extra?
- Which trade words do your customers use, and which ones do only you use?
Keep the portrait on the same page as the replies. When you add a line in three months, you will not have to reconstruct the mood from memory.
What to teach a chatbot on day one lists the questions. How the answers sound is the other half. A correct answer in the wrong voice still feels off. A lovely voice with a wrong price is worse.
"Your enquiry has been logged" is chatbot reply wording from a template, not from you.
Ten minutes: open the last ten texts you were glad you sent. Highlight three phrases you'd let a bot repeat.
What to borrow from plain-English guidance, and what to leave
GOV.UK publishes rules for tone and clear language. They are written for public information, not for a decorator's website. Several of them are what a plain English chatbot needs.
A few are a bad fit. "Make it professional" often pushes owners toward the stiff lines.
The page on using the right tone says GOV.UK's tone is specific, informative, clear and concise. It should be brisk without being terse, and human rather than a faceless machine. Write as if you are talking to one person you can help.
Use active voice, say "you", and prefer "they" rather than "he or she". Block capitals are hard to read and can feel like shouting. That transfers into a chat bubble.
Two parts stay on GOV.UK. The same page says there is usually no need to say "please". That is a house style for a government site.
Your customer is choosing whether to hire you. "Please send the postcode" is a normal text. One is enough.
Match yourself.
The page also calls GOV.UK's tone emotionless, because adjectives can sound like spin. A public page has a reason to be spare. A family-run firm can still sound warm.
Warm means a human sentence. "Happy to help with that" is enough. "We are absolutely delighted and passionate about your cleaning journey" is the voice to retire.
The companion page on clear language says plain English is mandatory on GOV.UK, and it gives swaps that work in any chat: "buy" rather than "purchase", "help" rather than "assist", "about" rather than "approximately". Use words your readers use, and explain a specialist term the first time. Keep paragraphs to five sentences or fewer, and split sentences past about 25 words. In a chatbot, one idea per message.
GOV.UK also separates "must", "need" and "can". "Must" is a legal requirement. "Need" moves a process on.
"Can" is a choice. "I'll need the postcode before I can quote" is the pattern. "You must provide your postcode" sounds like a form.
If you're weighing a bot against a form, that comparison is in website chatbot or contact form.
A plain English chatbot still sounds like you. Short words don't mean a colder you.
Ten minutes: swap "purchase", "assist" and "approximately" out of any draft reply. Use buy, help and about.
Say who is speaking
GOV.UK's tone guidance makes a point that chatbot owners miss. It says you should make it clear who has written the content. You can call yourselves "we" where it is already obvious who that is. In other places, use the name of the organisation before you say "we", and do not assume the reader knows.
On a small site the chat widget often pops up with no introduction. The visitor does not know if they are talking to you, to a call centre, or to a script. Put the name in the first line.
- "Hi, you're chatting with [your business name]. I can take the details of the job."
- "Hello, this is [your name]. Ask me about new work, or leave a number and I will ring you."
Use your real name. If several people reply later, "we" is fair once the business name has appeared. If it is only you, stay with "I" all the way through. Switching from "we" to a personal text an hour later is what makes people feel they were misled, even when you meant well.
There's a privacy version of the same point. The ICO's guidance for small organisations on privacy notices says you need a notice if you hold names and email addresses, and you give it when you first collect the details. For you, that's a short line plus a link in the chat, not the whole notice read aloud. The examples and the clause list are in the FAQ.
A line that does both jobs:
You're chatting with our website assistant at [business name]. We'll use your details to reply about this job. The privacy notice is here: [link].
The ICO's principles for explaining AI say you should make the use of AI obvious. For a greeting, say it's an assistant, and that a person follows up on quotes and dates.
Ten minutes: put your business name in the first line of the chat and read it on your phone.
The tone sheet
Fill the middle column in your own words. The right-hand column is there to catch the lines that creep in from templates. Read the middle column out loud before you paste it into the bot. If you stumble, the customer will too.
| Moment | A line in your voice | A line to retire |
|---|---|---|
| Greeting | Name the business, say it is the website assistant, and say what it can take | "Welcome to our innovative support experience" |
| Asking for details | Ask for one thing at a time, in the words you use on the phone | "Kindly furnish your requirements and location" |
| A question you have answered in writing | Give the short answer, then the next step | A paragraph copied from a page, with no question back |
| Something you have not written down | Say you do not have it, take their number, and name what happens next | A guess, or "Great question!" followed by a vague essay |
| Handoff to a person | Say who will reply, or just "I will", and give a real window | "A ticket has been generated" |
| Out of hours | Say you have the message and when a person next looks | A live-chat style "we're online" when nobody is |
| Price or date | Only a figure or a day you have approved in the script | Any price the bot builds from a similar job |
| Closing | One line on what you will do, then stop | A second sales pitch after they have already left their number |
The middle column is a brief, not the finished sentence. Write the finished sentence beside it in a note. For example, a handoff that many sole traders can live with is: "Thanks. I've got your number and what you need. I'll ring you on weekday mornings if I miss you today." Change the window until it's one you keep. A tone that promises "immediately" and delivers tomorrow is a tone problem, not a wording flourish.
You'll know it's working when a customer replies in the same register, as if they'd texted you, not a desk.
Ten minutes: fill the greeting row and the "I don't know" row in your own words. Read both aloud.
The handoff is part of the voice
The handoff to a person is where bots suddenly sound like institutions. "Your request has been escalated" is not how you text. Say what is happening in the same voice as the greeting.
Three handoffs cover almost every small service firm:
- I will reply. "Leave your number and I'll come back to you today." Use this when you are the person.
- A colleague will reply. "[Name] looks after new quotes and will email you by tomorrow lunchtime." Use a name only if that person knows their name is in the bot.
- We need a bit more, then a person. "If you send the photos in this chat, I'll look and tell you whether we can do it." The bot collects. You decide.
Do not invent a department you do not have. "Our customer success team" at a two-person firm is a costume. Customers notice when the costume comes off and a normal person writes back.
What to automate first draws the same line in operational terms. The bot can take the common question and the contact details. A person keeps the price, the complaint and the yes or no.
The tone sheet should make that line audible. If a reply reads as if the job is already booked, rewrite it until it feels like a message taken.
For the difference between a bot, a live chat and a phone receptionist, see chatbot vs live chat vs AI receptionist. The voice rules here are for the website chat. A phone agent needs a spoken version of the same sheet: shorter again, and with a slower ask for the number, because people mishear.
Ten minutes: write the handoff you'll keep, with a day and a time of day in it.
Words that make any firm sound like a template
Run a find on your draft replies. If these show up, replace them with the word you'd say.
"Kindly furnish your requirements" has never been said in your van.
- Purchase, assist, enquire (as a verb you would never say), commence, terminate. Prefer buy, help, ask, start, end. "Enquiry" as the noun is normal in British English. "We have received your enquiry" is the stiff version. "Got your message" is closer to a text.
- Delighted, passionate, world-class, cutting-edge. They tell the reader nothing about the job.
- Ticket, case, escalation, agent, unless you truly run a helpdesk and your customers know those words.
- Exclamation marks in every line. One, in a greeting, is a lot. None is safer.
- The customer's name in every sentence. Once, at the start, is friendly. Four times is a mail-merge.
Specialist words can stay when the customer used them first. GOV.UK allows a specialist term once you explain it. In a chat, that explanation is one short clause.
Ten minutes: search your draft for "delighted" and "ticket". Delete the hits.
Rewrite the stiff lines, one swap at a time
When a template sounds wrong, do not add adjectives to warm it up. Swap the verb and cut the noun. These pairs show the method.
Write the right-hand side in your own dialect. The left-hand side is the sort of line that arrives in a default widget.
- "Your request has been received and will be processed shortly." becomes "Got it. I'll look at this today and reply with a price or a question."
- "Please provide your contact details so an agent can assist." becomes "What number should I ring you on?"
- "We apologise for any inconvenience caused." becomes "Sorry about that. Tell me what happened and I'll sort the next step."
- "Our team of experts will be in touch." becomes "I'll ring you in the morning." If it will not be you, name the person or say "someone from [business] will ring you in the morning."
- "Is there anything else I can help you with today?" becomes nothing, if you have already asked for the one detail you need. Extra offers at the end of a short chat make people wonder if they finished.
Read the stiff line, then your rewrite, out loud. The shorter one is the one you would text. The pattern is a passive verb, no name, no time, and no next step.
Ten minutes: rewrite one stiff line from the list above, in the words you'd text.
Keep a tiny style card
One card, stored with the bot's notes, beats a long document nobody opens. Six lines are enough:
- I or we:
- Greeting, including the business name:
- Words we use for the work:
- Words we do not use:
- The handoff sentence, including the real time window:
- The sentence for "I don't know":
Pin the card where you edit the bot. When you add a new answer, check it against the card before you save. This is also how you stop a well-meaning contractor, or a cousin who "knows marketing", from replacing your voice with a generic one over a weekend. If their draft fails the card, it does not go live.
Review the card when something true changes: you hire someone, you stop Saturday calls, you rename a service. A tone sheet that promises a Saturday reply after you've dropped Saturdays isn't a tone problem. It's an accuracy problem, and it'll annoy people faster than a plain sentence ever will.
Ten minutes: fill the six lines on a card and pin it where you edit the bot.
How to test the voice without a focus group
You are the focus group, plus one other person who will be honest.
- Read the lines on your phone. That is the width your customer will use.
- Ask the ten questions from your day-one list. Mark any sentence you would not send.
- Ask something you refused to write an answer for. The only acceptable reply is the handoff. If it invents a price, it is not ready.
- Ask someone who knows the business who they think is speaking. If they cannot tell it is you, add your name.
- For the first week, read every transcript. Delete lines that crept in from a template library.
Change one thing at a time, or you will not know which change helped. After that, read five chats a month. If you're wincing, fix the line. If you're bored, the tone is probably doing its job.
Ten minutes: read the greeting and the handoff out loud. If you wouldn't send either as a text, rewrite it before you switch anything on.
Common questions
Should a chatbot say please and thank you?
Yes, if you would. GOV.UK's own tone guidance often drops 'please' because it is writing public information. A small firm is in a different conversation. Polite is fine. Padded is not. One thank you is enough.
How long should a chatbot reply be?
One to three short sentences is plenty for a chat bubble. GOV.UK asks writers to split sentences that run past about 25 words. In a chat, aim shorter than that. If you need a paragraph, you probably need a page on the site and a link.
What should it say when it does not know?
Say so, take the detail, and tell them a person will reply. A confident guess is the fastest way to sound like a robot and to create a complaint. 'I don't have that to hand. I've noted it and someone will come back to you' is a complete answer.
Can I copy another company's chatbot wording?
You can learn from the shape: greeting, question, handoff. Copying their jokes, their slogans or their promises will sound borrowed, and you may promise something you do not offer. Start from the last ten messages you were happy to send yourself.
How do I know it sounds like us?
Read every line out loud. If you wouldn't send it as a text to a customer, rewrite it. Then let two people who know the business read the greeting and the 'I don't know' line. If either line could belong to any firm in the country, it's too generic.
Where does the privacy notice sit in the chat?
The ICO's small-organisation guidance says that if you hold names and email addresses you need a privacy notice, given when you first collect the details, and kept where people can find it again. Their examples include a link on the contact page before anyone types, a link in the reply, and a spoken pointer on a voicemail. You don't have to read the whole notice in the bubble. Explain the key point and show the link. The ICO's principles for explaining AI, which apply to any organisation, say you should make the use of AI obvious, including when and why. A greeting isn't a legal decision. Still say it's an assistant, and that a person follows up on quotes and dates.