Chatbot Answers That Fit a Phone Screen: Length, Order and Splitting, With a Free Bubble Fitter

Chatbot answers are read on phones more than anywhere else, in a bubble about as wide as a thumb is long. A reply that looks fine in your dashboard can turn into a wall of fourteen lines on a small screen, with the useful part buried in line nine. This guide shows how long a reply can be before people stop reading, what order to put things in, when to split one reply into two bubbles, and how to cut filler without sounding rude. A free tool estimates how your reply looks on a phone and suggests a split.

⚡ In short

  • On a phone, one chat bubble line holds roughly 30 to 35 characters, so 60 words becomes 10 or more lines.
  • Aim for 2 to 4 lines per bubble and no more than one screen of chat per reply.
  • Put the answer first, the condition second, and the next step last.
  • Delete greeting and closing filler; it costs lines and adds nothing.
Chatbot answers in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Why length matters

A chat bubble is narrower than you think

When you write a reply in a dashboard on a laptop, the text box is wide. A 70-word paragraph looks like three comfortable lines. Your visitor sees something else. On a typical phone, the chat window is the full width of the screen minus margins, and each bubble is narrower still, because it sits to one side with an avatar beside it. In practice, one line of a bubble fits around 30 to 35 characters. That’s five or six words.

Do the arithmetic and the problem is clear. A 70-word reply is roughly 12 lines. With the phone keyboard open, the visible chat area may show only 8 to 10 lines. The visitor has to scroll inside a small window to read your reply, and many won’t. They’ll read the first two lines, decide whether it answers them, and either act or type the question again.

That’s why the first two lines matter more than everything after them. If the first two lines are “Thank you so much for reaching out to us regarding your query”, you’ve spent the most valuable space on nothing.

Short, front-loaded replies aren’t about being curt. They’re about respecting the screen your customer is actually using. Our guide to chat on phones covers the rest of the mobile layout, from the bubble to the keyboard.

A length budget

How long each kind of reply should be

It helps to set a budget for different kinds of replies, the same way a newspaper sets column inches. These are starting points for small-business chat, not strict rules.

  • Simple facts (hours, price, delivery time): 1 bubble, 2 to 3 lines, about 15 to 25 words.
  • Facts with a condition (free shipping above a value, returns except some items): 1 bubble, 3 to 4 lines, about 25 to 35 words.
  • How-to steps (how to track an order, how to book): 2 bubbles, or one bubble plus a link to the page with the full steps.
  • Policy explanations (refunds, warranty): 2 bubbles at most, then a link to the full policy.
  • Apologies and complaints: 1 short bubble that acknowledges, then a question that moves things forward.

If a reply needs more than two bubbles, it probably belongs on a web page, and the chat should point to it. Chat is good at the first answer and the next step. It’s poor at long documents.

A useful test: read the reply out loud. If you run out of breath, or if you’d naturally pause to let the other person speak, that’s where the bubble should end.

Free tool

See how your reply looks on a phone

Paste one reply. The tool estimates its line count in a phone bubble, flags long sentences, filler and a missing next step, and suggests a split into short bubbles.

Paste one reply your bot gives (an AI answer or a saved reply)

Runs only in your browser; nothing is sent or saved. Line counts assume a typical phone chat bubble of about 32 characters per line, so treat them as estimates.

Order

Answer first, condition second, next step last

The most reliable structure for a short reply has three parts, in this order.

1. The answer

Start with the thing they asked for. If they asked about delivery to Nagpur, the first words are the delivery time to Nagpur. If they asked whether you’re open on Sunday, the first word is “Yes” or “No”.

2. The condition

Then add the one condition that changes the answer for some people. “Orders placed after 4 pm go out the next day.” “Sunday hours are 11 am to 5 pm.” Only one condition per bubble. If there are three, the most common one goes here and the rest go on the policy page.

3. The next step

