WhatsApp Business API automation means using the WhatsApp Business Platform, through Meta’s Cloud API or a solution partner, to capture leads, qualify them, book meetings, answer routine support questions and hand complex chats to people, with every conversation synced to your CRM. It works best with clear opt-in, correctly categorised templates and tight cost control.
This guide is for B2B and services teams that sell and support through conversations. It covers the app versus the platform, Meta’s message categories and pricing after the 1 October 2026 change, consent, bot design, human handoff, CRM integration, measurement and a 30-day rollout plan.
Key takeaways
- Use the free WhatsApp Business app for manual replies; move to the WhatsApp Business Platform for automation, CRM sync, several agents or volume.
- Meta charges per delivered message by category; from 1 October 2026 service replies beyond 1,000 free per number each month, and utility replies, are charged too.
- Opt-in must name your business and say what people will receive; make opting out easy.
- Start with button menus, add AI only with guardrails, and always offer a fast route to a human.
- Treat the CRM as the source of truth and track cost per qualified lead from day one.
What does recent Meta documentation say about WhatsApp Business API automation?
According to Meta’s WhatsApp Business Platform pricing documentation (updated for 2026), Meta has charged per delivered message since 1 July 2025, and each business phone number gets a free tier of 1,000 delivered service messages per month. Meta’s pricing update notes (2026) say that from 1 October 2026 it charges per message for service messages, which had not been charged since November 2024, and for utility messages sent in response to users, which had not been charged since July 2025. A new Meta Business Agent category has been charged per token since 1 August 2026.
Messages in a free entry point window, opened when someone messages you from a click-to-WhatsApp ad or Facebook Page call-to-action, remain free for delivery; Meta’s pricing page says that window can stay open for up to 7 days. Meta also says it may update pricing only on the first day of each quarter, so up to four times a year.
Charges in Meta’s worked example of a five-message conversation
Scale is governed separately. Meta’s messaging limits documentation (2026) says limits cap how many unique users a business portfolio can message outside a customer service window in a moving 24-hour period. New portfolios start at 250, can reach 2,000 through business verification or high-quality sending, then scale automatically to 10,000, 100,000 and unlimited, shared across all numbers in the portfolio.
Do you need the WhatsApp Business app or the WhatsApp Business Platform?
The WhatsApp Business app is a free phone app for one business number, used by people typing replies. The WhatsApp Business Platform is the API product: you connect through Meta’s Cloud API directly or through a Solution Partner or Tech Provider, and software sends and receives messages. Automation, CRM sync and multi-agent inboxes need the platform.
| Factor | WhatsApp Business app | WhatsApp Business Platform (Cloud API) |
|---|---|---|
| Best for | Owner-led businesses replying by hand | Teams automating sales and support at volume |
| Set-up | Download, verify number, add profile | Meta business portfolio, Messaging account, phone number, templates, webhooks; directly or via a partner |
| Automation | Greeting, away messages and quick replies | Bots, CRM-triggered templates, routing, integrations |
| Throughput | Manual pace | Up to 80 messages per second per number by default, per Meta (2026) |
| Cost | Free to download | Per delivered message by category; partner fees may apply |
You do not always have to choose. Meta’s coexistence documentation (2026) lets partners onboard an existing WhatsApp Business app number to Cloud API so staff can keep chatting one-to-one in the app. There are trade-offs: such numbers have a fixed throughput of 20 messages per second, broadcast lists are disabled and some features, such as group chat sync, are not supported. Meta’s partner documentation says Solution Partners can extend credit lines to clients; Tech Provider clients add their own payment method.
How do message categories and pricing work for sales and support?
Meta’s pricing page lists five categories: marketing, utility and authentication templates, service messages (non-template replies) and Meta Business Agent messages. Its template documentation (2026) says templates are the only messages you can send outside a customer service window, and review can take up to 24 hours. A 24-hour customer service window opens each time a user messages you; within it you can send free-form replies.
Category depends on purpose: a meeting reminder is utility; a discount nudge to book a demo is marketing. Plan costs on the honest category.
| Use case | Likely message category | Cost note (check the current rate card) |
|---|---|---|
| Reply to a click-to-WhatsApp ad lead | Service, inside a free entry point window | Free while the window is open |
| Qualification questions after a website chat starts | Service | 1,000 free per number monthly, then charged |
| Meeting confirmation and reminder | Utility template | Charged; volume tiers can lower rates |
| Proposal follow-up or webinar invite | Marketing template | Charged; per-user limits apply |
| Ticket update or order status (B2B) | Utility template, or service if inside the window | Charged from 1 October 2026 even inside the window |
| CSAT survey after a ticket closes | Utility if purely about the case | Charged per delivered message |
Marketing templates have an extra delivery constraint. Meta’s per-user marketing limits page (2026) says WhatsApp may limit how many marketing templates a person receives from businesses based on their recent engagement, and that it does not currently deliver marketing templates to US phone numbers.
What consent do you need before automating WhatsApp messages?
The WhatsApp Business Messaging Policy requires opt-in before you message someone. Meta’s opt-in guidance says the opt-in must clearly state that the person is agreeing to receive messages and must name your business. It recommends separate opt-in by message category, clear opt-out instructions and watching your quality rating when you launch a new opt-in method.
- Forms: add an unticked WhatsApp checkbox with plain wording, for example ‘Send me meeting reminders and updates on WhatsApp from [Company]’.
- Ads: messaging you from an ad is not blanket consent for later marketing; ask inside the chat.
- Records: store consent source, timestamp, wording version and category in the CRM so it travels with the contact.
- Opt-out: honour STOP or ‘unsubscribe’ replies automatically and sync them back to the CRM within the same run.
In India, the Digital Personal Data Protection framework published on the MeitY data protection page is being phased in. Collect only the data you need, state the purpose, make withdrawing consent as easy as giving it, and keep chat transcripts for a limited period. Ask a lawyer to review your notices and processor contracts; this guide is not legal advice.
Which sales workflows should you automate on WhatsApp first?
For B2B and services firms, WhatsApp is a conversation channel beside email and calls, not a broadcast tool. If you run a store, the email and WhatsApp marketing guide for eCommerce covers carts and orders; these workflows suit lead-driven businesses.
1. Lead capture from click-to-WhatsApp ads
What: Facebook and Instagram ads that open a WhatsApp chat.
Why: They open a free entry point window and skip the form.
How: Use one prefilled message per campaign so the bot knows the source, and pass the ad ID to the CRM. The Meta Ads guide covers campaign structure and targeting.
2. Qualification bot
What: Three to five button-based questions: need, company size, timeline, location, budget band.
Why: It sorts serious enquiries before a salesperson spends time.
How: Map each answer to a CRM property, using the definitions from your lead management and sales handoff process so marketing and sales agree on what ‘qualified’ means.
3. Appointment booking
What: Offering open calendar slots in the chat and confirming the booking.
Why: Every extra step between interest and a call loses people.
How: Show slots as an interactive list, write the meeting to the CRM, and send a utility reminder the day before.
4. Follow-ups after meetings or proposals
What: Short, person-signed messages after a demo, proposal or site visit.
Why: A short nudge gets attention; too many hurt quality ratings.
How: Trigger from deal stages, cap follow-ups per deal, and stop on reply or opt-out.
How should WhatsApp support automation work?
5. FAQ answers
What: Instant answers to repeated questions such as service areas, documents needed and hours.
Why: It shortens queues and frees agents for real problems.
How: Answer from one approved knowledge base and offer “Talk to a person” in every reply.
6. Order, project or ticket status
What: A lookup by reference number that returns the current status from your system.
Why: Status questions are frequent and factual, so safe to automate.
How: Verify the person (matching phone number or a code) before showing account data, and keep replies short.
7. Ticket handoff to humans
What: Creating a ticket with the transcript and routing it to the right team.
Why: Customers hate repeating themselves; a clean handoff makes automation feel helpful.
How: Pass summary, category and customer ID into the ticket and tell the customer the expected reply time.
8. CSAT after resolution
What: A one-tap rating when a ticket closes.
Why: It shows quality by channel and agent.
How: Use three buttons, write the score to the ticket and alert a lead on low scores.
Menus, NLP or AI agents: which chatbot design fits?
| Design | Strengths | Risks | Use when |
|---|---|---|---|
| Menus and buttons | Predictable, cheap, easy to test, clean CRM data | Feels rigid for open questions | Qualification, booking, status lookups |
| NLP intent matching | Handles free text for known intents | Needs training data and upkeep; misroutes | Many varied FAQs in one domain |
| AI agent (LLM) with guardrails | Natural answers across a large knowledge base | Wrong or invented answers, cost per token, data exposure | High volume, good knowledge base, strong review process |
Guardrails for AI agents: answer only from approved sources, refuse pricing commitments and legal advice, never collect card numbers in chat, log answers for review, and hand off on low confidence. If you use Meta Business Agent rather than your own model, remember those messages are billed per token. Our AI workflow automation guide covers review loops in more depth.
When should the bot hand a WhatsApp conversation to a human?
- The person types “agent”, “human”, “call me” or similar, or taps a handoff button.
- The bot fails to understand twice in a row.
- The lead scores as high value and a salesperson is free.
- The message shows complaint, cancellation or legal language.
Outside business hours, say when someone will reply. When an agent takes over, pause the bot on that thread.
How do you connect WhatsApp to HubSpot or Zoho CRM?
Meta’s platform overview (2026) says the platform relies heavily on webhooks, and that delivery status updates are reported by webhook. A practical architecture has four parts:
- Inbound: a webhook receives each message and status update, matches the sender by phone number or business-scoped ID, and creates or updates the contact.
- Logic: a bot or integration layer (native, a partner platform, or tools such as Make, Zapier or n8n) runs the flow and writes properties.
- Outbound: CRM events (new lead, stage change, meeting booked) trigger approved templates via the API.
- Reporting: cost and outcome fields feed dashboards.
Native options exist. HubSpot’s knowledge base article on connecting WhatsApp says the integration needs a Professional or Enterprise subscription to Marketing Hub or Service Hub, links conversations to contacts whose phone property matches, and syncs only new messages. Zoho’s help article on WhatsApp for Business says its integration is available in all paid editions, logs messages against records and can send templates from its automation tools. Check both pages as of November 2026, as plans change. Record design is covered in the Zoho CRM guide and HubSpot CRM guide, and Bargaon’s marketing automation service helps teams plan this architecture.
Should this workflow run on WhatsApp, and how automated should it be?
Do you hold category-specific opt-in for this contact? If not, stop or ask for it first.
Is the message short, time-sensitive and useful? If it is long or reference material, use email.
Name the honest category and estimate monthly cost at expected volume before building.
Factual and repetitive: automate. Judgement or money involved: assist a human.
Define the handoff trigger, owner and CRM fields before launch.
How do you keep WhatsApp Business API costs under control?
- Use click-to-WhatsApp ads and Page buttons where conversations start, to benefit from free entry point windows.
- Track usage against the 1,000 free service messages per number per month.
- Review spend by template weekly in the first quarter.
- Move newsletters and long content to email, following the email deliverability guide.
What should you measure in WhatsApp sales and support automation?
Track a short scorecard: opt-in rate by source, bot completion rate, qualified leads and meetings booked, cost per qualified lead (Meta billing joined to CRM data), first response and resolution time, handoff rate, CSAT, and opt-outs, blocks and template status.
Meta’s template documentation notes that templates can be paused for recurring negative feedback or low read rates, so check template status weekly. For the wider picture, see the marketing automation guide.
What does a WhatsApp sales flow look like in practice?
Hypothetical example: a Noida-based IT services firm runs click-to-WhatsApp ads for a cloud migration audit. A prospect taps the ad, and the bot (inside the free entry point window) asks four button questions: company size, current cloud, timeline and role. Qualified prospects see three calendar slots; others get an email guide. The CRM receives the contact, ad ID, answers, consent record and meeting. A utility reminder goes the day before. After the call, the salesperson sends one personal follow-up; if there is no reply in a week, the deal moves to email nurture. No results are implied; this only illustrates the design.
What are the most common WhatsApp automation mistakes?
- Uploading purchased or old phone lists and messaging them without opt-in.
- Labelling promotional content as utility and getting recategorised.
- Bots with no exit to a human, or with long free-text questions.
- Keeping chats on salespeople’s phones, outside the CRM.
- Budgeting with pre-October 2026 assumptions that service replies are free.
- Ignoring quality rating and template status.
How do you roll out WhatsApp automation in 30 days?
| Days | Focus | Output |
|---|---|---|
| 1–7 | Choose set-up, verify the business, map consent | Account live, CRM fields created |
| 8–14 | Build one sales and one support flow; submit templates | Approved templates, handoff rules |
| 15–21 | Connect the CRM; soft launch with one ad set or segment | Live CRM data, cost tracking |
| 22–30 | Review completion, handoff, CSAT and cost; add one use case | Report and backlog |
Which related guides should you read next?
- Marketing automation for the wider automation strategy WhatsApp fits into.
- Lead management and sales handoffs to define qualified leads and routing rules.
- Zoho CRM to design records and workflows that WhatsApp will feed.
- Email deliverability for the channel that carries longer follow-ups.
- Email and WhatsApp marketing for eCommerce if you also sell online.
Frequently asked questions
Is the WhatsApp Business API free?
No. Meta charges per delivered message by category, and partners may add fees. Service messages are free up to 1,000 per business phone number per month, and messages in a free entry point window are free for delivery.
Can I send WhatsApp messages to leads who have not opted in?
No. The WhatsApp Business Messaging Policy requires opt-in, and the opt-in must name your business and say what people will receive. Message only people who have agreed, and record that consent.
What is the 24-hour customer service window?
Each user message opens a 24-hour window for free-form replies. Outside it, you need an approved template.
Can I keep using the WhatsApp Business app after moving to the API?
Yes, through coexistence if your partner supports it, with limits: 20 messages per second and no broadcast lists.
Should I use an AI chatbot on WhatsApp?
Only with a reliable knowledge base, guardrails, review and fast human handoff. For qualification and booking, button menus are more predictable and cheaper.
How quickly can I scale WhatsApp messaging?
New business portfolios start at 250 unique users per 24 hours outside service windows. Business verification or sustained high-quality sending raises this to 2,000, then limits scale automatically while quality stays high.
Sources and further reading
- Meta for Developers: Pricing on the WhatsApp Business Platform
- Meta for Developers: Pricing updates (2026)
- Meta for Developers: Messaging limits
- Meta for Developers: Template fundamentals
- Meta for Developers: Per-user marketing limits
- Meta for Developers: Get opt-in for WhatsApp
- Meta for Developers: Coexistence onboarding
- Meta for Developers: Solution Partner overview
- WhatsApp: Business Messaging Policy
- HubSpot Knowledge Base: Connect WhatsApp
- Zoho CRM Help: WhatsApp for Business integration
- MeitY: Data protection framework
- Editorial note: the Fit Check, 30-day plan and IT services example are Bargaon editorial models, not research data.
Planning WhatsApp automation for sales or support? Bargaon’s marketing automation service can help you map consent, flows, CRM fields and cost tracking before you build.