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)

Chatbot responses usually go wrong in a quiet way: the reply is polite, correct and on topic, but it answers a different question from the one the visitor asked. Someone asks “do you deliver to Coimbatore?” and gets a paragraph about your commitment to customers. This guide sorts visitor messages into seven types, shows what a reply to each type must contain, and covers the two types where a wrong reply causes real damage: order questions and complaints. A free tool checks your own message and reply pairs.

👤 What the visitor seesIllustrative: same question, two replies
do you deliver to coimbatore?
🤖 MissesThank you for reaching out! We are committed to serving customers across the country.
do you deliver to coimbatore?
🤖 FitsYes, we deliver to Coimbatore in 3 to 5 working days. Want me to check your pin code?

Both replies are polite. Only one answers.

⚡ In short

  • A reply fits when it gives the visitor the thing their message type asks for: a yes or no, a number, a time, a place, a person.
  • Yes/no questions get yes or no in the first three words. Price and time questions get a number in the first line.
  • Messages about a specific order never get an invented status. The bot hands over or collects what your team needs.
  • Complaints get one line of acknowledgement before any policy, and a clear next step.
Chatbot responses 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.

The problem

A polite reply can still miss the question

Most advice about bot replies is about tone: be friendly, be short, use the customer’s name. That matters, but it isn’t why visitors give up. They give up when they ask something simple and the reply doesn’t contain the answer.

Look at what visitors actually type into a website chat. “cod?” “price of 3 seater” “open sunday?” “where is my order”. Each of those messages has a shape. “cod?” wants a yes or a no. “price of 3 seater” wants a number. “open sunday?” wants a time or a “closed”. “where is my order” wants a status the bot usually can’t see, which means it wants a person.

A reply can be well written and still ignore that shape. “We offer flexible payment options to suit every customer” is a fine sentence. It is also useless to someone who typed “cod?”, because they still don’t know whether cash on delivery is available. They will either ask again, which makes the chat feel slow, or leave.

This happens with every kind of bot. Keyword bots send the reply attached to the keyword, whatever the actual question was: the word “delivery” triggers the delivery reply even when the visitor asked “my delivery is late, who do I call?”. AI bots are better at reading the question but drift into long, general answers when their knowledge is vague, or confidently fill gaps with guesses.

The fix is the same for all chatbot responses, whichever kind of bot sends them. Before you write or approve a reply, decide what type of message it is answering, and check that the reply contains the one thing that type needs. That check takes seconds once you know the seven types, and it catches most of the replies that make a bot feel unhelpful.

Seven types

What each kind of message needs in the reply

Message typeTypical wordingThe reply must containUsually goes to
Yes/no“cod available?”, “do you ship abroad?”Yes or no in the first three words, then one detailBot
Price or charge“how much is shipping”, “kitna hai”A number or range, with what it depends onBot
Time or timing“kab tak aayega”, “open sunday?”A time, a day or a number of daysBot
Place or area“deliver to Kochi?”, “where is your shop”Yes/no for the area, or the addressBot
Their own order or account“where is my order”, “money deducted”No invented status; who will check and howPerson
Complaint“arrived broken”, “worst service”One line of acknowledgement, then a next stepPerson, often
Asks for a person“talk to a human”, “call me”A handover, or a way to leave a contactPerson

Yes/no and area questions

Lead with the answer word

The single most common miss is a yes/no question that gets an explanation instead of a yes or a no. “Do you deliver to Coimbatore?” is answered by “Yes”, and the useful detail comes after it: “Yes, in 3 to 5 working days.” If the reply starts with background (“We ship through trusted courier partners across India…”), the visitor has to read to the end to find out whether the answer is yes, and sometimes it never says.

Write yes/no replies in this order:

  1. The answer word. Yes, no, not yet, only on orders above a certain amount.
  2. The one detail people ask next. For delivery that’s the number of days; for COD it’s the limit; for “do you have it in blue” it’s the sizes in stock.
  3. An optional next step. “Want me to check your pin code?” Only add this if the bot or your team can actually do it.

“No” deserves the same treatment. “No, we don’t deliver outside India yet” is a good reply. It’s honest, it’s quick, and the visitor can move on. Hiding a no inside a long paragraph doesn’t soften it; it only wastes the visitor’s time and makes them ask again.

Area questions (“do you deliver to…”, “is there a branch near…”) behave like yes/no questions with a place attached. If your answer depends on the pin code, say that plainly and ask for it, rather than listing every city you serve.

Short messages with a question mark (“cod?”, “emi?”, “parking?”) are almost always yes/no questions too. Treat them that way, even when the wording isn’t a full sentence.

Price and time questions

Put the number in the first line

When a visitor asks “how much” or “how long”, the reply needs a number. Not a promise to discuss pricing, not “it depends”, not a link to a page. A number, or a range with what it depends on.

