How Long Should a Chatbot's Answers Be? Writing Replies People Actually Read

A support chatbot's answer should usually be one to four sentences, with the answer itself in the first one. Use a short list when the visitor needs steps or options, link to the page instead of pasting it, skip the preamble, and when a question is too vague to answer, ask one short question back. People open a chat to get an answer, not to read an article in a small window.

I build ChatBento, an AI support chatbot for small-business websites. Its built-in reply style says replies should be "one to four sentences, or a short list when listing steps or options. No preamble." This post explains why I set it that way, what the research says, and how to steer your own bot's replies, with six rewrites you can copy the pattern from.

What does the research say about chatbot answer length?

In April 2026, Nielsen Norman Group published Less Chat, More Answer, a usability study of site-specific AI chatbots: nine participants each tried two or three of eight bots on realistic tasks. It's a small qualitative study, so read it as direction rather than measurement. But the direction is clear:

• Participants typed short, keyword-like questions and skipped the pleasantries. In the authors' words: "A longer answer was not a better answer."
• In a small chat window, even a short paragraph can look like a wall of text. They recommend short sentences and paragraphs of no more than two or three sentences, with lists and bold text for longer answers.
• Long answers streamed in word by word can add to the sense of overload.
• The structure they recommend: give the essential answer first, then offer more detail if the visitor wants it.
• Clarifying questions help with ambiguous queries but add friction, so use them sparingly.
• When a bot can't help, it should say so plainly instead of padding around the gap.

On reading itself, an earlier NN/g study of reading content on mobile devices (Kate Moran, 2016) found comprehension on phones was about the same as on computers for easy text, but hard passages took longer to read on a phone. Many of your visitors will meet your chatbot on a phone. Short and plain is the safe default.

The rules I use

1. Put the answer in the first sentence

If the question has a yes, a no, a number or a date in it, that goes first. Context and conditions come after. A visitor who reads only the first line should still leave with the answer.

2. One to four sentences

That covers almost every support question: the answer, the main condition, and where to go next. Needing more usually means the question is really two questions, or the visitor should be reading a page.

3. Use a list for steps and options, nothing else

A list helps when order matters (how to return an item) or when the visitor is choosing (which plan, which service). It doesn't help for a single fact. A one-item bullet list is just a sentence with extra punctuation.

4. Link to the page instead of pasting it

Your shipping page, your full terms, your size guide: the bot should give the key point and the link. The visitor gets the answer now and the full detail if they want it. ChatBento's bot can include full links that appear in your content, so make sure the pages you want it to point to are in its training.

5. Don't repeat the question or warm up

"Great question!", "You're asking about...", "I'd be happy to help with that" all push the answer down a line on a small screen. Friendliness belongs in the wording of the answer, not in a sentence before it.

6. Ask one clarifying question when the question is vague

"How much?" on a site with three services can't be answered well. One short question, ideally with the options named, beats a long answer covering every possibility. One, not a questionnaire.

7. Say "I don't know" early

If your content doesn't cover it, the first sentence should say so, followed by what the visitor can do next. A fallback message buried under a paragraph of loosely related information wastes their time and reads as evasive.

Six before-and-after rewrites

These are invented examples for made-up businesses, written to show the pattern.

1. Preamble and a repeated question

Visitor: do you deliver on sundays

Before: Great question! You're asking whether we deliver on Sundays. We know how important it is to get your flowers on time, especially for special occasions. Our delivery days are Monday to Saturday, so unfortunately we don't deliver on Sundays at the moment.

After: No, we deliver Monday to Saturday. For a Sunday occasion, order by 2 p.m. on Friday and we'll deliver on Saturday.

2. Steps buried in prose

Visitor: how do I return something

Before: To return an item you'll first want to make sure it's within 30 days of delivery and unworn with the tags on, and then you can go to the returns page where you enter your order number and email, after which you'll get a label to print, and once you've packed it you can drop it at any post office.

After: You can return unworn items with tags within 30 days of delivery:

• Enter your order number and email on the returns page: https://example.com/returns
• Print the label we email you
• Drop the parcel at any post office

3. Pasting the policy instead of linking it

Visitor: can I cancel my booking

Before: (the whole cancellation policy, five paragraphs, copied from the terms page)

After: Yes. Cancel at least 48 hours before your appointment for a full refund; later cancellations are charged 50%. The full terms are here: https://example.com/terms

4. A vague question answered with everything

Visitor: how much

Before: A paragraph each on window cleaning prices, gutter cleaning prices and pressure washing prices, with all the conditions.

After: Which service do you mean: window cleaning, gutter cleaning or pressure washing?

5. "I don't know" hidden at the end

Visitor: is there parking near you

Before: We're located on the high street in the town center, close to several shops and cafes, and we're easy to reach by bus. I don't have specific information about parking.

After: I don't have information about parking, sorry. The team can tell you: leave your email in the form below and they'll get back to you.

6. Options as one long sentence

Visitor: which plan is right for a small team

Before: It depends on your needs, because the Starter plan is good for one person and includes basic features, whereas the Team plan covers up to five people and adds shared projects, and the Business plan is for larger companies that need admin controls.

After: For a small team, it's usually Team (up to 5 people, with shared projects). The others:

• Starter: one person
• Business: larger companies that need admin controls

How do you steer reply length with instructions?

Most AI chatbot tools let you add your own rules to the bot's system prompt. In ChatBento they're called Instructions and live in the Settings tab. The built-in rules already ask for short, plain replies with no preamble, so you don't need to repeat that. Use your lines to refine it for your visitors:

• "Put the direct answer in the first sentence, then the main condition."
• "When a page covers the details, give the key point and the link to that page."
• "If a question could mean more than one of our services, ask which one before answering."
• "For step-by-step questions, use a short bulleted list."
• "Don't end every reply with a question."

Avoid lines that fight the built-in style, like "Always explain in full detail". You can't predict which rule wins in a given chat. My guide to writing chatbot instructions has more examples, and the free instructions generator builds a starting block.

Shape your content, not only your rules

Instructions change how the bot says things. Your content decides what it has to work with. In my experience, a Q&A whose first sentence is the answer ("Yes, we deliver to Canada. Shipping is $15 and takes 5 to 8 working days.") produces a cleaner reply than a paragraph where the answer sits in the middle. When you write Q&As, write them the way you want the bot to answer: short, answer first, in the visitor's words. How to train an AI chatbot on your website covers the rest of the content side.

When is a longer answer right?

Sometimes. A visitor who asks "can you explain how the whole process works, from quote to install?" has asked for detail. Even then, keep the structure: a one-line summary first, then a short list of the stages, then the link to the page that explains each one. And if the honest answer needs a conversation (a complaint, a custom quote, anything about their own order), the right reply is short too: say a person is better placed to help and hand it off.

How to check your bot's replies

Once a week for the first month, read ten real conversations on your phone, not your desktop, and ask:

• Is the answer in the first sentence?
• Could any sentence be cut without losing anything?
• Is there a list where there should be one, and none where there shouldn't?
• Did it link to a page instead of pasting it?
• When it didn't know, did it say so first?

Fix patterns, not single replies: if three answers open with a warm-up line, that's one instruction to add, not three rewrites.

The short checklist

• Answer in the first sentence
• One to four sentences for most replies
• Lists only for steps and options
• Links to pages instead of pasted text
• No "Great question!" and no restating the question
• One clarifying question when the question is vague
• "I don't know" stated first, with the next step
• Replies checked on a phone screen

If you want a head start on the rules, try the chatbot instructions generator, and read the system prompt entry to see where your instructions sit in what the bot is told.