The business_capability_update field reports capability limits on a WABA or business portfolio. It is mainly about messaging capacity and phone-number capacity.
What business_capability_update Reports
This field can report:
- messaging limits for the business portfolio,
- maximum phone numbers allowed per business portfolio,
- maximum phone numbers allowed per WABA,
- capability increases or decreases after Meta review or usage changes.
When It Fires
Meta sends it when a WABA is created or when business capabilities change. Capability changes can be increases or decreases, so treat this as a state update rather than only as a success signal.
Payload Shape
{
"object": "whatsapp_business_account",
"entry": [
{
"id": "<WABA_ID>",
"time": 1739321024,
"changes": [
{
"field": "business_capability_update",
"value": {
"max_daily_conversation_per_phone": 2000,
"max_daily_conversations_per_business": "TIER_2K",
"max_phone_numbers_per_waba": 25
}
}
]
}
]
}Common fields:
| Field | Notes |
|---|---|
max_daily_conversations_per_business | Current business portfolio messaging limit, delivered as a tier string: TIER_250, TIER_2K, TIER_10K, TIER_100K, or TIER_UNLIMITED. Meta's reference types it as an integer and its example shows 2000, but deliveries use the tier strings. |
max_daily_conversation_per_phone | Deprecated. Meta announced its removal for February 2026, but deliveries still include it as of late October 2026, as an integer (250, 2000, 10000, 100000, or -1 for unlimited). Read max_daily_conversations_per_business and treat this one as optional. |
max_phone_numbers_per_business | Business portfolio phone-number cap. Meta includes it only when the messaging limit is 250. |
max_phone_numbers_per_waba | Phone-number cap per WABA. Meta includes it only when the messaging limit is above 250. |
Dualhook Handling
Dualhook subscription: subscribed and forwarded. Dualhook's Meta app subscribes to business_capability_update, so it arrives on Dualhook's app-level callback and Dualhook forwards it to your endpoint.
Dualhook records each event in the connection's webhook log and compares it with the previous one. When the messaging limit drops, Dualhook emails the organization's admins. The dashboard does not show the phone-number caps; check those in WhatsApp Manager.
The field contains account metadata, not user messages. Dualhook stores the relevant operational metadata and forwarding status only.
Implementation Notes
- Treat missing fields as "unchanged or not included", not as zero.
- Normalize numeric and tier-style messaging-limit values into your internal format.
- Alert operators when a capability decreases, because sends, number onboarding, or customer growth may be affected.
- Pair this field with
phone_number_quality_updateandaccount_alertsfor capacity monitoring.