Short answer: a WhatsApp chatbot is an automated flow on the official WhatsApp Business API that replies the moment someone messages your business number. For a business, the useful kind is a structured flow with buttons and lists. It greets the customer, asks two or three qualifying questions, saves the answers to the contact and hands the chat to a person in your team inbox with the full history. You can add an AI assistant on top, but most mid-sized teams get further with a clear flow first. Below is how to build one, when AI helps, the mistakes that make bots fail, and what Meta’s pricing change of 1 October 2026 means for bot replies.
Last updated: 21 November 2026
This guide is for Indian teams that get more WhatsApp messages than a few people can answer from one phone: hotel and travel groups, coaching institutes, real estate developers, D2C brands and SaaS companies. If you get ten chats a day, the WhatsApp Business app and a saved quick reply are enough. If you get hundreds, or your leads arrive at night, read on.
What a WhatsApp chatbot actually does for a business
Most people picture a bot that answers questions. In practice the answering is the small part. The valuable work is everything around it: replying at 11pm when nobody is online, asking what the person wants, recording it, and putting the chat in front of the one person who can close it.
On CampaignHQ you build that as a visual flow with buttons, lists, branches and delays, instead of writing keyword rules. The bot and your agents work from the same contact record, so when an agent picks up the chat they see what the bot asked and what the customer chose.
Typical jobs a bot does well:
- Greets every new chat within seconds, day or night, and offers a short menu.
- Captures name, city, budget, course, travel dates or whatever your team needs to qualify a lead.
- Answers the questions that come up fifty times a day: timings, location, fees structure, order status links.
- Tags the contact and assigns the chat to a department or an agent queue.
- Steps aside the moment a customer asks for a person.
How Moustache Escapes uses its chatbot
Moustache Escapes, the hostel and hotel chain, runs its inbound WhatsApp on CampaignHQ. They get a flood of queries, and most of them need a short back and forth before a person should step in. Their chatbot handles that first part: it answers, qualifies the lead, routes it to the right department and creates the lead in their own CRM. Our guide to WhatsApp lead management walks through the routing rules and follow-ups in detail.
The CRM side is what most chatbot guides skip. Moustache’s CRM also sends WhatsApp messages through the CampaignHQ API, and webhooks push every inbox conversation back into the CRM. So the bot, the agents and the sales team all look at the same history, and nobody copies chats into a spreadsheet. If you run a custom CRM, our guide to connecting WhatsApp to your CRM covers the setup.
How to plan a WhatsApp chatbot in six steps
- Read your last 200 chats. Sort them by what the customer wanted. You’ll usually find four or five reasons cover most of them. Those become your menu.
- Decide where each reason should end. A booking enquiry goes to sales, a complaint goes to support, a fees question can be answered by the bot. Write the destination before you write any messages.
- Pick the two or three questions that qualify a lead. For a hotel that might be dates, number of guests and property. For a coaching institute, course and city. Ask with buttons or lists so the answers land as clean fields, not free text.
- Build the flow and the handoff together. Set which agent queue each branch lands in, and what the agent sees when it arrives. Auto-assign, team queues and round-robin keep chats from waiting on one person.
- Connect it to your other systems. Push qualified leads to your CRM and trigger follow-ups (a brochure, a reminder, an email) from the answers the bot captured.
- Test every branch, then watch the drop-offs. After a week, look at where people stop replying. That step is usually a question that’s too long or a menu with too many options.
Want to see a qualifying bot built around your chats?
Bring a few real enquiries to a demo and we’ll sketch the flow, the routing and the CRM handoff with you.
Rule-based flows or an AI chatbot?
WhatsApp chatbots come in two kinds. A rule-based bot follows a flow you design: buttons, lists, questions and branches. It says exactly what you approved, captures clean answers and never invents a refund policy. An AI chatbot uses a language model to read free text and write its own replies. It copes with questions you didn’t plan for, but it needs your documents, clear limits and someone checking what it says.
For lead capture and routing, start rule-based. The questions are known, the answers need to land as clean fields, and a wrong answer can cost a booking. AI earns its place in the long tail: the open questions a menu can’t cover, such as “can I check in early if my train arrives at 6am”.
CampaignHQ’s chatbot builder is a no-code flow builder with messages, buttons, lists, questions, delays, conditions and API calls to your own systems. For the AI side, you can connect Claude or ChatGPT to CampaignHQ through our MCP server. Once an admin turns on “Allow AI agents to send inbox replies”, the assistant can answer an inbox conversation one reply at a time, and it can never launch a campaign or send in bulk. Our guide to the WhatsApp MCP server explains the setup.
Form not loading? Open it on our site.
Why most business chatbots disappoint
The bot usually isn’t the problem. The setup around it is. The mistakes we see most often:
The bot only understands exact keywords. A customer types “is the room free on saturday” instead of “availability” and gets a menu back. Buttons and lists fix most of this, because the customer taps instead of guessing your words.
The handoff loses the conversation. The bot collects details, then the agent asks for all of them again. When the bot and the inbox share one contact record, the agent starts where the bot stopped.
Nobody owns the chats the bot passes on. A bot that qualifies a lead at midnight is wasted if the lead sits unassigned until noon. Route each branch to a queue with a person behind it, and use tags so a manager can see what’s waiting.
The bot tries to do everything. A bot that answers 80 questions is hard to maintain and easy to get lost in. Keep it to the jobs it does well and let people handle the rest.
What bot replies cost on WhatsApp since 1 October 2026
This changed recently, and it matters more for bots than for anything else you send. When a customer messages you, a 24-hour customer service window opens, and the replies you send inside it are service messages. Meta made service messages free in November 2024. From 1 October 2026, according to Meta’s pricing documentation, each business phone number gets a free tier of 1,000 service messages a month, and Meta charges per message after that. Unused free messages don’t roll over.
A chatbot sends several messages per conversation: a greeting, a menu, a question, a confirmation. So a busy number can pass 1,000 service messages in the first days of the month. Two things follow from that.
First, design flows that get to the point. Fewer, clearer steps cost less and convert better. Second, look at where your chats start. Conversations that begin from a click-to-WhatsApp ad open a free entry point window, and Meta doesn’t charge for service, utility, authentication or marketing messages inside it. Utility templates sent inside the customer service window, which used to be free, are now charged at utility rates too. Our WhatsApp Business API pricing guide explains the categories in detail.
Chatbot, team inbox or both
| Your situation | What to set up first | Why |
|---|---|---|
| Many chats, each needs a person (sales calls, complex support) | Team inbox with auto-assign | Speed of human reply matters more than automation |
| Many chats, most ask the same few things | Chatbot with a short menu | The bot clears the repeat questions before anyone looks |
| Leads arrive at night or from ads | Qualifying bot plus routing | Leads get a reply in seconds and land with the right team in the morning |
| You run your own CRM or booking system | Bot plus API and webhooks | Leads and replies stay in the system your team already uses |
Most mid-sized teams end up with both. The bot handles the first minute, the inbox handles the rest.
What to look for in a WhatsApp chatbot platform
CampaignHQ is a full customer messaging platform for WhatsApp, email, SMS and RCS, built on the official WhatsApp Business API, and we’re an official Meta Business Partner. Our chatbot builder sits on the same contact record as the shared inbox, broadcasts and automations, so a lead the bot qualifies can get an email follow-up or a WhatsApp reminder without another tool. You can see the builder on our WhatsApp chatbots page.
Whichever platform you choose, check these before you sign:
- It runs on the official WhatsApp Business API, not an unofficial gateway that risks your number.
- Bot-to-agent handoff keeps the full chat history and the captured fields.
- Routing goes beyond one shared login: auto-assign, team queues, round-robin.
- Answers from the bot save as fields you can segment and automate on.
- There’s an API and webhooks if your leads need to reach your own CRM.
- WhatsApp sits next to email and SMS, so follow-ups don’t need a second system.
For the bigger picture on automation, see our posts on lead qualification automation, WhatsApp AI agents for retention and WhatsApp Flows, which work well inside a bot for longer forms. Hotels can start with our guest communication playbook, and developers with real estate lead nurturing.
Frequently asked questions
Can I build a WhatsApp chatbot without coding?
Yes. On CampaignHQ you build the flow visually with messages, buttons, lists, branches and delays, and set the handoff to your team inbox in the same builder. Connecting a custom CRM through the API is the only part that may need a developer.
Do I need the WhatsApp Business API for a chatbot?
For a business chatbot, yes. The WhatsApp Business app only offers greeting and away messages and quick replies. Automated flows, multiple agents and integrations need the official WhatsApp Business API through a provider.
Are chatbot replies on WhatsApp free?
Replies inside the 24-hour customer service window are service messages. Since 1 October 2026, Meta gives each business number a free tier of 1,000 service messages a month and charges per message after that. Chats that start from a click-to-WhatsApp ad open a free entry point window where those messages aren’t charged.
Should my WhatsApp chatbot use AI?
Start with a structured flow for greetings, qualifying questions and routing, because the answers land as clean fields and the bot only says what you approved. Add AI for the open questions a menu can’t cover, with a person reviewing what it sends. On CampaignHQ, an AI assistant connected through MCP can send inbox replies only after an admin allows it.
What happens when a customer wants to talk to a person?
Give them a clear “talk to our team” option at every step. The bot then pauses and assigns the chat to an agent or queue in the shared inbox, with everything the customer has already said.
Next step
If your team is answering the same WhatsApp questions all day, or leads wait until morning for a reply, bring a few real chats to a demo. We’ll show you the bot, the routing and the inbox on CampaignHQ, and you can start with a 7-day free trial, no credit card needed.
Prefer to talk first? See how it works, or start a 7-day free trial, no credit card needed.
Written by CampaignHQ Team