What Meta Business Agent costs you on the WhatsApp Business app
Meta has published specific consequences for WhatsApp Business app users who enable the Meta Business Agent. According to their Help Center, customer conversations are collected to improve Meta's AI systems, and this collection continues even when businesses mute the agent:
"Messages sent or received in chats that have connected Meta Business Agent will still be collected by Meta to improve AI at Meta, even when you mute Meta Business Agent."
Deletion is the only documented control that stops data collection. Muting merely pauses agent responses without halting the data-gathering process.
Meta also documents operational feature losses for app-path users:
- Broadcast lists, disappearing messages, greeting and away messages become unavailable
- The inability to pause or delete the agent using WhatsApp Web
What the Cloud API documentation says instead
For businesses using Meta's Cloud API—the path most Indian companies take through Solution Partners—the documentation differs significantly. Cloud API developer documentation meticulously describes mechanics: standby webhooks, handoff procedures, thread control endpoints, and control-release mechanisms.
However, across nine developer documents reviewed, there are zero mentions of data collection practices, feature restrictions, or messaging capability changes equivalent to those published for app users.
The nine documents, and what is not in them
A systematic search across Meta's developer documentation for the agent yielded striking gaps:
| Term Category | Search Terms | Results Found |
|---|---|---|
| Feature loss | disable, unavailable, cannot use, lose access (22 terms) | 0 |
| Data use | improve AI, train, retention, privacy, consent (17 terms) | 0 |
| Messaging capability | messaging limit, throughput, rate limit (11 terms) | 0 |
What this does not prove
This documentation gap does not necessarily indicate Meta is concealing unfavorable terms. Cloud API deployments have fundamentally different architectures than phone-based WhatsApp Business apps. Broadcast lists and linked devices are app-specific concepts that don't exist in Cloud API environments, so feature losses wouldn't apply.
The core problem is simpler: Solution Partners cannot answer clients' basic questions about costs because Meta hasn't published the answers in either direction.
Where Meta Business Agent is available
The WhatsApp Help Center clearly states: "This feature is currently only available in limited countries to select businesses. It might not be available to you yet."
The developer documentation merely requires businesses be "based in a country authorized for Meta Business Agent" without naming any specific countries. No published country list exists, and India is neither explicitly included nor excluded in any official documentation.
One defect you can check yourself
The thread control endpoint appears at three different URLs across Meta's documentation:
- Get Started guide:
https://graph.facebook.com/v21.0/<PHONE_NUMBER_ID>/thread_control - Thread Control reference:
https://api.facebook.com/business/whatsapp/phone_numbers/{phone_number_id}/thread_control - Changelog:
POST /business/whatsapp/phone_numbers/{phone_number_id}/thread_control
The reference and changelog align; the walkthrough diverges. Developers following the Get Started guide would call a different endpoint than the official reference specifies.
Actionable recommendations
- Verify deployment path first: Cloud API and WhatsApp Business app paths are documented entirely separately with different consequences
- Read the mute clause carefully: For Business app users, muting doesn't stop Meta's data collection
- Check eligibility individually: Use the eligibility endpoint rather than assuming global availability based on third-party claims
- Test both endpoints: If implementing thread control, verify both documented URLs in your testing environment
The asymmetry remains: one deployment path has published costs; the other has published mechanics only.
