Bot AI Chat Number Check: Test Every Price, Date and Limit Your Bot Quotes Before Customers Do
Bot AI chat mistakes that hurt most are rarely about tone. They’re about numbers: a delivery time that’s two days too short, an old price, a return window from last year’s policy, a COD limit that changed. Customers screenshot numbers and hold you to them. This guide shows why numbers go wrong, how to find every number your bot can quote, how to remove conflicts, and how to retest after each change, with a free tool that pulls the numbers out of your text and writes the test questions for you.
⚡ In short
- Most costly bot mistakes involve numbers: prices, days, limits, hours and phone numbers.
- The usual cause is two versions of the same fact in the bot’s knowledge, an old one and a new one.
- List every number, keep one value per fact, and write a test question for each.
- Retest the number list after every price or policy change. It takes ten minutes.

Why numbers
Customers forgive a clumsy sentence, not a wrong price
When an AI assistant answers a question about your business, it combines the words in the question with the knowledge you gave it. For most answers, small differences in wording don’t matter. “We deliver across Pune” and “Delivery is available everywhere in Pune” mean the same thing.
Numbers are different. “Delivery in 2 days” and “delivery in 5 days” are both reasonable sentences, and an AI has no way to know which one is current unless your knowledge makes it clear. The same goes for prices, discount percentages, opening hours, return windows, COD limits and phone numbers. A bot that quotes the wrong one sounds just as confident as a bot that quotes the right one.
And numbers are what customers act on. They plan a gift around the delivery date. They pay because the free-shipping threshold was ₹999. They return an item on day 9 because the bot said 10 days. When the number turns out wrong, the conversation becomes a complaint, often with a screenshot.
That’s why a bot ai chat number check is worth doing before launch and after every change. It’s the highest-value ten minutes of bot testing you’ll do.
Where conflicts come from
Two versions of the truth, both in the knowledge
Wrong numbers usually come from the same source: the bot was given two versions of a fact.
- An old FAQ and a new policy page. The FAQ still says returns within 7 days; the updated policy says 10.
- A sale banner left in the knowledge. “Free shipping over ₹1,499 this Diwali” stays in the text long after Diwali.
- Different pages written at different times. The home page says “same-day delivery in Pune”; the shipping page says “1 to 2 days”.
- Copied documents. A price list PDF from last year sits next to this year’s website text.
An AI assistant given conflicting facts may pick either one, and it may pick differently on different days. Rewording the question can change which version comes back. This is one reason testing with a single question can give a false sense of safety.
The fix isn’t a cleverer bot. It’s cleaner knowledge: one value per fact, written in one place, with old versions deleted rather than left beside the new ones. Our knowledge audit guide covers how to choose which pages and documents to keep.
Free tool
Find every number in your bot’s knowledge
Paste your FAQ, policy or price text. The tool lists each price, time, day count, percentage and phone number, flags likely conflicts, and gives you a test question for each.
Paste the text your bot learns from (FAQ, policy page, price list)
Runs only in your browser; your text is not sent or saved. It finds numbers by pattern, so read the list with common sense.
Make a fact sheet
One line per fact, one value per line
Once you have the list of numbers, turn it into a short fact sheet. This is a plain document, separate from your website, that says the current value of every number the bot might quote. It becomes the single source of truth for your bot, your staff and your website.
A good fact sheet line has four parts:
- The fact: “Free shipping threshold”.
- The value: “₹999”.
- Any condition: “Prepaid orders only; not on furniture”.
- The date checked: “Checked 20 Oct”.
Keep it to the numbers that matter to customers: prices or price ranges, delivery times by area, free-shipping and COD limits, return and exchange windows, opening hours, phone numbers and any fees. A small business often ends up with somewhere between 15 and 30 lines.
Then go back to the bot’s knowledge and make every number match the sheet. Delete old versions rather than adding “updated” notes. If you’re unsure whether a page is still used, take it out of the knowledge; you can always add it back.
LiveChatBot’s AI Agent answers from the knowledge you give it, so a clean fact sheet directly improves its answers. When the AI isn’t answering, the free keyword bot uses your saved replies, so update the matching saved replies at the same time. The AI Agent overview explains how the two work together.
Test questions
Ask each number three ways
A single test question per number isn’t enough, because customers phrase things differently. For each number on your fact sheet, ask the bot three versions:
- The direct question. “How many days do I have to return something?”
- The situation question. “I got my order on the 3rd. Can I still return it on the 12th?”
- The edge question. “Can I return a sale item?” or “Does free shipping apply to COD?”
The direct question checks the number. The situation question checks whether the bot applies it correctly. The edge question checks whether it knows the conditions, or at least says it needs to check.
Mark each answer pass or fail. A pass gives the right number, applies it correctly or says honestly that a person needs to confirm. A fail quotes a wrong number, applies it wrongly or invents a condition.
Hours and dates
The numbers that change with the calendar
Some numbers change predictably: holiday hours, festival delivery delays, sale prices and seasonal cut-off dates. These are the ones most often left behind after the date passes.
Handle them with a simple rule: every time-limited number goes into the knowledge with its end date written in the sentence. “Diwali offer: free shipping on orders over ₹499 until 2 November” is safer than “Free shipping over ₹499”, because the AI and your staff can both see when it ends. Better still, put a reminder in your calendar on the end date to remove it.
Opening hours deserve their own care. If your chat tool has an opening hours setting, as LiveChatBot does, let that setting decide when the widget shows people as available, and keep the hours in the knowledge text the same. When they disagree, the visitor gets mixed messages: the bot says “we’re open now” while the widget says “away”. Our guide to opening hours covers the setting.
For festival delivery delays, it’s often best to tell the bot to give the normal time plus a clear warning: “Delivery usually takes 2 to 3 days; during festival weeks it can take longer. A person can confirm for your pin code.” An honest range beats a precise wrong number.
Ranges and conditions
When the honest answer isn’t one number
Many numbers depend on something: delivery time depends on the pin code, the price depends on the size, the return window depends on the category. If your knowledge gives only one number, the bot will apply it to every case.
Write conditions into the sentence. Instead of “Delivery takes 2 days”, write “Delivery takes 2 days within Pune city, 3 to 5 days elsewhere in Maharashtra, and 5 to 8 days for other states.” Instead of “Returns within 10 days”, write “Returns within 10 days for clothing; electronics can only be replaced if faulty.”
Where the condition is too complex, such as exact delivery dates for every pin code, tell the bot not to guess: “If a customer asks for an exact delivery date, ask for the pin code and say a team member will confirm.” Then make sure someone actually does. The away form and tickets help when nobody is online; see turning a chat into a ticket.
A bot ai chat that says “it depends on your pin code; share it and we’ll confirm” is less impressive than one that gives a confident number. It’s also the one that doesn’t create refunds and complaints.
After every change
A ten-minute retest routine
Numbers break when the business changes, and a bot ai chat only knows what you last told it: a new price list, a new courier, new hours, a new return policy. Build a small routine so the bot keeps up.
- Update the fact sheet first. Change the value and the date checked.
- Search the knowledge for the old value. Paste the knowledge text into the number finder above and look for the old number. Remove every copy.
- Update matching saved replies. Staff and the keyword bot use them.
- Update the website page. Customers who read the page and ask the bot should see the same number.
- Run the three test questions for the changed fact.
Ten minutes, and the bot is safe again. If you change many numbers at once, at the start of a sale, for example, run the full test list. Our golden-question regression testing guide shows how to keep a reusable list of test questions for exactly this.
Keep the test results somewhere simple, like a spreadsheet with a column per test date. When something goes wrong later, you’ll be able to see when the answer changed.
When a wrong number gets out
Fix it, honour it, and learn from it
Even with good checks, a wrong number will sometimes reach a customer. How you handle it matters more than the mistake.
Honour it if you reasonably can. If the bot quoted free shipping at ₹999 and the threshold is now ₹1,499, the gesture of honouring it for that customer usually costs less than the complaint, and it builds trust.
Fix the source the same day. Find the old number in the knowledge, delete it, and retest.
Check for others. If one customer got the wrong number, others might have too. Search recent chats for the old value in the inbox.
Tell the team. Staff should know about the fix so they don’t repeat the old number from memory.
Finally, look at why the old number survived. Was it in a document nobody remembered? Was the sale end date not written down? Each answer improves your routine.
Getting started
Run the check today
Copy your FAQ page, shipping policy, return policy and price list into one text file. Paste it into the number finder above. Fix the conflicts it flags, make a fact sheet, and ask the bot three questions per number. Most small businesses can do this in under an hour, and it removes the most expensive kind of chatbot mistake.
If you’re setting up a bot for the first time, LiveChatBot’s AI Agent answers from the knowledge you provide and hands over to your team in the inbox or the Android app when it can’t help. The free plan covers two websites with 100 visitors per website each month. See pricing and start at livechatbot.in. Our guide to training your AI chatbot covers the rest of the knowledge setup.
Frequently asked questions
Why does my bot ai chat give different numbers for the same question?
Usually because its knowledge contains two versions of the fact, such as an old FAQ and a new policy. Keep one value per fact and delete the old one.
Which numbers should I test first?
The ones customers act on: prices, delivery times, free-shipping and COD limits, return windows, opening hours and phone numbers.
How often should I retest?
After every price, policy or hours change, and once a month as a routine. A focused retest takes about ten minutes.
Should the bot give exact delivery dates?
Only if your knowledge has exact, current rules. Otherwise it should give the usual range and offer to confirm for the customer’s pin code.
What if the bot already quoted a wrong price?
Honour it for that customer if you reasonably can, fix the source the same day and check recent chats for others who got the same answer.
Keep reading
Related guides
Best Website for Chatting With Your Customers Is Your Own: Pull Enquiries Off DMs and Into One Inbox
Best Live Chat for Website Switchers: Move From Your Current Tool in a Weekend Without Losing Replies or Leads
Best Live Chat Apps for Replying From Your Phone: A 10-Test Field Trial You Can Run in an Evening
Give your bot one version of every number
Make a fact sheet, test each number three ways and retest after changes. Start free on livechatbot.in.