WhatsApp Chatbot Development for Business
WhatsApp is where a great many customers would rather talk to you, and it has rules that no other channel has. Most of the surprises in a WhatsApp project are not technical — they are the messaging window, template approval, and per-message pricing.
Discuss your projectWhat it can do
Answer questions
Grounded in your documentation, the same way a website chatbot is, in the app your customers already have open.
Order and delivery status
The highest-value use in practice. A customer messages a reference and gets a straight answer, in the place where they would otherwise send a "where is my order" email.
Book and change appointments
Availability read from your calendar, booking written back, with a confirmation and reminders as template messages.
Qualify leads
A short conversation that writes a structured record into your CRM, which is a higher-completion path than a web form on a phone.
Notifications out
Order confirmations, shipping updates, appointment reminders, one-time passcodes. These require pre-approved templates and are priced per message.
Handoff to a human
Into your helpdesk, with the conversation and context attached, exactly as on any other channel.
Setting up the WhatsApp Business Platform
This is the part that takes the calendar time, and almost none of it is development. Starting it early is the main thing that determines when you launch.
- 01
Meta Business account and business verification
Meta verifies your business against official documentation — registration details, and often a utility bill or bank statement showing the business name and address. Allow real time for this; rejections over a mismatched trading name are common and each round costs days.
- 02
A phone number that is genuinely free
The number cannot be registered to a personal or Business-app WhatsApp account. A number currently in use must be deleted from WhatsApp first, which destroys its chat history. Most clients take a new number instead, and we would advise that unless the existing number is already known to customers.
- 03
Cloud API directly, or through a provider
Meta's Cloud API is free to call and you pay Meta for messages. Providers such as Twilio, 360dialog or MessageBird add their own margin and their own tooling. For a custom build we usually go direct, which removes a layer of cost and a layer of rate limits.
- 04
Display name approval
The name customers see is reviewed against Meta's policy and has to relate clearly to your verified business. Aspirational or keyword-stuffed names get rejected.
- 05
Message templates submitted for approval
Every message you send outside an open conversation window must use a template approved in advance. Each is reviewed, and each variation needs its own submission, so the set is planned up front rather than added one at a time.
The 24-hour window, and what it means for your design
This is the rule that catches everyone. When a customer messages you, a window opens during which you may reply freely with any content. Once it closes, you can no longer send a free-form message — only an approved template, which is charged.
The practical consequence: a conversation your agent picks up the next morning cannot be continued with a normal reply. It needs a template to reopen contact. Teams that discover this after launch end up with agents unable to answer customers they can plainly see waiting, which is an avoidable and very frustrating situation.
So the templates are designed alongside the conversation flows, not afterwards, and we plan for the realistic case where a customer replies twelve hours later. Pricing follows the same logic: Meta charges per message by category — marketing, utility, authentication and service are priced differently, and rates vary substantially by country. Those rates change, so we model your expected volumes against Meta's current published rates during scoping rather than quoting a figure that will be stale.
One more rule worth knowing before you plan a campaign: you need opt-in to message a customer first, and Meta enforces quality ratings. A number that generates blocks and reports has its sending limits cut. WhatsApp is not a bulk channel, and treating it as one costs you the channel.
Integrations
- CRM: HubSpot, Salesforce, Zoho, GoHighLevel, Pipedrive — conversations and qualified leads written to the contact record.
- Helpdesk: Zendesk, Freshdesk, Intercom, so WhatsApp arrives in the same queue as email and web chat.
- Commerce: Shopify, WooCommerce, or your own store, for order lookup and shipping updates.
- Calendars: Google Calendar, Calendly, or your booking system.
- Your own database or application, for the lookups that make an answer specific to the person asking.
Other channels, same bot
The knowledge, the integrations, and the escalation rules sit behind the channel rather than inside it, so the same bot runs on your website, in your app, on Slack or Microsoft Teams for internal use, and on WhatsApp. One set of content to maintain instead of several that quietly diverge.
What does change per channel is formatting and the rules of the platform. WhatsApp has the messaging window and templates. Slack has threads and blocks. A website widget can show a card with a button. The content is shared; the presentation is not pretended to be.
Common questions
Related in AI Chatbot Development
Tell us what you need
Describe the problem and we will come back with scope, timeline, and a rate. No obligation to proceed.
Get in touch