How to Create a WhatsApp Bot: Business API, Providers, Flows, and Limits

You create a WhatsApp bot for a business on the official WhatsApp Business API: connect directly to Meta's Cloud API or through an approved provider (BSP), verify the business, register a dedicated sender number, build the conversation flow, and plan outbound messages around the 24-hour window.

WhatsApp is where most of the world actually talks, which is exactly why a bot on it converts so much better than one buried on a website. People reply to WhatsApp messages within minutes; they ignore web chat widgets for days.

But creating a WhatsApp bot is not like dropping a widget on a page - there is an official API, approved providers, business verification, and a set of messaging rules that exist to keep WhatsApp from turning into a spam channel. Get those right and you have a powerful, high-response channel. Get them wrong and your number gets blocked. In this guide I will walk you through how to create a WhatsApp bot the way it actually works in 2026, including the parts the marketing pages skip.

This is the WhatsApp-specific companion to my broader guide on how to build a chatbot, which covers the brain - the AI, the persona, and grounding it in your content with RAG. Here I focus on the channel itself: getting onto the API, the flows, and the limits.

Step 1: Decide the one job the bot does

As with any bot, focus wins. Decide the single job: answering common questions, confirming and tracking orders, booking appointments, qualifying leads, or sending reminders and updates. On WhatsApp this matters even more, because users expect a quick, human-feeling reply, not a sprawling menu. A bot that does one thing fast and well, and cleanly hands off to a person for everything else, beats a clever one that makes people feel trapped in a robot.

Step 2: Get onto the WhatsApp Business API - directly or through a provider

This is the part that surprises people, so here it is plainly. There are three different WhatsApp products, and only one of them lets you build a real bot:

There are two ways onto the Business API. The first is the Cloud API that Meta hosts itself: you create an app in Meta for Developers, attach a WhatsApp Business Account (WABA) and talk to the Graph API with nobody in between. The second is a Business Solution Provider (BSP) - a Meta-authorized company that gives you a dashboard, support and usually a no-code flow builder, for a monthly fee. Going direct saves the provider fee and gives you full control, but it needs a developer to build and maintain the connection; a provider suits a team with no technical staff. Either way, the setup involves verifying your business with Meta and registering a sender phone number (a dedicated number, not your personal one). This verification step takes time and paperwork, so start it early - it is the most common thing that delays a WhatsApp bot launch.

You also choose between two integration styles: a no-code provider platform where you build the bot visually in their dashboard, or a custom integration where your own code talks to the provider's API. No-code is faster to launch and great for FAQ and booking bots; custom code is the right call when you need the bot tied deeply into your own systems or want full control of the experience. It is the same trade-off I cover in no-code vs custom code for apps.

Step 3: Build the conversation flow

Now design how a conversation actually goes. Map the common paths: a greeting, the main options, what happens when someone asks something off-script, and crucially, how they reach a human. Decide where the bot answers freely with AI and where a fixed menu or buttons are safer. My rule of thumb: use AI for open questions where understanding matters, and use structured buttons for choices where you want a guaranteed clean path, like picking an appointment time or confirming an order. Always include an obvious "talk to a person" path - on WhatsApp, an unhelpful bot with no escape is worse than no bot at all, because it sits in the customer's most personal app.

Step 4: Respect the 24-hour window and template rules

This is the single most important rule on WhatsApp, and the one that trips up everyone who skips it. WhatsApp splits your messages into two kinds:

• Inside the 24-hour window: once a user messages you, you can reply with anything - free-form text, your AI answers, buttons - for 24 hours. This is the conversational mode your bot lives in.
• Outside the window: if more than 24 hours have passed since the user's last message, you may only send pre-approved template messages. You cannot send free-form text to re-open a conversation. Templates have to be submitted to Meta and approved in advance, and many categories are paid per message.

