How do we build a WhatsApp bot that replies to leads and updates the CRM?
Use the official WhatsApp Business Platform, create the lead on the first message, qualify in a few questions, hand off to a person, and plan for Meta's service message pricing.
On this page · 10
In short: Use the official WhatsApp Business Platform (Cloud API), create or update the lead in the CRM as soon as the first message arrives, then let the bot ask a few qualifying questions and hand off to a person with the full conversation. Replies inside the 24-hour customer service window are service messages; since October 1, 2026 Meta charges for them after the first 1,000 delivered per business phone number per month, so plan for that cost. Messages outside the window need an approved template.
Step 1: Choose the official API
| Option | What it means |
|---|---|
| WhatsApp Business Platform (Cloud API), directly or via a provider | Official, supports templates, webhooks and scale; billed by Meta |
| Unofficial gateways that automate the WhatsApp app | Risk of the number being banned; not suitable for business-critical lead flows |
For lead handling that has to be reliable, use the official platform. Unofficial gateways can be fine for internal experiments.
Step 2: Create the lead first, then qualify
When a message arrives on the webhook:
- Look up the phone number in the CRM.
- If it is new, create the contact and a lead or deal immediately, with source = WhatsApp.
- Log the message on the record.
- Only then start qualifying questions.
If the bot qualifies first and creates the lead at the end, every abandoned conversation is a lost lead. We wrote about this in create the lead before you qualify it.
Step 3: Keep the questions short
Ask two to four questions that decide routing: what they need, where they are, and when. Save each answer to a CRM property. Use buttons or lists where possible so answers are clean.
Step 4: Route and hand off to a person
| Situation | Action |
|---|---|
| Qualified, in business hours | Assign an owner by rule, notify them, keep the chat open for them |
| Qualified, out of hours | Confirm a callback time, create a task |
| Asks for a person | Hand off immediately with the transcript |
| Not a fit | Polite answer, mark the reason |
See our lead routing use case for assignment rules. GoHighLevel users can run this inside GHL conversations; see GoHighLevel services.
Step 5: Understand the cost from Meta's pricing
From Meta's pricing page:
| Message type | How it is charged |
|---|---|
| Messages from the user to the business | Free |
| Service messages (non-template replies) inside the 24-hour customer service window | From October 1, 2026, charged after a free tier of 1,000 delivered per business phone number per month; the tier resets monthly and does not roll over |
| Messages in a free entry point window (for example from a click-to-WhatsApp ad) | Free, except Meta Business Agent messages |
| Template messages outside the window | Charged per Meta's rate cards by category and country |
Without a payment method on the account, Meta stops delivering service messages once the free tier is used. Check the current rate card for your countries before you estimate monthly cost.
Step 6: Test before launch
- New number, returning contact, and a contact already in the CRM with a different format of the same number.
- A message outside business hours.
- A person asking for a human in the first message.
- A webhook failure: the message must still reach the CRM on retry.
FAQ
Can a WhatsApp bot update HubSpot or GoHighLevel?
Yes. The bot creates or updates the contact on the first message, logs the conversation and writes answers to CRM properties.
Are WhatsApp replies to customers free?
Not always any more. From October 1, 2026, Meta charges service messages after the first 1,000 delivered per business phone number per month. Messages from users to you remain free.
Do I need templates?
Only to start or restart a conversation outside the 24-hour customer service window. Replies inside the window can be free-form.
Should the bot answer everything?
No. Let it capture the lead and qualify, and hand off quickly. People should be able to reach a person at any point.
How Octacer helps
Octacer builds WhatsApp lead and support bots on the official platform and connects them to HubSpot, GoHighLevel and other CRMs. For a support example, see our bilingual WhatsApp support triage playbook.
Next step
Count how many WhatsApp conversations you get per number per month and check Meta's rate card for your countries. Then book a call and we will scope the bot.
Sources
- Meta for Developers, WhatsApp Business Platform pricing: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing
Keep going
More guides
Want it running on your stack?
We implement this guide for clients, tailored to your stack, your data, and your team's workflow, and handed over documented.