A WhatsApp chatbot that earns its keep answers the questions your team retypes every day, books or qualifies the customer, and hands the chat to a person with the CRM record already open. To run one with AI, you need the WhatsApp Business Platform, not the phone app, plus a knowledge base you control and a clear rule for when a human takes over.
The cost of a slow WhatsApp reply is easy to miss because nobody logs it. A customer asks about stock, a delivery date or an appointment slot at 9pm, gets no answer, and buys elsewhere. Meanwhile the messages that do get answered live on one staff member's phone, so the CRM never learns the lead existed.
Below: the app versus the API, the Meta rules that shape every build, how to ground and limit the assistant, how chats reach your CRM, and when a builder subscription is the better buy.
Where WhatsApp support and sales break down
Chats live on one phone
The WhatsApp Business app runs on a phone and a few linked devices. When the person holding it is busy or on leave, customers wait, and history stays out of the CRM.
Leads never reach the CRM
A prospect who messages on WhatsApp is often not created as a contact at all, so nobody follows up and the channel looks like it produces nothing.
Follow ups blocked by the window
Teams discover after launch that they cannot send a free-form message to a customer who went quiet. Outside the service window only an approved template is allowed.
A bot that guesses
A general chatbot answers a refund or stock question from its own training instead of your policy, and the customer screenshots the wrong answer.
What customers use WhatsApp for with a business
Most business WhatsApp traffic is short: is this in stock, when does my order arrive, can I move my appointment, can someone call me back. A smaller share is high value: a quote request, a wholesale enquiry, a complaint that becomes a refund if nobody answers.
Before building, read a few hundred recent chats and sort them into three buckets: answer alone, collect then hand over, never touch. If most of your messages are complaints or custom quotes, a bot is the wrong first step; a shared inbox and better staffing will do more.
WhatsApp Business app versus the WhatsApp Business Platform
The WhatsApp Business app is a free phone app with a business profile, quick replies, labels and an away message. It suits a small team answering by hand. It offers no supported way to connect an AI model, a CRM or a booking system.
The WhatsApp Business Platform, often called the WhatsApp Business API, is built for software. Meta hosts it as the Cloud API, reached directly or through a Business Solution Provider such as Twilio. Every WhatsApp chatbot integration that reads your systems and writes to your CRM runs here. Tools that script a logged-in phone app break Meta's terms and put the number at risk, so we do not build on them.
Check how your current number is used before moving it, because registering it on the Platform changes how it works in the app. Some businesses give the assistant a new number until the flow is proven.
Verification, templates, opt in and the service window
Four Meta rules shape every whatsapp business automation. Treat these as the general model and confirm current terms in Meta's documentation.
- Business verification: legal name, address and website must match across Meta's business tools. Mismatched records are a common cause of delay.
- The customer service window: after a customer messages you, you can reply freely for a limited time, including AI replies. After it closes, only an approved template can restart the conversation.
- Message templates: pre-approved messages for reminders, order updates and marketing, sorted by Meta into categories that affect what you pay. Submit them early; a rejected reminder template stalls a booking flow.
- Opt in: get the customer's permission before you message first, and say what they will receive. Meta watches block and report rates and can limit sending on a low quality number.
A WhatsApp AI chatbot grounded in your own knowledge
A whatsapp ai chatbot is only as good as what it is allowed to say. We ground it in sources you own and edit: your product or service list, policies, hours, delivery rules and approved answers. When those are silent, it says so and routes the question to a person instead of guessing.
Live facts come from your systems at the moment of the question. Order status reads the store, availability reads the calendar, stock reads inventory. That is the difference between a whatsapp bot that sounds helpful and one that is right.
Meta's Business Platform terms are written for businesses serving their own customers and restrict general purpose AI chat, so check current terms and keep the scope to your products, orders and bookings. The same discipline drives our web work: the VOT Distribution storefront assistant at shopfreezo.com answers product, compliance and shipping questions from the brand's own content.
Bookings, orders and lead capture
The useful WhatsApp flows end in a record, not just a reply. Typical builds we scope:
- Bookings: real slots from your calendar, a confirmation, and a reminder template with a reschedule option.
- Order questions: status read from the store by order or phone number; refunds and damaged items go to a person.
- Lead capture: the three or four questions sales needs, then a contact created or updated with an owner. A quote request is never left with a bot.
- Proactive updates: shipping, appointment and payment reminders as utility templates to customers who opted in.
Handoff to a person and WhatsApp business CRM integration
Handoff is the part of a whatsapp business integration that customers notice most. The assistant hands over when the customer asks for a person, when the topic is a complaint, refund, legal or medical matter, when its sources lack the answer, or when the enquiry crosses a value threshold you set. The person receives the transcript, the customer's details and a one-line summary.
For the whatsapp business crm integration, the chat lands on the right record. In HubSpot or Zoho that means matching by phone number, creating the contact if missing, logging a summary, and setting an owner and next step. Inconsistent phone formats cause duplicate contacts, so we normalize numbers before matching. If your CRM's native WhatsApp inbox covers your workflow, use it and build only the AI and routing around it.
Facebook Messenger with the same assistant
Messenger and Instagram often get the same questions. Meta's Messenger Platform has its own rules and messaging window, but the knowledge, handoff rules and CRM logic can be shared: one source of truth and a thin adapter per channel, so an fb chatbot and a wa chatbot never give different answers. Start with the channel that carries the most revenue.
Builder platform or custom build
WhatsApp chatbot builders sell a monthly subscription, usually priced by contacts, conversations or seats, with a flow editor and shared inbox. If you need menus, FAQs and a team inbox, a builder is faster and cheaper, and you do not need Benian.
A custom api whatsapp chatbot fits when the assistant must read and write several systems, follow rules a flow editor cannot express, or keep logic and data in accounts you own. We build on the Cloud API or your provider account, with the automation in your own n8n account and credentials you hold, and you pay Meta and any provider directly. Scope depends on systems connected, number of flows, languages and how much the handoff rules need testing.
How a WhatsApp chatbot integration gets built
- Read the chats. Sort real conversations into answer, collect and hand over, and agree the flows in scope.
- Set up the Platform. Verification, the number, any provider account and the first templates, all in your name.
- Build knowledge and connections. Approved answers plus live lookups to the calendar, store or CRM, with credentials in your accounts.
- Write the handoff rules. Triggers, who receives the chat, what context travels and what happens out of hours.
- Test, then launch narrow. Replay past questions, go live on one flow, and track resolution rate, handoff rate, wrong answers and captured leads weekly.