An AI WhatsApp chatbot that answers from your documents
Load your policies, product details and FAQs, and let the assistant answer out of them instead of guessing. When it should not answer alone, it drafts a reply for your agent and steps back.
The honest version
Why people hate most WhatsApp chatbots
Two different things get sold under the same word. The first is a menu: press 1 for orders, press 2 for support. It works until a customer types a full sentence, and then it loops, apologises, and offers the menu again. Nobody has ever enjoyed that.
The second is a general-purpose language model bolted onto your number. It understands the question beautifully and then answers it from nothing in particular — inventing a returns window, confirming a feature you do not ship, quoting a delivery time nobody promised. Fluent and wrong is worse than a menu, because customers believe it.
What actually works sits between the two: an assistant that understands how people really phrase things, but answers only from material you have given it, and knows when to stop and fetch a human.
What the AI layer does
Grounded answers, agent drafts, generated flows
Three capabilities that reinforce each other, plus the controls to keep them honest.
Answers from your knowledge base
The AI retrieves from documents you have loaded and answers out of that material, rather than inventing something plausible-sounding about your refund window or your delivery timelines.
Upload a file or paste the text
Two ways in. Upload an existing document — a policy PDF, a product sheet, an internal FAQ — or paste text straight into a knowledge-base entry when there is no file to upload.
Suggested replies for your agents
Ask for a draft reply on any contact and the AI writes one using the conversation and your knowledge base. It does not send. Your agent reads it, edits it, or ignores it.
Describe a flow, get a flow
Write what the automation should do in plain language and the AI generates an automation flow graph from it. You get a working starting point instead of a blank canvas.
Settings you control
AI behaviour is configuration, not a black box. Tune how the assistant is set up for your business and change it as you learn what your customers actually ask.
A knowledge base you can audit
List everything the AI can draw on, download the original file back, and delete anything out of date. When an answer is wrong, you can find the source and fix it.
Retrieval is the difference between useful and dangerous
A knowledge base is not decoration. When a customer asks something, the assistant pulls the relevant passages from what you have uploaded and composes its answer from those. If the answer is missing from your documents, the honest outcome is that the assistant says so rather than filling the gap. That also means the fix for a bad answer is editorial, not technical: find the document, correct it, replace it.
An AI that writes for your agent, not over them
Most chatbot products only offer one setting: the AI talks to your customer. Suggested replies offer another. An agent opens a conversation, asks for a draft, and gets one written against that contact's history and your knowledge base — which they then send, rewrite or discard. Nothing reaches the customer without a person choosing to send it. For regulated categories, for high-value accounts, or simply for a team still building trust in AI, that is often the right setting to start on.
Describing an automation instead of drawing one
Flow builders are powerful and slow to learn. Writing what you want in a sentence — the trigger, the question to ask, where each answer should go — and getting back a generated flow graph turns the hardest part into an editing job. You still review every branch before it goes live, which is the point: reviewing is a skill most teams already have.
Typical setup
How teams put this together
A realistic order of operations. Most of the work is in step two, and it is not engineering work.
- 1
Connect the number
Your AI assistant needs a WhatsApp Business Platform number behind it before it can answer anything. That is the foundation everything else sits on.
- 2
Write down what you actually know
Collect the answers your team already gives every day — returns policy, shipping timelines, sizing, warranty terms, opening hours, the three questions that fill your inbox — and load them as uploaded documents or pasted text.
- 3
Configure how the assistant behaves
Set it up for your business: how it should sound, what it is allowed to cover, and where its boundaries are. Expect to revisit this in week two.
- 4
Choose autonomous or agent-assisted
Decide whether the AI replies directly or only drafts for a human. Many teams start in draft-only mode on every conversation, then move the clearly safe topics to autonomous once they have read a few hundred drafts.
- 5
Generate the structured flows
For the repeatable, transactional paths — order status, appointment booking, lead qualification — describe the flow in plain language, generate it, then open the graph and tighten the branches yourself.
- 6
Define the handover
Decide the triggers that pull a human in: an explicit request, a complaint, a topic outside the knowledge base, a repeated failure to answer. Route those into a shared inbox with the transcript attached.
- 7
Read the transcripts and feed them back
Every week, skim the conversations the assistant handled badly. Each one is either a missing document or a wrong one. This loop is what turns a mediocre chatbot into a good one, and there is no shortcut around it.
Plan the handover before you plan the bot
Nobody should promise you a chatbot that never needs a person. The useful question is not how many conversations the AI closes on its own — it is how quickly the ones it cannot close reach someone who can, and whether that person has to ask the customer to repeat themselves.
So the handover deserves as much design as the answers. Which signals escalate. Who receives the conversation. What the agent sees when it lands. Whether the assistant keeps drafting in the background once a human has taken over, which is usually the right answer, because the agent still benefits from a first draft.
Related
Where this fits with everything else
An AI assistant is one layer of a WhatsApp setup, not the whole thing. The structured, deterministic paths belong in no-code automation flows, the escalations land in a shared inbox where agents can pick them up, and the contact history the AI reads about comes from your WhatsApp contact records. None of it works without official WhatsApp Business Platform access underneath.
If you are still working out the vocabulary, we wrote a longer explainer on what an AI WhatsApp chatbot actually is and a practical piece on automating WhatsApp customer support without making it worse.
FAQ
Frequently asked questions
Straight answers on grounding, drafts, handover and templates.
What is the difference between an AI WhatsApp chatbot and a rule-based chatbot?
A rule-based chatbot follows a decision tree you drew: it matches keywords or button taps and moves to the next node. It is predictable, and it fails the moment someone phrases a question in a way you did not anticipate. An AI chatbot interprets the message itself, so 'has my parcel shipped', 'where's my order' and 'kab tak aayega' can all reach the same answer. Most businesses end up using both — flows for structured, transactional steps, AI for the open-ended middle.
Where does the AI get its answers from?
From a knowledge base you build. You upload documents or paste text, and the assistant retrieves the relevant passages before it answers — a pattern usually called retrieval-augmented generation. That grounding is what separates an assistant that quotes your actual returns policy from one that improvises a policy that sounds reasonable but is not yours.
Can the AI draft a reply without sending it?
Yes, and this is a genuinely useful middle ground. The suggest-reply capability produces a draft for a specific contact and hands it to a human agent — it does not send anything to the customer. Teams that are not ready to let AI speak on their behalf can still get most of the speed benefit, because writing the first version of a reply is where the time goes.
What happens when the chatbot cannot answer?
It should hand over, and you should plan for that from day one rather than treating it as a failure state. Route the conversation into a shared inbox where a human picks it up with the full transcript in front of them. Any business claiming its chatbot never needs a human is describing a demo, not a support operation.
Do I still need message templates if I have an AI chatbot?
Yes, for anything you start. Meta's WhatsApp Business Platform lets you reply freely for 24 hours after a customer's last message; outside that window you must use an approved template. So an AI assistant handles the live conversation, and templates handle the outbound message that begins one. Check Meta's current published rates for what each conversation category costs.
Do I need to know how to build automation flows?
It helps, but it is not the starting point. You can describe the automation you want in a sentence or two and have the AI generate a flow graph from that description, then open it and adjust the branches. Reviewing a generated flow before you publish it is far easier than designing one from nothing.
Want an AI chatbot that stays inside the facts?
Create your account, or message us on WhatsApp and we'll bring you on as soon as we open the doors.