WhatsApp Business Platform Review (2026)
Since July 2026 Meta ships its own agent on its own channel, billed per token, uncapped by default, with zero pre-built connectors.
Some links on this page can be affiliate links. We may earn a commission at no cost to you. This never affects our rankings. How we work.
What the score measures. Five things we can verify from published material: whether pricing is transparent, whether the product can act on your systems or only answer from documents, whether the vendor still owns its own roadmap, how much independent review evidence exists, and whether the bill stays predictable as volume grows. Weighted, then scored against an ideal platform that scores 5.
BEST FOR: BUSINESSES WHOSE SUPPORT ALREADY LIVES ON WHATSAPP · LAST UPDATED 2026-08-21
WhatsApp Business Platform in depth
This is infrastructure rather than an application. There is no inbox, no agent seat, no ticketing, no reporting UI. You get an API layer and a webhook contract, and you build everything a support team touches.
The material change since anyone last reviewed this is that Meta launched the Meta Business Agent Platform on 1 July 2026. In Meta's own words, it is an AI agent for WhatsApp that answers questions, takes actions through your systems, and hands off to your app. Before that, the WhatsApp Business Platform had no AI in it at all. It was a transport.
What it does
- Cloud API for messaging, calling and groups
- Business Management API for numbers, templates and analytics
- Meta Business Agent, launched 1 July 2026, as a fifth component
- Connector Tools: your own APIs, registered with a JSON schema the agent populates
- Thread control, so your app can take over and hand back
- Agent Events, letting your backend make the agent speak
- Token budgets over rolling 1, 7, 14 or 30-day windows
More detail on how it works
That makes Meta the only vendor in this directory that is simultaneously the channel, the agent and the meter. Every other WhatsApp product here is a customer of the thing it resells, which is worth holding in mind when their pricing pages describe what WhatsApp costs.
Genuinely agentic, and the schema is what proves it
Most products in this directory describe an action that turns out to be a flow step fired by a trigger. Meta's is not that. Connector Tools are registered with a stable key described as visible to the agent, and the schema documentation instructs you to define explicit properties with types and descriptions rather than leaving an object undefined, because the agent needs a fully specified schema to correctly populate the request. That is LLM tool-calling. The agent decides a call is needed, fills in the arguments and executes. Meta also names booking an appointment and confirming a payment as example actions, so writes are in scope, not only lookups.
The agent is the primary responder, and you are the fallback
This inverts the usual arrangement. When Meta Business Agent is enabled it acts as the primary responder for the conversation, and your application receives standby webhooks. You take control by sending a message, and pass it back through thread control. There is also a channel running the other way: your backend can post an agent event when an order or shipping status changes, and the agent tells the customer. Which webhook field a customer message arrives on depends on who currently holds thread control, and that is the detail people get wrong first.
Zero pre-built connectors, and Meta says so by implication
Connectors let the agent take actions in your systems by calling external APIs, and the examples given are retrieving customer information, checking product availability, checking order status and accessing schedules. Meta then adds that these are examples of what businesses connect, not a fixed set of categories. There is no integrations directory because there are no integrations. Every one is an API you author, register and authenticate. Note the tension worth reading carefully: every example in that sentence is a read, while the overview names booking and payment confirmation as actions.
Eligibility is a gate, not a setting
Meta's own overview says all verticals are supported except finance, government, health, alcohol, gambling, over-the-counter drugs and matrimony services, and that the account must have a valid business category set. The other requirement catches more people: the account must be managed through the WhatsApp Business Platform on the Cloud API, including through a solution partner, and explicitly not through the WhatsApp Business app. Meanwhile Meta's consumer marketing sells a same-named product as three easy steps with no coding required, starting by setting up Meta Business Agent in the WhatsApp Business app. Two products share one name and the marketing route is the one the developer docs disqualify.
Setting WhatsApp Business Platform up
Realistic time to a working deployment: Weeks. This is an API and a webhook contract, not a product you log into.. Read from the vendor's own documentation.
- 01
Create a Meta app with the WhatsApp use case
Requires a Facebook account and developer registration.
- 02
Connect a WhatsApp Business Account
Then generate a temporary token and send a test message to prove the path works.
- 03
Stand up a webhook endpoint
A server you host. There is no hosted inbox, no queue and no agent desktop anywhere in this product — you build all of it.
- 04
Create a system user and a permanent token
Scopes: business_management, whatsapp_business_messaging, whatsapp_business_management.
- 05
Accept the Meta Business Agent terms in WhatsApp Manager
Solution providers must separately accept the Tech Provider terms or the API calls are simply rejected.
- 06
Subscribe the app and its webhooks
messages, standby and messaging_handovers. Which field a customer message arrives on depends on who currently holds thread control — the split that catches people.
- 07
Configure skills, business info, FAQs and connectors
Every connector is an API you write, register with a JSON schema and authenticate. Meta ships none.
- 08
Set an agent budget before you go live
Token budgets take rolling one, seven, fourteen or thirty-day windows. An empty budgets array means no cap and unlimited spend, and that is the default.
The step that takes longer than they imply. The eligibility gate for Meta Business Agent, which you cannot engineer around: an approved country, a permitted vertical, business verification, and an account on the Cloud API rather than the WhatsApp Business app. Meta's own consumer marketing sells the agent as three no-code steps starting in that app — the route its developer docs list as disqualifying.
What the AI actually does
Every platform here says “AI agent”. It covers a bot that reads your help centre and a system that can refund a customer. This is which one you are buying.
The only WhatsApp-native product here where the AI itself decides to call an API, populates the arguments from a schema and executes.
Meta ships no connectors, so every system it reaches is one you built and registered.
- Connector Tools are registered with a key Meta describes as visible to the agent, plus a JSON schema the agent populates itself
- Meta's own documentation names booking an appointment and confirming a payment as example actions, so writes are in scope rather than lookups only
- When enabled, the agent is the primary responder and your app receives standby webhooks, taking control by sending a message
- Agent Events run the other way: your backend posts an order or shipping change and the agent tells the customer
- Zero pre-built business-system connectors, and Meta says the categories it lists are examples rather than a fixed set
- Billed per token at $2.00 per million since 1 August 2026, uncapped unless you set an agent budget
Who Should Use It
The second list is the more useful one.
Worth a look if
Your support already lives on WhatsApp, you have engineers, and you would rather own the integration than rent someone else's. The pricing documentation is the most precise in the category, with a published calendar, committed notice periods and worked examples. No seats and no minimum means a small volume genuinely costs very little. And the tool-calling contract is real, which is more than most of this directory can say.
Who should look elsewhere. Anyone without engineers. There is no product to log into and nobody to answer a customer. It is also closed to finance, government, health, alcohol, gambling, over-the-counter drugs and matrimony businesses, closed to anyone still on the WhatsApp Business app rather than Cloud API, and a poor fit for anyone who needs a predictable monthly bill, since per-token pricing with no default cap is the opposite of one.
Strengths and Weaknesses
What Works
- The only genuinely agentic option among the WhatsApp-native products here, with a real tool-calling contract rather than a triggered flow step.
- Pricing documentation includes a published change calendar with committed notice periods, worked cost examples, and Meta's own comparison against third-party AI.
- Token budgets over rolling windows exist, and free test messages plus an evaluation harness let you check behaviour before go-live.
What Does Not
- A consumer marketing page sells a same-named product whose setup route the developer docs list as disqualifying.
- Zero pre-built connectors means every integration is a build.
- Per-token billing makes cost per conversation genuinely unpredictable, with Meta's own examples spanning 16 to 50 cents.
- Two significant price increases land ten weeks apart.
- And you get no inbox, no reporting and no agent tooling.
WhatsApp Business Platform pricing
There is no subscription and there are no seats. You pay for messages you send. Non-template messages inside the 24-hour customer service window have been free, utility templates in response to users are free, and everything is free for 72 hours inside a free-entry-point window.
Since 1 August 2026 Meta Business Agent messages are billed per token at one global rate of $2.00 per million tokens. Meta estimates 20,000 to 25,000 tokens per message, roughly 4 to 5 cents. Its own worked examples are the honest unit: a simple what-time-do-you-open runs about 16 to 20 cents across four messages, and a complex walkthrough 40 to 50 cents across ten.
The full arithmetic
Meta Business Agent messages are free in neither window. Not the 24-hour service window, not the 72-hour free entry point. The token charge applies regardless.
From 1 October 2026 Meta starts charging for service messages, which have not been charged since November 2024, and for utility messages sent in response to users inside an open 24-hour window. That change matters beyond this page, because at least two other vendors in this directory currently publish some version of inbound is free. Both statements are true today and false in October.
The default spend cap is none. The Agent Budget API takes token budgets over rolling 1, 7, 14 or 30-day windows, and an empty budgets array means no cap and unlimited usage. Set one before you go live rather than after.
Custom and private pricing
WhatsApp Business Platform does not publish a rate. You have to ask, which means a sales conversation before you can compare it against anything else on this site.
Ask two things on that call: what triggers a billable event, and what the rate is at twice your current volume.
INTEGRATIONS
Our Recommendation
Who we would tell to buy this, and who we would not.
The most capable agent on the most common support channel, sold as a parts kit with the meter running. If you have engineers, this is the version of WhatsApp AI where you own the integration and pay Meta directly instead of paying a reseller to pay Meta. Set an agent budget before your first live conversation, and read the October price change before you model anything, because it retires the free-inbound assumption that most WhatsApp cost comparisons still rest on.
Where we write about WhatsApp Business Platform
2 pieces on this site name it.
- Chatfuel ships four autonomy levels and starts every bot on the one where the AI writes nothing.Every vendor here will tell you their agent takes action, and almost none will say who approves it or where the record lands. One small vendor publishes a four-level autonomy slider the rest of the category should be measured against.
- Meta started billing its own WhatsApp agent by the token on 1 August. Almost every explainer of it is wrong.Meta Business Agent is the first AI in this directory billed per token rather than per resolution or per seat. The rate is published and checkable, the vendor explainers describing it get the mechanism wrong, and there is a spend ceiling that does not exist unless you set it.
Similar Tools
Others in ai agents & chatbots.
Fin (formerly Intercom)
Teams already on Fin who can absorb variable per-resolution billing
4.2 / 5 · $0.99/resDecagon
Large support organisations that need the agent shaped to existing procedures
3.1 / 5 · Not publishedSierra
Enterprises wanting one vendor across chat and phone
3.1 / 5 · Not published
Ada
Global brands needing many languages and channels at once
3.5 / 5 · Not publishedFrequently Asked
The questions people actually search for about WhatsApp Business Platform.
How much does Meta Business Agent cost?
$2.00 per million tokens, one global rate, since 1 August 2026. Meta estimates 20,000 to 25,000 tokens per message, about 4 to 5 cents. Its own worked examples are more useful: a simple opening-hours question runs 16 to 20 cents across four messages, and a complex walkthrough 40 to 50 cents across ten. There is no subscription and no seat cost underneath it.
Are inbound WhatsApp conversations still free?
Today, mostly. Inbound customer messages are never charged and non-template replies inside the 24-hour service window have been free. From 1 October 2026 Meta begins charging for service messages, which have not been charged since November 2024, and for utility messages sent in response to users inside an open window. Meta Business Agent messages are already outside both free windows, so the token charge applies regardless.
Can Meta's agent actually do things in my systems?
Yes, through Connector Tools, and the mechanism is real LLM tool-calling rather than a triggered flow step. Tools are registered with a key described as visible to the agent and a JSON schema, and Meta's documentation says the agent needs a fully specified schema to correctly populate the request. Meta ships zero pre-built connectors, so every integration is an API you write and authenticate yourself.
Who is not eligible for Meta Business Agent?
Meta's overview excludes finance, government, health, alcohol, gambling, over-the-counter drugs and matrimony services, and requires a valid business category on the account. The requirement that catches more people is the platform one: the account must run on the Cloud API, including via a solution partner, and explicitly not on the WhatsApp Business app.
Is there a spend cap by default?
No. The Agent Budget API accepts token budgets over rolling 1, 7, 14 or 30-day windows, and an empty budgets array means no cap and unlimited usage. That is the default state, so setting a budget is something you do before going live rather than something you inherit.
Is this an alternative to Gorgias or Intercom?
Not really. It is the layer underneath. There is no inbox, no queue, no ticketing and no agent desktop, and most WhatsApp-capable tools in this directory are built on top of this platform rather than competing with it. Buying direct means owning the integration work those vendors do for you, in exchange for paying Meta's rate rather than a reseller's.