Bots Chat in Plain Words: A Readability Check for Every Message Your Website Bot Sends (Free Message Checker)
Bots chat with your customers in whatever words you gave them, and those words are often the problem. Answers copied from policy pages arrive as 50-word sentences. Support phrases like “kindly revert” confuse people reading in a second language. A fallback asks four questions at once. This guide shows how to make every bot message easy to read on a phone, with before-and-after rewrites and a free checker that marks long sentences, jargon, passive wording and overloaded messages.
⚡ In short
- A chat bubble on a phone shows about 300 characters at once. Messages longer than that get skimmed or skipped.
- Keep sentences under 20 words, use everyday words, and say who does what.
- One question per message. Offer choices as a short list instead of a run of questions.
- Check your most-seen messages first: welcome, fallback, delivery and returns.

Why it matters
Chat is read fast, on small screens, often in a second language
A chat window is not a web page. People read it in snatches, on a phone, while doing something else. They expect each message to be short, like a text from a friend. When a long, formal paragraph arrives, most people skim the first line and miss the rest.
That’s a bigger problem for bots than for people. A person on your team naturally writes “Yes, you can return it within 7 days.” A bot often sends whatever text it was given, and that text usually came from somewhere written for a different purpose: a terms page, a policy document, an email template. Legal language reads fine in a contract. In a chat bubble it looks like a wall.
In India there’s another layer. Many of your visitors read English as a second or third language. Plain words help them more than anyone. Office phrases common in Indian business English, like “kindly revert”, “do the needful” or “please intimate”, are familiar to some readers and puzzling to others, and they make a bot sound like a government office rather than a shop.
The good news is that readability is one of the easiest things to fix. You don’t need new software or more knowledge. You rewrite the messages you already have, mostly by cutting. Most small businesses can improve the messages their bot sends most often in an afternoon.
When bots chat in plain words, visitors understand the answer the first time, ask fewer follow-up questions and are less likely to ask for a person just to check what the bot meant.
Seven checks
What makes it hard to read when bots chat
Too long for the screen
Over about 300 characters, the message scrolls off a phone screen. Split it or cut it.
Long sentences
Over 20 words, readers lose the thread. One idea per sentence.
Office jargon
“Kindly”, “revert”, “as per”, “escalated to the concerned team”. Use everyday words.
Passive wording
“Refunds will be processed.” By whom, when? Say “We refund within 5 days.”
Too many questions
Four questions in one message means the visitor answers none. Ask one.
Shouting
CAPITALS and !!! read as panic or anger, especially in an apology.
Key fact buried
The answer is at the end of a paragraph. Put it in the first sentence.
Length
Write for one phone screen
The simplest rule is length. On a typical phone, a chat bubble shows roughly 250 to 300 characters before the visitor has to scroll. Beyond that, people skim. If the important part is at the bottom, they miss it.
That doesn’t mean every message must be tiny. It means each message should do one job, and the first sentence should carry the answer.
Compare these two answers to “What is your return policy?”:
Before: “Kindly be informed that as per our policy, all return requests must be initiated within a period of seven days from the date of delivery, failing which the request will not be entertained, and refunds will be processed to the original mode of payment subsequent to quality verification.” (One sentence, 47 words.)
After: “You can return unused items within 7 days of delivery. Once we’ve checked the item, we refund the same way you paid.” (Two sentences, 22 words.)
Same facts. Half the length. The answer is in the first five words.
If something genuinely needs detail, such as a full size chart, a list of serviceable pin codes or step-by-step instructions, put the short answer in the chat and link to the page with the detail. “Yes, we deliver to most pin codes. Check yours on our delivery page.” Visitors who need the detail click; everyone else is already answered.
If you use LiveChatBot’s AI Agent, apply the same thinking to the knowledge you give it: short, clear source text tends to produce short, clear replies. Our AI training guide covers how to write it.
Words
Swap office language for everyday words
Most hard-to-read bot messages aren’t hard because of the ideas. They’re hard because of the words. A few swaps make a big difference.
Common swaps
- “Kindly” → “Please” (or nothing)
- “Revert” → “Reply”
- “As per our policy” → “Under our policy”, or just state the rule
- “Escalated to the concerned team” → “Passed to the right person”
- “Initiate” → “Start”
- “Prior to” → “Before”
- “Subsequent to” → “After”
- “Utilize” → “Use”
- “Do the needful” → say exactly what you will do
- “At the earliest” → give an actual time
Say who does what
Passive wording hides the person doing the action. “Your request has been escalated and will be processed” leaves the visitor wondering who has it and when anything will happen. “I’ve passed this to Ravi in our orders team. He’ll reply by 5 pm today” answers both. If you can’t promise a name, at least say “our team” and give a time.
Drop throat-clearing
“Please note that”, “We would like to inform you that” and “Kindly be informed” add nothing. Start with the information itself.
None of this means being casual or careless. Plain words are still polite. They just respect the reader’s time. Our guide to sounding human in chat has more on tone.
Free tool
Check every message your bot sends
Paste your bot’s messages, one per line. The checker marks length, long sentences, jargon, passive wording, too many questions and shouting, and gives a rough reading-ease score.
Paste your bot’s messages, one per line (welcome, answers, fallback, handover).
Runs only in your browser; nothing is sent or saved. Rules of thumb for plain English, not a grade from any official test.
Questions
One question per message
Fallback messages are the worst offenders. When a bot doesn’t understand, it’s tempting to offer everything at once: “Sorry, I didn’t understand. Can you rephrase? Or would you like to see our FAQ? Or talk to a person? Or browse products?”
Four questions. The visitor has to work out which one to answer, and often answers none. Worse, “Can you rephrase?” puts the blame on them.
A better fallback does one thing well. Two good patterns:
Offer a short choice. “I’m not sure I got that. I can help with delivery, returns or sizes, or connect you to our team.” That’s one sentence, with options the visitor can pick by typing a word.
Hand over. “That one’s best for our team. They’re online now and will see your message.” No question at all.
The same rule applies everywhere. If the bot needs a detail, ask for one at a time: “What’s your pin code?” then, after the reply, “And which size?” A visitor can answer a single question in two seconds. A message with three questions often gets a reply to only the first.
Our guide to error-moment replies covers fallback wording in more depth, and the microcopy guide covers the small fixed lines around the chat window.
Before and after
Real-style messages, rewritten
Languages
Plain English helps translation too
If your bot or chat widget translates messages, plain English pays off twice. Short sentences with everyday words translate much more accurately than long ones full of idioms and office phrases.
“Kindly do the needful at the earliest” can come out of an automatic translation as something strange. “Please reply by 5 pm” translates cleanly into almost any language.
LiveChatBot detects the visitor’s language and can show welcome translations, and the AI Agent can reply in the visitor’s language. Both work best from clear source text. If many of your visitors write in Hinglish or regional languages, test your key messages with a few real customers or staff who speak those languages. Our multilingual chat guide covers the setup.
A good habit: read each message aloud. If you’d never say it to a customer standing in front of you, rewrite it. When bots chat the way your best team member talks, translation, comprehension and trust all improve together.
Priorities
Which messages to fix first
You don’t need to rewrite everything at once. Start with the messages visitors see most often, because each improvement there is multiplied by every chat.
- The welcome message. Every visitor who opens the chat sees it. Our welcome message guide has examples.
- The fallback. It appears whenever the bot is unsure, which, early on, is often.
- The handover and out-of-hours messages. These set expectations at the moment visitors are most anxious.
- Your top five answers. Usually delivery, returns, payment, hours and pricing. Check your inbox to see which questions come up most.
- Saved replies your team uses. The same plain-English rules apply to messages people send with one tap. See saved replies.
Paste each group into the checker, fix the ones with the most points, and then read the results aloud. Repeat for the next group next week.
Once your messages are clean, keep them that way: whenever someone adds a new answer or saved reply, run it through the checker before it goes live. It takes ten seconds and stops policy-page text creeping back in.
Checklist
Plain-words check for any bot message
Getting started
Fix your five most-seen messages today
Copy your welcome message, fallback, handover, out-of-hours message and your most common answer into the checker. Fix whatever it marks, read the results aloud, and update your bot. That’s about thirty minutes, and it touches nearly every conversation.
LiveChatBot’s free plan includes a customisable welcome message with auto translations, an AI Agent with a small free monthly allowance, a free keyword bot that answers from saved replies, opening hours with an away form, the team inbox and the Android app, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.
Frequently asked questions
How long should messages be when bots chat with customers?
Aim for under about 300 characters per message, so it fits one phone screen, with no sentence over 20 words. Put the key fact first and link to a page for detail.
Is formal language more polite in a chat?
Not usually. Plain words like please, reply and before are just as polite as kindly, revert and prior to, and much easier to read, especially for people reading in a second language.
What should a bot’s fallback message say?
One short sentence that offers a few topics it can help with or connects the visitor to a person. Avoid stacking several questions.
Does the checker work for AI-written replies?
Yes. Paste a few typical AI replies to check them. If they’re long or formal, rewrite the knowledge the AI answers from in plainer words.
Does the checker send my messages anywhere?
No. It runs entirely in your browser and nothing is sent or saved.
Keep reading
Related guides
Bot Technologies Compared on One Question: Keyword Rules, Fuzzy Matching, Search and AI Answers (Free Matching Simulator)
Bot Live Chat Weekly Review: Read Last Week’s Chats and Decide What the Bot Learns Next (Free Outcome Tagger)
Bot in Chat With Your Team: Who Speaks When, So the Bot and Staff Never Talk Over Each Other
Messages people read the first time
Short, plain answers from a bot that hands over when it should. Start free on livechatbot.in.