Finish with something the visitor can do or answer: “Share your pin code and I’ll check.” “Would you like the booking link?” A next step keeps the conversation moving and stops the visitor having to think up the next question.

Here’s the difference in practice (illustrative):

  • Before: “Thank you for your question. We are a family business based in Pune and we work with several courier partners, so delivery times can vary depending on where you are. Generally, delivery takes 2 to 5 days.”
  • After: “Delivery takes 2 to 3 days in metro cities and 4 to 7 days elsewhere. Share your pin code and I’ll give you a closer estimate.”

The second version is half the length and gives more information.

Splitting

When one reply should become two bubbles

Sometimes a reply genuinely needs more room: a price list with three options, a return process with steps, an explanation of a delay. In those cases, two short bubbles read better than one long one.

Split at a change of job. The first bubble answers; the second explains or asks. For example:

  • Bubble 1: “Yes, we can deliver by Friday to Pune.”
  • Bubble 2: “Order before 2 pm Wednesday and choose express at checkout (₹80). Want the link?”

Each bubble is short enough to read at a glance, and the visitor can react to the first before reading the second.

Don’t split into many tiny bubbles either. Five one-line bubbles arriving in a row feel like being talked at, and they push the visitor’s own message off the top of the screen. Two, occasionally three, is the comfortable maximum.

For saved replies your team sends by hand, split them into separate saved replies when the second part is optional. Your team can then send the first and decide whether the second is needed. Our guide to saved replies explains how to set them up with the visitor’s {name}.

Filler

Cutting filler without sounding rude

Most long replies aren’t long because the answer is complicated. They’re long because of filler at the start and end: “Thank you so much for reaching out”, “We really appreciate your interest”, “Please feel free to contact us if you have any further questions regarding the same.”

In email, some of this is normal courtesy. In chat it reads differently. The visitor is already in a conversation with you; they don’t need to be thanked for starting it, and they know they can ask more because the chat box is right there. Filler also makes replies feel automated, which is the opposite of what you want.

Warmth in chat comes from three things, none of which cost lines:

  • Using their name once, near the start, if you have it.
  • Answering their exact situation, not a general version of it.
  • A friendly next step, such as “Happy to check that for you.”

If a reply feels cold after you remove the filler, add one short warm phrase, not three. “Good question” or “Sure” at the start is enough. Our guide on sounding human in live chat has more examples.

AI replies

Keeping AI-written chatbot answers short

If you use an AI assistant to reply, its length depends on two things: the instructions you give it and the knowledge it answers from.

Instructions first. Most AI chat tools let you describe how replies should sound. Ask for short, specific replies in plain words: “Answer in 2 to 3 short sentences. Put the answer first. End with a question or a next step when useful. Link to the page for full details.” That one paragraph changes length more than anything else.

Knowledge second. An AI tends to mirror the style of the text it reads from. If your FAQ answers are long paragraphs, AI-written chatbot answers will be long paragraphs too. Rewriting your knowledge so each answer starts with the direct fact, followed by conditions, helps the AI pick out the short version. Our guide to writing knowledge your bot can use covers how.

LiveChatBot’s AI Agent answers from the knowledge you give it and hands over to your team when it can’t help. When the AI isn’t available, the free keyword bot answers from your saved replies, so the same length rules apply to saved replies. Write both to fit a phone screen and visitors get a consistent experience either way. The AI Agent page explains how the two work together.

Links and lists

Using links, lists and numbers in small bubbles

Three small formatting choices make a big difference inside a narrow bubble.

Links. A full URL can take three lines on its own. Where your chat tool supports link text, use short words like “returns page”. Where it doesn’t, link to a short page address rather than a long one with tracking codes. Always say what the link is before it, so the visitor knows why to tap it.

Lists. A list of three options reads well on a phone if each item is short: “Small ₹299, Medium ₹399, Large ₹499.” A list of five long items does not; send the link to the page instead. Commas and line breaks are usually enough; you rarely need bullet symbols in chat.

