Our previous post covered what Meta’s Business AI Agent is in plain terms. This one is for the more technical case: if you’re already running the WhatsApp Business (Cloud) API — through a Business Solution Provider like WhatsApp Hub, or directly — the agent isn’t just a Meta Business Manager checkbox. It has a real, documented API surface, and understanding its shape matters if you want to know what actually happens to your numbers and your existing inbox when you turn it on.
Two integration patterns
Meta’s own developer documentation lays this out for two cases. A business managing its own WhatsApp Business Account (WABA) directly can configure the agent using its own system-user token. A platform operating WhatsApp on behalf of multiple client businesses — what Meta calls a Business Solution Provider or Tech Provider, which is what a platform like WhatsApp Hub is — can configure and manage the agent on a client’s WABA using a business-integration system-user token, the same delegated-access model already used for template and phone number management.
It’s a staged flow, not a single switch
Configuration happens at the phone number level within a WABA, not account-wide. Per Meta’s documentation, the flow moves through distinct stages:
- Eligibility — checking whether a given number can use the agent at all.
- Onboarding — assigning the WABA to the agent.
- Configuration — skills, business information, FAQs, connected websites, uploaded files, and third-party connectors.
- Operation — thread control, agent events, and testing/evaluation endpoints for day-to-day running.
Each stage is its own set of API calls, not a single on/off toggle — worth planning for as a proper implementation phase, not a five-minute setting change.
What happens to your existing inbox
The part that matters most for anyone already running a team inbox: once the agent is live on a number, your own platform doesn’t lose visibility into the conversation. Meta places your integration in what it calls standby — you keep receiving copies of the messages the agent is handling — and there’s a dedicated Thread Control endpoint that lets you explicitly take a conversation back (Meta calls this a “pass” action) the moment a human needs to step in.
That’s the mechanism that makes “AI handles the easy stuff, a person handles the rest” actually work operationally, rather than just as a slide in a pitch deck — nothing about it requires the customer to start a new conversation, or the hand-off to be manual on Meta’s side.
On cost
Meta has published API-connected pricing at $2.00 per 1 million tokens, effective 1 August 2026 — a genuinely different cost model from the per-conversation pricing that governs regular template and session messages, so it’s worth budgeting for separately rather than assuming it folds into your existing conversation costs. Confirm current rates directly with Meta before committing volume, since token-based AI pricing is a newer, faster-moving line item than conversation pricing.
Should you build against this yourself?
Eligibility, onboarding, and eligibility-gating by country and vertical mean this isn’t yet a flip-a-switch feature for every business — test the Eligibility endpoint for your specific number before assuming it’s available. Treat the Skills/FAQs/Connectors configuration step as the real work: an agent is only as good as what it’s been given to work from.
Takeaway
The Business AI Agent is a proper API integration, not a settings toggle — eligibility and onboarding first, real configuration effort second, with your existing team inbox kept in standby rather than cut out. If you’re evaluating this for your own numbers, the background on what the agent actually is and isn’t is worth reading first: Meta Business AI Agents on WhatsApp: What They Are and What They Change.
Leave a Reply