What this means in practice: design your bot so it does its real work inside the window, and plan any proactive outreach - order updates, reminders, confirmations - as approved templates. If you want to start a conversation with a customer who has not messaged you recently, it has to be a template. Building this understanding in from the start saves you from a redesign later, and from the classic mistake of assuming you can message anyone anytime. For current build and running costs, see how much a chatbot costs.

Step 5: Test, then launch on one flow

Test with real phones, not just the provider's preview. Send the messy messages real people send - voice notes, emojis, half-sentences, questions in the wrong order - and watch where the flow breaks or the bot gives a bad answer. Then launch narrow: one flow, like booking or FAQ, with a human monitoring conversations for the first weeks. WhatsApp is intimate, so a bad first experience costs you more here than on a website. Earn trust on one flow, then widen. I build these for clients - see AI chatbot development.

How much does a WhatsApp bot cost in 2026?

WhatsApp bots have a cost structure worth understanding up front. There are usually three layers: the provider fee (a monthly subscription to your BSP, if you use one), WhatsApp message charges (since July 1, 2025 Meta charges per delivered template message, priced by the template's category - marketing, utility or authentication - and the recipient's country), and the build cost. A no-code provider bot can launch for a modest monthly fee plus the message charges. A custom-built WhatsApp bot is an upfront development project, similar in scope to a small app, which I size up in idea to MVP: how to build your first product, plus the same ongoing message costs. If your bot also uses AI to answer, add the model-usage cost on top. Ordinary replies inside the 24-hour window the customer opened, and utility templates sent inside that window, were free until 30 September 2026. From 1 October 2026 both are charged, with replies billed at the market's utility rate after 1,000 free a month per business number (see WhatsApp Business API pricing). So a bot that answers people who wrote in stays cheap at low volume; most of the cost sits in outbound messages - reminders, campaigns and verification codes. I break down the full build and running ranges in how much a chatbot costs.

The hard parts nobody mentions

Three things consistently catch people out when they build a WhatsApp bot:

• Business verification takes longer than expected and is the usual cause of a delayed launch, so start it before you build anything.
• The 24-hour window and templates shape every proactive message. A bot designed as if you could message anyone anytime gets rebuilt.
• Compliance: WhatsApp is strict about spam, opt-in and message quality, and a flagged number can be restricted. Clear consent is a requirement, not a nice-to-have.

What to have ready before you start

Before building a WhatsApp bot, have these ready - each one can stall the setup for days:

• Admin access to the business's Meta Business Manager.
• The business details for verification: legal name, address, and a website that shows the same legal name. My own verification was rejected the first time for exactly that - the legal name was missing from the site.
• A dedicated phone number for the bot. A number already registered in the WhatsApp app usually has to leave the app before it can be registered on the API.
• The list of topics the bot handles, and who in the business takes the conversation when the bot is stuck.
• The template wording you will need, such as an order confirmation and a reminder, so they can go to Meta for approval early.

Should you build it yourself or hire someone?

You can self-serve a simple WhatsApp bot through a no-code provider if your needs are basic FAQ or booking and you are willing to learn the platform and the rules. Bring in help when the bot needs to connect to your own systems - your CRM, your inventory, your booking calendar - when you want AI answering accurately from your content, when business verification and compliance feel daunting, or when the bot is central to how you sell. The WhatsApp Business API has more moving parts than a website widget, and getting the provider setup, the windows, and the templates right is exactly where experience saves you weeks of false starts.

Putting it together

So the path is: pick one clear job, get onto the WhatsApp Business API through a provider and verify your business early, design flows that mix AI and buttons with an always-available human handoff, build everything around the 24-hour window and approved templates, then test on real phones and launch on one flow. Start narrow, respect the rules, and let the bot earn a wider role as it proves itself in the channel where your customers actually reply.

If you want a WhatsApp bot that is properly set up, compliant, and answers accurately from your own content, that is exactly what I build. Book a call and tell me what you want it to handle, or reach me through the contact form, and I will tell you the simplest way to get it live without tripping over the rules.

Sources

• Meta - Pricing on the WhatsApp Business Platform