A chatbot that says "I don't know" is worth more than one that guesses
Customers forgive a bot that hands them to a person. They do not forgive one that invents a refund policy. Here is how we keep business chatbots grounded in what the business actually says.
Large language models are very good at sounding right. Ask one about your return policy and it will give a confident, well-written answer, whether or not your business has that policy. For a customer-facing chatbot, that fluency is the risk.
The goal is not a bot that can talk about anything. It is a bot that answers what the business has written down, does the actions it is allowed to do, and hands everything else to a person.
Answer from your documents, not from memory
The common pattern is called retrieval-augmented generation. In plain words: when a question comes in, the system first searches your own material (policies, price lists, product pages, FAQs) for the passages that match, and then asks the model to answer using only those passages.
- The bot can quote the policy page it used, so staff can check where an answer came from.
- Updating the bot means updating a document, not retraining a model.
- If the search finds nothing relevant, the bot knows it has no basis for an answer.
Search first, answer from what was found, and hand over when nothing was found.Let rules handle numbers
Prices, balances, stock levels and delivery dates should never come from a language model's guess. We fetch them from the real system and give them to the model as facts, or skip the model entirely for those answers.
Who should answer which kind of question in a business chatbot.| Question | Answered by | Why |
|---|
| What is your return policy? | Model, from the policy document | Wording varies, the source is fixed |
| Where is my order? | Order system lookup | Must be exact and current |
| How much is the 2 kg pack? | Price list lookup | Prices change, guesses are costly |
| I want to complain about a rider | Handover to a person | Needs judgement and follow-up |
Design the handover first
When to hand over
The handover to a person is not a failure path; it is a feature. A good one passes the whole conversation along, so the customer never repeats themselves, and it happens early, before the customer gets frustrated.
- Hand over when the search finds nothing, when the customer asks for a person, or when the topic is a complaint, a refund or a legal matter.
- Outside working hours, take the details and promise a callback rather than pretending to resolve it.
- Log every handover. The most common reasons show which documents to write next.
The best measure of a support bot is not how much it answers. It is how rarely it answers wrongly.
Test it like a customer would
Before launch we write a test list of real questions, including the awkward ones: misspellings, Roman Urdu, two questions in one message, questions about competitors, attempts to make the bot promise a discount. Every release is checked against that list.
Frequently asked questions
Can it run on WhatsApp?
Yes. The same assistant can answer on a website widget and on WhatsApp through the official business platform, with the same documents behind both.
Do our documents leave our control?
That depends on the model you choose. A hosted model receives the passages it needs for each answer; a self-hosted model keeps everything on your own server, at the cost of running it.
Will it ever make something up?
The risk can be reduced a lot, never to zero. That is why we limit it to your material, keep numbers in lookups, show sources, and review conversations regularly after launch.
How do we keep the answers up to date?
By keeping the documents up to date. When a policy or price list changes, the bot uses the new version on the next question; nothing has to be retrained.