“Shipping is free above ₹999; below that it’s ₹60” fits. “Our shipping charges are calculated based on several factors” misses. The second reply may be technically true, but it doesn’t help anyone decide anything. If the price genuinely varies, give the range and the factor: “Stitching starts at ₹450 for a plain blouse; designs with work cost more. Share a photo and our team will quote.” (Illustrative figures.)

The same goes for time. “kab tak deliver hoga” wants “3 to 6 working days”, ideally followed by an offer to check for the visitor’s pin code. “Open sunday?” wants “Yes, 10 am to 2 pm” or “No, we’re closed on Sundays; we reopen Monday at 10 am.”

Two traps catch a lot of businesses here.

Prices that change

If a price changes often, the bot’s answer will go stale. Either give a “starts from” figure you’re happy to honour, or say that prices change and hand over for a quote. A wrong number is worse than no number, because the visitor may hold you to it.

Times you can’t promise

If delivery depends on the courier, say “usually” and give the typical range. Don’t promise a date the bot can’t guarantee. And don’t let the bot answer “when will *my* order arrive” with the general delivery time as if it were a status; that’s an order question, covered below.

Free tool

Check whether your chatbot responses fit the message

Paste pairs of visitor messages and bot replies. The checker works out what type each message is, then checks the reply for the one thing that type needs, and flags invented order statuses, missing acknowledgements, filler and dead ends.

Paste message and reply pairs. Start the visitor’s message with V: and the bot’s reply with B:. Leave a blank line between pairs.

Runs only in your browser; nothing is sent or saved. Remove names, phone numbers and order IDs before pasting.

Order and account messages

Never invent a status

Messages about the visitor’s own order, payment, booking or account are a different kind of question. “Where is my order?” isn’t asking how long delivery usually takes. It’s asking about one specific parcel, and unless your bot is connected to your order system, it has no idea where that parcel is.

This is where the most damaging replies come from. A bot that answers “Your order has been shipped and will arrive soon!” sounds helpful. If the order hasn’t shipped, you’ve now told a paying customer something false, in writing, and they’ll come back angrier when it doesn’t arrive. AI bots are especially prone to this: asked about a specific order, a model with no order data may produce a plausible-sounding status rather than admit it can’t see one.

The safe pattern is simple:

  • Say what the bot can’t do, briefly. “I can’t see individual orders from here.”
  • Say who can, and when. “Our team checks orders between 10 am and 7 pm.”
  • Collect what they’ll need. An order number and a phone number or email, so the team can reply even if the visitor leaves.

Payment problems (“money deducted but order not placed”) need the same handling, plus one more rule: the bot must never ask for an OTP, card number, CVV or UPI PIN. Your team never needs those to look into a failed payment, and asking for them teaches customers a habit scammers exploit.

In LiveChatBot, these chats go to your team in the inbox. Outside your opening hours the away form collects an email or phone number, and the message can become a ticket with an owner, so nothing gets lost overnight. Our guide on turning a chat into a support ticket shows how. Teach your AI knowledge a plain rule too: “The bot cannot see order status. For questions about a specific order, ask for the order number and pass the chat to the team.” See how to train your AI chatbot.

Complaints and requests for a person

Acknowledge first, then hand over

Complaints

“The mug arrived broken” is not a question about your return policy, even though the return policy is part of the answer. A reply that goes straight to “Returns are accepted within 7 days of delivery” reads as cold, and sometimes as a brush-off. The visitor needs to know you’ve registered the problem before you tell them the rules.

One line is enough: “Sorry it arrived like that.” Then the next step: “Could you share a photo? Our team will arrange a replacement.” Don’t over-apologise, don’t write three sentences of regret, and don’t promise a refund the bot can’t authorise. Complaints often need a person’s judgement, so the next step usually involves your team.

Requests for a person

“Can I talk to a person?” has one correct reply: a handover. Not a menu of things the bot can help with, not “I can answer that too!”, and certainly not the same reply repeated. Visitors who ask for a person and get the bot again tend to leave, and they remember it.

If someone is online, connect them. If nobody is online, say so honestly and offer a way to be reached: “Our team is offline right now. Leave your number or email and we’ll reply in the morning.” In LiveChatBot, opening hours control when the away form appears, so the bot doesn’t promise a live person at 2 am.

Watch for indirect versions too: “call me”, “customer care number?”, “is anyone there?”, “baat karni hai”. They all mean the same thing. The checker above treats these as requests for a person.

Rewrites

Six replies that missed, and versions that fit

