Quick answer: Meta Business Agent or a third-party WhatsApp AI agent?
Meta Business Agent (MBA) is Meta’s own AI responder for eligible Cloud API / BSP-managed WhatsApp numbers. It becomes the primary responder, puts your BSP app into standby, and bills token usage directly with Meta (~$2 per 1M tokens, roughly a few US cents per message). Mark360 AI Agents are third-party agents on your WhatsApp stack — built for vertical journeys, CRM/Shopify tools, campaigns, and inbox coexistence without forcing Meta’s standby model as the only path.
- MBA Platform API path ≠ WhatsApp Business App “AI agent” path — different setup, eligibility, and billing.
- MBA excluded verticals include Finance, Government, Health, Alcohol, Gambling, OTC drugs, and matrimony (confirm via Meta’s eligibility endpoint).
- MBA billing bypasses the BSP for agent token charges; you still need a partner that handles standby webhooks and handoff.
- Third-party agents (Mark360) keep tool-calling, CRM writes, Shopify actions, and campaign orchestration in one product surface.
- Many teams will evaluate coexistence: MBA for simple FAQ coverage vs Mark360 for revenue workflows — not a blind either/or.
What Meta Business Agent is (and is not)
Meta launched Meta Business Agent for WhatsApp Cloud API numbers (including BSP and Embedded Signup numbers). On the Platform API path, MBA answers in the brand voice from uploaded knowledge, crawled sites, FAQs, and connectors (Meta has named systems such as Shopify and Zendesk among early connectors). It can recommend products, answer shipping/payment questions, and hand off when confidence is low or the user asks for a human.
Two products share the name:
| Platform API path | Business App path | |
|---|---|---|
| Who | Developers, enterprises, BSP clients | Small businesses on the WhatsApp Business app |
| Setup | API, system user, webhooks | In-app Tools tab, no code |
| Pricing | ~$2.00 / 1M tokens (AI + delivery bundled) | Free allowance then Meta One-style subscription (app path) |
| Billing | Meta bills the business directly | Via Meta One / app plan |
| Routing | Standby webhook + Thread Control | Manual takeover stops AI |
If you buy WhatsApp through a BSP, the Platform API path is the one that affects your integration. Do not assume MBA is “app only” or “unavailable on BSP numbers” — Meta’s docs include BSP-managed Cloud API numbers when eligibility passes.
Standby, handoff, and what happens to your BSP
When MBA is active as primary responder:
- Consumer messages arrive on your partner’s standby webhook while the agent holds control.
- messaging_handovers events fire when control moves between MBA and your app.
- Your app takes control by sending a message into the thread; releasing control returns the agent as automatic responder.
- MBA can auto-handoff on low confidence, integrity issues, or “human please” requests.
Operational implication: your shared inbox, bots, and CRM sync must understand standby. A BSP that only mirrors classic messages webhooks will look “quiet” while MBA is talking — until handoff.
For BSP-managed numbers, both the client MBA Terms of Service and the provider’s Tech Provider ToS generally need to be in place before API setup succeeds.
MBA pricing and billing (token model)
Public Meta / 360dialog explainers cite a global $2.00 per 1 million tokens for Platform API MBA messages, combining model usage and delivery into one charge. Rough public illustrations: ~20k–25k tokens per message → about 4–5 US cents per MBA message; multi-turn chats scale with turns. Cache tokens are described as free. Free messaging windows (24h / CTWA 72h) do not waive MBA token charges — delivery may be free in a window, tokens are still billed.
Meta bills MBA usage directly (credit line or card). Delivery can be gated until a payment method is attached to the Business Agent account. That is separate from your BSP’s WhatsApp conversation / template invoice.
Eligibility constraints buyers miss
Platform eligibility is strict (all required). Highlights:
- Supported vertical / category — exclusions include Finance, Government, Health, Alcohol, Gambling, OTC drugs, matrimony.
- Cloud API–managed number (BSP / Embedded Signup / direct) — not the consumer Business app number for the Platform path.
- WABA / business not restricted; country authorized for MBA; trust/verification bars; no conflicting messaging product on that number.
- Authoritative check: Meta’s agent eligibility API for the phone number ID.
Clinic, hospital, and some finance WhatsApp buyers often cannot lean on MBA even if they want Meta-native AI — third-party agents remain the practical path when policies allow messaging at all.
Mark360 AI Agents: third-party differentiation
Mark360 AI Agents sit on your WhatsApp Business API program as a product layer you control with Mark360 — campaigns, drips, inbox, and tools — rather than Meta owning the primary responder with your BSP forced to standby.
| Dimension | Meta Business Agent | Mark360 AI Agents |
|---|---|---|
| Who owns the brain | Meta agent runtime | Mark360 agent + your KB / tools |
| Billing for AI replies | Meta token invoice (direct) | Mark360 product + normal WhatsApp message categories (service/utility/marketing per Meta rules) |
| BSP coexistence | Partner app → standby while MBA controls | Designed as the automation/inbox layer on your number |
| Vertical / health exclusions | Hard MBA eligibility exclusions | Subject to WhatsApp messaging policies; not the same MBA vertical gate |
| Tools & systems | Meta connectors / skills model | CRM, Shopify, booking, catalog, campaign, and handoff flows you configure in Mark360 |
| Campaigns & drips | Not a replacement for BSP marketing orchestration | Native broadcasts, journeys, CTWA openers alongside agents |
| Best fit | Eligible brands wanting Meta-native FAQ/agent with direct Meta AI billing | SMBs and mid-market needing vertical journeys + Shopify/CRM actions on WhatsApp |
Practical Mark360 strengths for BSP buyers
- Tools that close work: order lookup, slot booking, cart recovery, lead qualification fields written to CRM — not only FAQ text.
- Shopify and commerce journeys: abandoned cart, COD confirm, delivery updates paired with agent deflection.
- Vertical flows: hotels, clinics (where WA messaging is allowed), education, real estate, restaurants — same broadcast / drip / chatbot framing Mark360 already documents.
- Human takeover that matches your inbox: AGENT keyword, VIP rules, complaint escalation without depending solely on Meta’s handoff settings.
- One surface for ads → chat → nurture: CTWA entry, then agent qualification, then drip — without splitting “Meta AI bill” vs “campaign tool” mental models mid-funnel.
Decision guide: when to enable MBA, Mark360, or both
- Check MBA eligibility first. If you are in an excluded vertical, skip MBA Platform path and invest in Mark360 (or another third-party) agents + compliance review.
- If FAQ volume is huge and you are eligible, MBA can be a Meta-native deflection layer — but budget tokens separately and confirm your BSP supports standby/Thread Control.
- If revenue depends on Shopify/CRM side effects, prefer Mark360 agents with explicit tools and test transcripts before any MBA cutover.
- Do not turn on MBA on a production number until billing is attached (unless allowlist-only test modes Meta documents) and your team understands standby silence in the inbox.
- Coexistence experiments: allowlist MBA for a segment; keep Mark360 journeys for campaigns and complex tools; compare CSAT, cost per resolution, and handoff rate.
- Remember Oct 1, 2026 service pricing: whichever AI you use, free-form service replies (including many bot replies) become chargeable after the free tier — AI does not create a free message category by itself. MBA tokens are an additional bill on top of or instead of classic service economics depending on path.
Buyer checklist for BSPs evaluating MBA
- Is the partner a Tech Provider with advanced messaging permissions?
- Do they document standby + messaging_handovers + Thread Control release?
- Is Meta vs BSP invoice split explained clearly (MBA tokens vs templates/service)?
- Can they run eligibility checks and dual ToS acceptance with you?
- What breaks in your current chatbot when the partner app is standby-only?
360dialog publishes deep MBA technical guides for infrastructure buyers. Mark360’s job in this comparison is the SMB/mid-market product decision: which agent actually runs your money paths on WhatsApp.
How Mark360 helps you choose
Start with a Mark360 AI agent on one high-volume FAQ intent, wire AGENT handoff, connect Shopify or CRM fields you already trust, and measure deflection vs conversion for two weeks. If MBA eligibility and BSP standby support look strong later, you can evaluate Meta’s agent with eyes open — not as a surprise inbox outage.
Mark360 WhatsApp API · WhatsApp AI agent complete guide · soft CTA: talk to Mark360 about agent + campaign setup on mark360.ai.
Related reading
Service messages Oct 2026 cost hedges · Cloud API vs BSP · Ecommerce use cases.