Numbers. Write numbers as digits, not words. “2 to 3 days” scans faster than “two to three days”, and “₹999” is shorter than “nine hundred and ninety-nine rupees”. Put the number early in the sentence, where the eye lands first.

One more point: emoji. One emoji can replace a few words of warmth. Several in a row take up a line and look noisy on small screens. Use them sparingly, if at all, and never in complaint replies.

Quick reference

Before and after: five common replies

Opening hours
🚩 Too longThank you for asking! Our store timings are from 10 in the morning till 8 in the evening on all weekdays and Saturday as well.
✅ Phone-friendlyWe’re open 10 am to 8 pm, Monday to Saturday. Closed Sundays. Planning a visit today?
Free delivery
🚩 Too longWe are happy to inform you that we offer free delivery on all orders which are above the value of Rs 999 across India.
✅ Phone-friendlyDelivery is free on orders over ₹999. Below that it’s ₹60. Want me to check your cart?
Returns
🚩 Too longAs per our return policy, which you can find on our website, returns are accepted within a period of 7 days from the date of delivery.
✅ Phone-friendlyYou can return items within 7 days of delivery. Sale items can only be exchanged. Shall I start a return?
Order status
🚩 Too longWe understand your concern regarding your order and we would request you to kindly share the order number so we can check.
✅ Phone-friendlySorry for the wait. Share your order number and I’ll check where it is.
Price question
🚩 Too longThe price of the product varies depending on the size and the material that you choose at checkout.
✅ Phone-friendlyPrices start at ₹1,200 for small and go up to ₹2,800 for large. Which size are you looking at?

Testing

Read every reply on a real phone

The cheapest test is the best one. Open your own website on your phone, start a chat, and ask the ten questions customers ask most. Read each reply with the keyboard open, because that’s how visitors see it.

Look for four things:

  1. Does the answer appear in the first two lines?
  2. Is any reply longer than the visible chat area?
  3. Do links and prices break awkwardly across lines?
  4. Is there a clear next step at the end?

Fix the replies that fail, then test again. It’s also worth asking someone outside your business to do the same test, since you know the answers already and will skim. Our chat test with 15 questions gives a ready list to try.

Repeat the check whenever you add new saved replies or change the AI’s instructions. Long replies tend to creep back in over time as different people add content.

Getting started

Fix your ten most-sent replies today

You don’t need to rewrite everything at once. Start with the ten replies your bot or team sends most often, because they’re the ones most visitors read. Paste each into the bubble fitter above, move the answer to the front, remove filler, add a next step and split anything over four lines.

Short, front-loaded chatbot answers make every other part of your chat work better: visitors understand faster, ask fewer repeat questions and move to the next step sooner.

LiveChatBot includes saved replies, an AI Agent that answers from your knowledge, and an inbox plus Android app for your team, all on a free plan covering two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.

Frequently asked questions

How long should chatbot answers be on mobile?

For simple facts, 15 to 25 words, which is two or three lines in a phone bubble. Even for complex topics, keep each bubble to about four lines and link to a page for the full details.

Is it rude to skip the greeting in a reply?

Not in chat. The visitor is already talking to you. Lead with the answer, and add one short warm phrase or use their name if the reply feels cold.

Should I split a reply into several messages?

Split at a change of job, such as answer then next step. Two bubbles, occasionally three, is the comfortable maximum.

How do I make AI replies shorter?

Ask for two or three short sentences with the answer first in the instructions, and rewrite long knowledge paragraphs so each starts with the direct fact.

Do the same rules apply to saved replies?

Yes. Saved replies are read in the same narrow bubble, so the same length budget and order apply.

More to read

More guides on this topic

📘

Chatbot Responses That Answer the Question Asked: Match Every Reply to the Message Type, From Yes/No to ‘Where Is My Order?’ (Free Response Fit Checker)

Read the guide →

Write replies that fit the screen

Answer first, condition second, next step last, in two to four lines. Start free on livechatbot.in.