To build a WhatsApp chatbot you need to settle two things before picking any tool: which connection the bot talks through (Business app, official API or an unofficial connection) and whether it follows a fixed flow or understands what the customer writes. The rest is choosing a builder.
Before you start: the connection
| Connection | Cost | Risk | Good for |
|---|---|---|---|
| WhatsApp Business (app) | free | none | greeting and away messages, not a real bot |
| Official API (Meta Cloud API) | per-conversation pricing plus the provider | low, approved by Meta | companies, volume, outbound with approved templates |
| Unofficial connection (Baileys, whatsapp-web.js) | free | the number can be banned if you abuse it | people already talking to their customers, own projects |
Route 1: what WhatsApp Business does on its own
Greeting, away messages and quick replies. It is not a chatbot (it does not understand questions or show menus), but it covers "got it, I'll reply soon". Free, on your phone.
Route 2: official API plus a flow builder
The company route. You connect the number to the official API through a provider (Meta itself or a partner) and design the flow in a visual builder: menu, questions, data capture, handoff to a human. Tools like Typebot and n8n handle the flow.
Short version:
- Create a Meta Business account and register the number on the API.
- Pick a builder and point the WhatsApp webhook at it.
- Design the flow starting from the most common question.
- Test with your own number before opening it to customers.
Route 3: your own code
For developers: libraries like Baileys (Node) and whatsapp-web.js connect the number as a linked device and let you write the bot. Free and flexible, but the connection is unofficial: no bulk messages to people who did not ask, which is what gets numbers banned most.
Route 4: an AI agent instead of a flow
Chatbot flows break when the customer writes something outside the menu. An AI agent reads the message and the history and answers. The catch is tone: a generic agent sounds like a call center.
WACrew takes this route for people whose customers know them: instead of a bot with a name, it drafts the reply in your own writing style and you approve it (or switch auto on per chat). It is open source, runs on your own server and uses an unofficial connection (Baileys). It also ships an MCP server so your coding agent (Claude Code, Codex, Cursor) can read and answer the chats. See WhatsApp AI agent.
Which one to pick
- Store, delivery, bookings at volume: official API plus a flow builder.
- A professional answering on their own number: an agent with approval that replies like you.
- Quick test, no cost: WhatsApp Business with greeting and away messages.
Questions
Can I build a WhatsApp chatbot for free? Yes, with the Business app (no intelligence) or with an unofficial connection and open-source code. The official API charges per conversation.
Do I need to code? Not for route 2: visual builders handle it. For route 3, yes.
Can a chatbot get my number banned? On the official API, only if you break Meta's policies. On an unofficial connection, the risk grows with bulk messages and messages to people who do not know you.
Is a chatbot the same as an AI agent? No. A chatbot follows a designed flow; an AI agent understands free text and decides what to answer.



