You can build a WhatsApp chatbot without writing code. What "no-code" doesn't remove is the setup around it: WhatsApp runs on Meta's Business Platform, which means a chain of Meta accounts, an approved phone number, and per-message fees once you go live. This guide covers what you actually need, what it costs in 2026, and a concrete build path — plus a genuinely free option for the simplest case.
WhatsApp requirements and pricing were checked against Meta's developer and pricing documentation in September 2026. Meta has a further pricing change scheduled for 1 October 2026, with rates due to be published shortly before — those exact rates were not confirmed at the time of writing. This guide is written from official documentation, not a hands-on build.
What it costs in 2026
Two things changed the economics here:
- Per-message pricing. As of 1 July 2025, Meta replaced its old "1,000 free conversations a month" model with per-message pricing. Messages are billed by category — Marketing, Utility, Authentication, Service — and by the recipient's country.
- The free service window. When a customer messages the business first, replies sent within a 24-hour window are currently free (this includes free-form replies and, at present, utility messages). Marketing templates are billed from the first message.
- Another change is scheduled for 1 October 2026, which is expected to start billing service messages and in-window utility messages per message. Check Meta's current pricing page for the confirmed rates before you build a cost model around it.
- Your platform adds its own fee. A no-code platform sits on top of Meta's fees and charges separately — either per message or a monthly subscription.
So "free WhatsApp chatbot" is only true while you're testing. A live bot that answers customer questions has a real, if small, per-message cost.
The accounts you need before you start
- A Meta (Facebook) account.
- A Meta Business portfolio (business account) — new or existing.
- A WhatsApp Business Account connected to that portfolio.
- A phone number for the bot that is not already registered to a personal WhatsApp account, which you'll verify as the sender.
- For anything beyond initial testing, a permanent access token — the temporary token Meta issues at first expires quickly, so you create a system user and generate a long-lived token.
Option A: basic auto-replies with the WhatsApp Business App (free, ~15 minutes)
If all a business needs is "reply to common questions when we're closed," the free WhatsApp Business App (the mobile app, not the API) supports a greeting message, an away message, and up to a set number of quick replies. There's no branching logic and no knowledge base — it's auto-replies, not a chatbot — but for a single-location business it's often enough, and it costs nothing.
Option B: a branching bot with Twilio (free to build and test)
For a real conversational flow, one accessible path is Twilio: its WhatsApp Sandbox lets you build and test for free, and Twilio Studio is a drag-and-drop visual flow builder — no code. Going live still requires an approved WhatsApp sender through Meta, and Twilio charges a small per-message fee (currently $0.005 per message) on top of Meta's template fees. There's a free trial with no credit card to start.
- Activate the WhatsApp Sandbox in the Twilio Console and connect your test phone by sending the join code.
- Build the knowledge base as realistic sample content for the specific business — real product names, real hours, real FAQ answers — so the demo is convincing.
- Build the flow in Studio. A minimal first version: a welcome message → a branch that routes the incoming message by intent (hours / pricing / booking / something else) → an answer node for each, with a fallback for "something else."
- Add the human handoff. When a message looks like a serious enquiry — a booking request, a price negotiation, a complaint — the bot should say a person will follow up and notify the business (an email or SMS node), rather than trying to close the conversation itself.
- Test with the Sandbox from your own phone.
Other no-code platforms (for example Wati, Rasayel, ManyChat's WhatsApp product, or Landbot's WhatsApp plans) do similar things with different pricing — note that Landbot's free plan is web-chat only and its WhatsApp support is on paid plans. Whichever you choose, it sits on top of Meta's per-message fees.
Designing the flow, not a menu
A rigid numbered menu ("Reply 1 for hours, 2 for pricing…") feels robotic and rarely matches how people actually type. Aim for intent matching: the bot reads the message and routes to the closest answer. Getting the tone right — especially if the business serves a non-English-speaking market, where direct translation reads stiffly — usually takes more iteration than the technical setup.
Testing: use messy questions early
Clean, single-topic questions ("what time do you close?") almost always work. Early versions tend to fall over on vague or multi-part messages — someone asking two things at once, or asking about price before giving any other detail. Test with those deliberately from the start; finding the gaps early avoids a rebuild once real customers are using it.
Going live
Moving from the Sandbox to a real number means registering the sender with Meta and getting message templates approved for the categories you'll use. Remember the 24-hour service window: outside it, or for marketing, messages are billed. Build the flow so most interactions happen inside that window (the customer messages first, the bot replies) to keep costs down.
Frequently asked questions
Is it free? Building and testing can be free. A live bot has a per-message cost from Meta, plus your platform's fee. Budget for it before quoting a client.
Do I need a spare phone number? Yes — one not already tied to a personal WhatsApp account, for the API path. The free Business App uses the business's own number.
Can I do the whole thing on my phone? Only the basic auto-reply option (Option A). A branching bot needs the API and a platform like Twilio.
Thinking of doing this for several local businesses? Read our take on whether a chatbot automation side business is realistic. If you'd rather not build it, see our comparison of AI customer support tools versus hiring a freelance VA.