Yes, for the standard route. A non-developer can install the WhatsApp integration from the Botpress Hub, press Authorize WhatsApp and click through Meta's prompts with a Facebook account. Help is worth paying for in three places: stalled Meta business verification, message templates, and the manual route that uses your own Meta app, tokens and webhooks.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe split matters because the whole job feels technical until you see it in pieces. Most of it is clicking, writing and testing, which an owner can do in an afternoon. The rest is either waiting on Meta, which no consultant can speed up, or developer-level plumbing that most small businesses never need. The sections below mark which is which, with costs worked out for an online clothing store.
What do you need before connecting Botpress to WhatsApp?
Connecting Botpress to WhatsApp needs a published bot and a Facebook account, according to Botpress's own short checklist. During setup you will be asked to create or select a Facebook business page and a WhatsApp business account, so decide beforehand which Facebook login represents the business. Using a personal profile that a former employee also owns is how companies end up locked out later.
A published bot means the bot already answers questions in Botpress Studio and you have pressed Publish. If you have not built one yet, start with the beginner FAQ bot tutorial and come back; the WhatsApp connection is a channel bolted on afterwards, not a different bot.
- A published Botpress bot, with the knowledge base filled in (covered below).
- A Facebook login that the business controls, not one tied to a single employee's personal profile.
- A Facebook business page and a WhatsApp business account, created or selected during setup.
- A WhatsApp business account for the business number. Read Meta's prompts carefully at this step, because the number rules are Meta's and can change.
- Your registered business details to hand, since Meta will check them. Matching names and addresses across your website, business page and registration saves time.
How do you connect Botpress to WhatsApp without code?
Install the WhatsApp integration from the Botpress Hub and press Authorize WhatsApp: Botpress documents this as the default path, and it needs no code. Allow 30 to 45 minutes for the clicking if your Facebook business page already exists, longer if you are creating everything fresh.
- Open your bot in Botpress Studio and select Explore Hub in the upper-right corner.
- Search for WhatsApp and select Install Integration.
- In the integration's Configuration menu, select Authorize WhatsApp.
- Follow the on-screen instructions to connect Botpress to your WhatsApp account. This is where you create or select the Facebook business page and the WhatsApp business account.
- Save the configuration and send a test message from a phone to confirm the channel is connected.
Botpress also publishes a video walkthrough of the same steps on its YouTube channel, which helps if you prefer to watch someone click through Meta's screens first. Meta changes its screens from time to time, so expect the wording to differ slightly from any written guide, mine included.
Why does the bot stay silent until Meta verifies the business?
Until Meta has verified your business, a Botpress bot cannot send messages to WhatsApp users, even if everything is configured correctly. After setup, Meta runs a business verification process, and Botpress also says it cannot help speed up Meta's process.
This is the single biggest source of "it doesn't work" messages from first-time owners, and it is not a fault with Botpress or with you. Plan around it. Start verification on day one, build and test the bot while you wait, and do not promise customers a WhatsApp launch date until the business shows as verified.
Testing while you wait: the WhatsApp Playground
Botpress built the Playground for exactly this gap. You need a published bot and a WhatsApp account. In Studio, open Explore Hub, install the WhatsApp integration, choose Test your agent on WhatsApp and follow the instructions. You then chat with your own bot from your own phone.
Use the wait productively. Send the bot twenty real questions from your enquiry inbox, note every wrong or vague answer, and fix the knowledge base each time. By the time verification clears you will have fixed most of the embarrassing answers in private.
Who does what: a task-by-task table
Here is how I would divide the work between an owner and a paid helper. "Alone" means following the vendor's own steps with no code.
| Task | Alone? | When paid help earns its fee |
|---|---|---|
| Install from the Hub and Authorize WhatsApp | Yes | Rarely; only if Meta's screens loop or reject your business page |
| Meta business verification | Mostly | If it stalls or is rejected; a helper can tidy your business records and resubmit, but cannot make Meta faster |
| Writing and loading the knowledge base | Yes | If you have hundreds of pages or conflicting price lists |
| Buttons and menus for choices | Yes | No |
| Human handover (Plus plan) | Mostly | If staff need routing rules, tags or out-of-hours logic |
| Message templates for messaging customers first | Partly | If templates keep being rejected or recategorised |
| Manual configuration with your own Meta app | No | Almost always; tokens, secrets and webhook fields |
| Connecting to a CRM or booking system | Depends | If the tool has no ready integration in the Hub |
The pattern is simple: everything on the standard route is point-and-click, and the paid-help rows are all places where something external (Meta, a CRM, staff rules) has to cooperate.
How do you write a knowledge base for a WhatsApp bot?
A WhatsApp bot answers well only if its knowledge base is clean, because WhatsApp users write short, impatient messages. Typical examples are "do you do size 14 in the blue one" or "where's my parcel". In Botpress Studio, open the Knowledge Base menu, select New Knowledge Base and add sources such as files, web pages or tables.
A new AI agent in Botpress already searches every knowledge base by default through the Search Knowledge card in its autonomous node. If you later create separate knowledge bases (say one for delivery and returns, one for sizing), you can choose which ones that card searches under Included Knowledge Bases. What you store counts towards vector storage, which Botpress's pricing page lists as 100MB on Free and 1GB on Plus.
A filled-in example: an online clothing store
Say the shop sells knitwear and ships from one warehouse. Rather than uploading the whole website, write one plain document with a heading per question people actually send. A fragment looks like this (illustrative wording, replace with your own policies):
DELIVERY
Standard delivery takes 3 to 5 working days. Orders placed before 1pm ship the same day.
Delivery is free on orders over $60; below that it costs $4.95.
RETURNS
You can return unworn items in their packaging within 30 days.
We refund to the original payment method within 5 working days of receiving the parcel.
Sale items can be exchanged but not refunded.
SIZING
Our knitwear runs true to size. If you are between sizes, choose the larger one.
The size chart is at [page link]. We cannot confirm stock for a specific size over chat;
send the customer to the product page.
Notice the last line: it tells the bot what it must not claim. A bot that confidently says "yes, size 14 is in stock" from a stale page costs you a return and a cross customer. For a longer treatment, see the FAQ your chatbot needs before launch.
What to do when the knowledge base has no answer
Botpress's autonomous node will generate a response when it finds nothing, which is where invented answers come from. The docs describe a way to catch the case: add a Transition card whose condition checks that no answer was found, and add a line to the node's prompt telling it to transition when no answer is found in the knowledge base. You can then send a fixed message such as "I'm not sure about that one, let me pass you to the team". That setup takes about ten minutes and is worth doing on day one.
If your product details live in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
What limits does WhatsApp put on menus and buttons?
WhatsApp shows one to three choices as buttons, four to ten as a dropdown, and eleven or more as multiple dropdowns, because Botpress maps a bot's choices to WhatsApp's own formats. Button titles are limited to 19 characters and dropdown titles to 23, so labels longer than that get cut.
Here is a before and after for the same shop's opening menu (illustrative):
| Before (breaks) | After (fits) |
|---|---|
| Track my current order status (28 characters) | Track my order (14) |
| Start a return or exchange (27) | Returns (7) |
| Delivery times and costs (25) | Delivery info (13) |
| Speak to a person (17) | Speak to a person (17) |
Four options would show as a dropdown; three would show as buttons, which are quicker for a customer to tap. If you can drop the menu to three, do: "Order help", "Returns and delivery", "Speak to a person". Count characters, including spaces, before you publish.
What does the Plus plan buy for handover to a person?
Handover to a person needs a Botpress Plus plan or higher, and Botpress's Human-in-the-Loop guide says a live agent can then join the bot's conversation. A WhatsApp bot that cannot hand over is a liability the first time someone is angry. Setup, as the docs describe it, is three moves: install the HITL integration from Explore Hub, install the HITL plugin and pick the integration in its configuration, then add a Start HITL card to the workflow at the point where handover should happen.
The card asks for a Ticket Title (what your staff see), a User ID and a Conversation ID. Botpress's page says to fill the last two with {{event.userId}} and {{event.conversationId}}. Botpress also notes that new workspaces are directed to its Botpress Desk product, while existing workspaces can keep the older HITL integration, so what you see in your own workspace may differ from this description. Read your Studio screens first.
Decide the handover rules on paper before you build them. For the clothing store they might be: any message containing "refund" over $100, any second "that's not what I asked", and anything about a damaged item goes to a person. When a chatbot should hand over to a human has a fuller list of triggers.
What will Botpress and WhatsApp messages cost?
Two meters run on a Botpress WhatsApp bot, Botpress conversations and WhatsApp messages, and owners often count only one.
Botpress: conversations
Botpress's pricing page shows Free at $0 with 100 conversations a month, Plus at $150 a month billed annually with 250 conversations, and Team at $750 a month billed annually with 1,500. Extra conversations come in packs of 100: $65 on Plus, $50 on Team, and none on Free. Packs are added automatically once you reach 95% of your quota, and the pricing FAQ says that auto-recharge cannot be turned off and that packs persist month to month until you remove them in billing settings.
The FAQ defines a conversation as any exchange with at least two messages from the end user in the billing month. A conversation spanning two months counts in both, each anonymous session counts separately, and emulator conversations count the same as real ones. So your own twenty test messages are not free once you pass the limit.
Meta: per delivered message
Meta charges per delivered message from the business to the user, never for messages users send you. Rates differ by message category and by the recipient's country calling code, so I will not quote a rate; read Meta's published rate card for the countries your customers are in. Two free allowances matter to a small shop: the first 1,000 service messages each month for each business phone number, and a free window when a customer arrives through a Click to WhatsApp ad. Replies a bot sends inside the open 24-hour customer service window count as service messages when they come from a third-party AI like Botpress, rather than Meta's own agent product.
A worked example with numbers
Take the clothing store with 600 customers a month who message at least twice. That is 600 Botpress conversations. On Plus, 250 are included and the other 350 need four packs (400 conversations), so the bill is $150 plus 4 x $65 = $410 a month, about $0.68 a conversation. At 1,000 conversations it is $150 + 8 x $65 = $670. Team at $750 starts to win once Plus would need ten packs, around 1,250 conversations, where Plus would cost $800.
The Meta side: if the bot sends four replies per conversation, 600 conversations produce 2,400 service messages. The first 1,000 are free, so 1,400 are chargeable at your market's service rate. Multiply that count by the rate on Meta's card and add it to the $410. Put both lines in a spreadsheet before you commit; the WhatsApp chatbot cost tutorial covers other tools' fees, and the Botpress pricing tutorial explains the plans in more depth.
The Tuesday the bot read everything and answered nothing
A scenario that matches Botpress's troubleshooting page: a shop finishes setup, tests well in the Playground, and goes live on a Monday. By Tuesday morning the Botpress logs show a stream of incoming WhatsApp messages and no replies going out. Nobody changed anything.
The page lists two likely causes. Either Meta has not finished verifying the business, in which case the bot cannot send at all, or the bot receives messages but cannot send back because of a problem with the payment method on the WhatsApp business account. The second one is easy to miss because everything else looks fine. Open the billing hub linked from Botpress's troubleshooting note, confirm a working payment method is attached, and send yourself a test. Add "payment method checked" to your go-live list.
Where paid help is worth the fee, and the brief to give
If you do hire, hire for the rows in the table that say "almost always" or "if it stalls". A decent brief is half a page. For this job it would read:
Goal: connect our published Botpress bot to WhatsApp and hand over to staff.
Already done: bot built, knowledge base loaded, Facebook business page exists.
Please do: Meta business verification support, message templates for
order updates, Human-in-the-Loop setup with these three triggers [list].
Please do not: change the knowledge base wording or the plan we are on.
Deliver: a one-page record of every account, login and setting changed,
and a test log of 20 messages with results.
Budget and deadline: [yours]
The "record of every account and login" line protects you more than any technical skill does. If you want help deciding whether you need an expert at all, this tutorial on hiring a Botpress expert sets out what to hire for and what to keep. And if you would rather map it with someone first, that is what my AI implementation consultation covers; see the contact page.
The manual route, in case you are told you need it
Botpress documents an advanced alternative that uses your own Meta app. You create a Meta developer app, choose Manual Configuration in the integration, and paste in a Verify Token (any alphanumeric string you invent), an Access Token, a Client Secret, a Default Bot Phone Number ID and a WhatsApp Business Account ID. You then copy the webhook URL and Verify Token from Botpress into your Meta app's configuration and subscribe to five webhook fields. Botpress's docs list them as message_template_components_update, message_template_quality_update, message_template_status_update, messages and template_category_update.
That is a one-hour job for a developer and a frustrating evening for anyone else. Most small businesses never need it. If a vendor tells you it is mandatory, ask why the standard route will not do.
A two-hour test script before you tell customers
Run this once verification has cleared. Use a phone that is not the one you set up with.
- Send ten ordinary questions straight from your last month of enquiries. Mark each answer right, vague or wrong.
- Send three things the bot must refuse or hand over: a refund demand, a complaint about a damaged item, a legal threat.
- Type a message in capital letters with spelling mistakes, then send a voice note and a photo. See what it does with each.
- Tap every button and dropdown option. Confirm no label is cut off.
- Trigger the handover and check that your staff member actually sees the ticket, with the right title.
- Send a message at an odd hour and confirm the reply says when a person will be back.
- Check the Botpress usage page afterwards to see how many conversations your test used.
Anything wrong goes back to the knowledge base, not into more prompt instructions. How to test a customer chatbot before it goes live has a longer list if you want it.
Questions owners ask before connecting WhatsApp
Do I need a developer to use the Botpress WhatsApp integration?
Not for the standard route. You install the integration from the Hub in Botpress Studio, select Authorize WhatsApp and follow Meta's prompts with a Facebook account. A developer becomes useful only for the manual route with your own Meta app, for custom workflows that call other systems, or when Meta's verification stalls.
Can I test the bot before Meta verifies my business?
Yes. Botpress offers a WhatsApp Playground that needs only a published bot and a WhatsApp account. It lets you chat with the bot on your own phone while verification is pending. Customers cannot receive replies from your business number until Meta has verified the business, so treat the Playground as a rehearsal.
Why does my bot receive messages but never reply?
Botpress's troubleshooting notes give two causes. If Meta has not verified your business yet, the bot cannot send messages to users. If it receives messages but does not send any back, check the payment method in your WhatsApp business account's billing hub. Fix whichever applies, then send a fresh test message.
Which Botpress plan do I need for WhatsApp and human handover?
Botpress's pricing page lists WhatsApp from the Plus plan upwards, and I found no WhatsApp entry in the Free column. Botpress's handover guide says the Human-in-the-Loop integration needs Plus or higher. Check the live pricing page before you build, because plans and limits change.
Further reads
- Botpress Not Working: Fixes for a Website Bot That Stays Silent — Fixes when a Botpress bot goes quiet
- Botpress and Calendly: Let a Website Bot Book Calls — Add call booking to the same bot
- Can a Takeaway Take Orders on WhatsApp With AI? — A food business taking orders on WhatsApp
- ManyChat vs Botpress: No-Code Flows or a Builder With More Control? — If Botpress feels heavy, compare a lighter builder
- How to Stop an AI Chatbot Giving Customers Wrong Answers — Keep the bot from inventing answers
- How to Train an AI Chatbot on Your FAQs, Policies, and Prices — Turn policies and prices into bot answers
Show 3 more related tutorials
- Is WATI Worth It? When a Shared WhatsApp Inbox Pays for Itself — WATI against the free WhatsApp Business app: what a shared inbox adds, what Growth and Pro cost, message fees, break-even and who should skip it.
- How to Connect Botpress to Google Calendar to Book Appointments — Map a website booking flow to real Calendar actions, then test busy slots, explicit confirmation, invitations and retry failures.
- Botpress for WordPress: Embed the Webchat and Test It First — Copy the Botpress embed code into WordPress with WPCode, test on a staging copy, and check styling, answers and conversation limits before going live.
Browse all AI-for-business tutorials
Sources: Botpress WhatsApp integration page and docs, Botpress pricing page, Botpress knowledge base and Human-in-the-Loop docs, Meta's WhatsApp Business Platform pricing page (all read 17 November 2026).