“cod available?”
🚩 Missed“We offer multiple convenient payment methods for your ease.”
✅ Fits“Yes, cash on delivery is available on orders up to ₹5,000.” (Illustrative limit.)
“how much for a website?”
🚩 Missed“Our pricing is customised to your requirements.”
✅ Fits“Basic sites start at ₹15,000. Tell me how many pages you need and I’ll get you a closer figure.” (Illustrative.)
“where is my order”
🚩 Missed“Your order is on its way!”
✅ Fits“I can’t see individual orders, but our team can. What’s your order number? They check orders from 10 am to 7 pm.”
“the mug arrived broken”
🚩 Missed“Returns are accepted within 7 days.”
✅ Fits“Sorry it arrived like that. Could you share a photo? Our team will sort out a replacement.”
“can i talk to a person”
🚩 Missed“I can help with delivery, returns and payments!”
✅ Fits“Sure, I’ll pass you to our team now.” Or, offline: “They’re offline right now. Leave your number and they’ll call you back.”
“open sunday?”
🚩 Missed“Sorry, I didn’t understand that.”
✅ Fits“Yes, Sundays 10 am to 2 pm. Weekdays we’re open 10 am to 8 pm.”

When the bot doesn’t know

The honest no-match reply

Some messages won’t match anything the bot knows. That’s normal, and it’s fine, as long as the reply doesn’t end the conversation.

“Sorry, I didn’t understand that” is the classic dead end. It tells the visitor nothing about what to do next, and when it’s repeated it makes the whole chat feel broken. A good no-match reply does three things: admits the bot doesn’t have the answer, says what it can help with, and offers a person.

“I don’t have an answer for that one. I can help with delivery, returns and payment, or I can pass you to our team. Which would you like?”

If the same visitor hits no-match twice in a row, stop trying and hand over. Asking them to rephrase a third time is the point where most people close the window.

Treat every no-match as a note for your next update. If several visitors ask about gift wrapping and the bot has nothing, that’s a missing answer, not a visitor problem. Our Q&A sheet guide shows how to add new pairs without creating overlaps, and the chatbot dialogue examples cover confused, off-topic and silent visitors in more detail.

Setting it up

Where your chatbot responses live in LiveChatBot

Once you’ve checked your replies, put them where the bot and your team can use them.

  • AI Agent knowledge. The AI Agent answers from the knowledge you give it. Write facts in the shape the replies need: numbers for prices and times, plain yes/no statements for availability, and explicit rules for order and payment questions (“cannot see order status; ask for the order number and hand over”). There’s a small free monthly allowance per website, then AI packs.
  • Saved replies. Save the fitted replies as saved replies. When AI replies aren’t available or the allowance is used up, the free keyword bot answers from saved replies, and your team can send the same text in one click, with {name} for the visitor’s name. See using saved replies.
  • Opening hours and the away form. So “talk to a person” outside hours gets an honest reply and a way to leave a contact.
  • Tickets. So order questions and complaints that arrive overnight have an owner the next morning.

Then test. Type each message type into your own widget, in the way customers write it, typos and Hinglish included, and paste the replies into the checker. For the questions the bot asks visitors rather than answers, see our chatbot questions examples; for the opening and closing lines, see bot messages examples.

Checklist

Before a reply goes live

Reply check

Getting started

Check ten replies today

Open your widget, ask the ten questions customers ask you most, and copy each question and the bot’s reply into the checker as V: and B: lines. Fix every reply marked Misses before you touch tone or wording. Then save the fixed versions as saved replies so the keyword bot and your team give the same answers.

LiveChatBot’s free plan includes the AI Agent with a small monthly allowance, the free keyword bot, the team inbox, the Android app, Flows, opening hours with an away form and tickets, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.

Frequently asked questions

What makes good chatbot responses?

A good reply gives the visitor the thing their message type asks for, in the first line: yes or no, a number, a time, a place or a person. Tone and length come second; a friendly reply that doesn’t answer still fails.

Should a chatbot answer questions about a specific order?

Only if it’s connected to your order system. Otherwise it should say it can’t see individual orders, collect the order number and a contact, and hand the chat to your team. It should never guess a status.

How long should a bot reply be?

Most chat replies work best under about 40 words: the answer, one detail and an optional next step. Longer replies are fine when the visitor asked for detail.

What should the bot say when it doesn’t understand?

Admit it doesn’t have that answer, say what it can help with, and offer a person. If it misses twice in a row, hand over instead of asking the visitor to rephrase again.

Does the fit checker send my replies anywhere?

No. It runs entirely in your browser using simple wording rules, and nothing is sent or saved. Remove personal details before pasting anyway.

Keep reading

Related guides

📘

Chatbot Questions Examples, Judged by the Reply They Get: 40 Bot Questions in Six Formats, Weak vs Strong (Free Reply Predictor)

Read the guide →

🧭

Chatbot Questions and Answers Sheet: Write Q&A Pairs That Don’t Overlap, Contradict or Leave Gaps (Free Q&A Set Checker)

Read the guide →

🛠️

Chatbot Questions Worth Automating: Score Each One by Volume, Stability and Risk, and See the Hours It Saves (Free Question Scorer)

Read the guide →

Replies that answer the question

Give the AI Agent the facts it needs, save fitted replies for the keyword bot and your team, and hand order questions to people. Start free on livechatbot.in.