Most WhatsApp chatbots are built to replace conversations. That is why most of them are abandoned within three months.
The ones that survive do something narrower and more useful: they clear the queue of questions that never needed a human, so that the humans can answer the ones that do. That is a smaller ambition and a much better outcome.
Start by reading your own inbox
Before designing anything, export the last month of incoming messages and sort them by what was being asked.
Almost every business finds the same shape: five or six questions account for most of the volume. In India, typically:
- Where is my order?
- What are your prices / do you have this in stock?
- What are your timings / where are you located?
- How do I return or exchange this?
- Is my payment done?
- Can I talk to someone?
That last one matters as much as the rest. It is the escape hatch, and it needs to work instantly.
If you skip this step you will build a bot for the questions you imagined, and those are never the ones people ask.
WhatsApp inbox, campaigns, journeys and deep analytics that turn one-time buyers into loyal customers.
Start free See the demoWhat to automate
Order and delivery status. The highest-volume question in Indian commerce, and the easiest to answer well because the answer is already in a system. Ask for an order number, look it up, reply with the real status and a tracking link.
Here is the deeper fix, though: most "where is my order" messages exist because the order update never arrived, or arrived and was unclear. Automating the answer treats the symptom. Sending a good proactive update removes the question.
Business basics. Hours, address, directions, payment methods, return policy. Static, unambiguous, asked constantly.
Catalogue browsing. Categories, a few products, prices, and a way to reach a person to actually buy. Do not try to run the whole purchase through a menu unless your catalogue is genuinely simple.
Lead qualification. For services — what do you need, what is your budget range, when do you need it. Three or four questions, then hand to a human with the answers already attached. This is one of the few places where a bot makes the human conversation measurably better rather than merely shorter.
Appointment booking and reminders. Show slots, take a booking, confirm it, remind the day before. Clinics, salons and studios get most of their automation value here.
What not to automate
Complaints. Someone unhappy and being handled by a menu becomes someone much more unhappy. Detect the sentiment and route immediately.
Refunds and payment disputes. Money moving the wrong way needs a person, both for the customer's sake and for your records.
Anything where being wrong is expensive. Medical guidance, legal questions, technical advice that could cause damage.
Negotiation. Discounts, custom pricing, bulk terms. A bot that gives away margin is worse than no bot.
The handover is the whole design
The single most common failure is a bot that will not let go.
Rules that work:
"Talk to a person" is always available. Every menu, every step. Not buried.
Three failures and you are out. If the bot has not understood twice, stop trying. Say a person will take over, and mean it.
Frustration ends the flow immediately. Words like "useless", "not working", "want refund", or just repeated messages in a row — hand over.
The human sees the whole conversation. Nobody should have to re-explain. The agent opens the chat with the full history and whatever the bot collected.
Say when. "Someone will reply within 15 minutes" is fine. Silence is not. And whatever you promise, staff to it.
The honest limits
A WhatsApp chatbot will not replace your support team. If that is the business case, the project will fail and you will have spent money learning it.
What it does well is absorb the repetitive half of the volume so the same team handles more without growing, and answer instantly at 11pm when nobody is there.
The correct measure is not "conversations handled by the bot". A bot can handle a conversation by exhausting the customer. Measure instead:
- Conversations fully resolved without a human, where the customer did not come back with the same question
- Time to first human reply for the ones that did hand over — this should fall
- Handover rate — if it is above roughly half, the bot is answering the wrong questions
- Repeat contacts within 24 hours — if this rises after launch, the bot is deflecting rather than resolving
Writing for a bot is not writing for a website
Bot copy fails in predictable ways, and almost all of them come from writing it like web copy.
Keep every message short. Two or three lines. A wall of text in a chat window gets scrolled past, and on a phone it fills the screen.
Give numbered options, not open questions. "How can I help?" invites a sentence your bot cannot parse. "Reply 1 for order status, 2 for returns, 3 to talk to someone" gets a usable answer.
Never more than four options. Beyond that people stop reading and type something else.
Say what you are. "Hi, I'm the automated assistant" sets expectations correctly and makes people more patient when you get something wrong. Pretending to be human makes the eventual failure feel like a trick.
Write the error message properly. "Sorry, I didn't understand" is where most bot conversations die. Better: "I didn't catch that. Reply 1 for order status, 2 for returns, or 3 to talk to a person." Always re-offer the exit.
The flow mistakes that kill adoption
Asking for information you already have. If the customer is messaging from a number tied to three orders, do not ask for an order number. Offer the three.
Dead ends. Every branch must lead somewhere — an answer, or a person. A branch that replies with information and then stops leaves the customer staring at a chat with nothing to do.
Forgetting context one step later. If they said "return" in the first message, do not offer "returns" as an option in the third.
Working only in English. In much of India, customers reply in Hindi, in Hinglish, or in a regional language. A bot that only recognises English keywords will not understand a large share of its own users. At minimum, recognise common Hinglish spellings — "order kahan hai", "kab aayega", "return karna hai".
Test it like a customer, not like a builder
Before launch, three tests that catch most problems.
Walk every path. Including the wrong ones. Reply with nonsense. Reply with an emoji. Reply with nothing for an hour and then continue.
Give it to somebody who did not build it — ideally someone in the business who talks to customers — and watch without helping. Every place they hesitate is a place the copy is wrong.
Send a real message from a real phone, not the preview. Line breaks, emoji rendering and button behaviour differ between the builder and the handset.
Start smaller than feels worthwhile## Start smaller than feels worthwhile
Automate one thing. Order status, or appointment booking. Run it for two weeks. Read every conversation it handled — all of them, not a sample. You will find things nobody predicted.
Fix those, then add the second thing.
The businesses that get value from WhatsApp automation are not the ones with the most elaborate flows. They are the ones that picked the single most repetitive question, answered it properly, and left everything else to people.
Frequently asked questions
Do chatbot replies cost money?
Free-form replies inside the 24-hour customer service window are free, within the 1,000 free service messages per number per month introduced on 1 October 2026. Beyond that allowance they cost ₹0.115 each. Template messages you send to start a conversation are always charged.
Will a chatbot annoy my customers?
It will if it stands between them and a person. Customers accept automation that answers instantly and hands over the moment it cannot help. They resent loops.
Do I need AI for this?
Usually not to start. Most support volume is a handful of repeated questions, and a simple menu answers them more reliably than a language model. Add AI once you know what is actually being asked.
What should the bot never handle?
Complaints, refunds, anything involving money going the wrong way, and anyone who says they are frustrated. Route those to a person immediately.
