The account_alerts field reports account and phone-number alerts that Meta wants the business or partner to act on. It is a management webhook field, not a message-path field.
What account_alerts Reports
Use account_alerts to detect changes such as:
- messaging-limit increase decisions that were denied, deferred, or need more information,
- Official Business Account (OBA) approval or rejection,
- deleted business profile photos,
- profile or capability alerts that may require a business action.
The important nested object is alert_info. It carries the severity, status, type, and human-readable description.
When It Fires
Common trigger families are:
| Trigger | Typical meaning |
|---|---|
| Increased-capability eligibility | Meta cannot increase limits yet, deferred the decision, or needs more verification. |
| OBA status | The phone number's Official Business Account request was approved or rejected. |
| Profile photo lost | The phone number's public business profile photo was deleted and should be uploaded again. |
Payload Shape
{
"object": "whatsapp_business_account",
"entry": [
{
"id": "<WABA_ID>",
"time": 1739321024,
"changes": [
{
"field": "account_alerts",
"value": {
"entity_type": "BUSINESS",
"entity_id": "<BUSINESS_OR_PHONE_ID>",
"alert_info": {
"alert_severity": "WARNING",
"alert_status": "ACTIVE",
"alert_type": "INCREASED_CAPABILITIES_ELIGIBILITY_DEFERRED",
"alert_description": "Limits cannot be increased yet."
}
}
}
]
}
]
}Key values:
| Field | Notes |
|---|---|
entity_type | Usually BUSINESS, PHONE_NUMBER, or a status/profile entity. |
entity_id | Business portfolio ID, phone number ID, or profile/status entity ID. |
alert_severity | CRITICAL, WARNING, or INFORMATIONAL. |
alert_status | Usually ACTIVE or NONE. |
alert_type | Machine-readable reason, such as OBA_APPROVED, OBA_REJECTED, or an increased-capability eligibility result. |
alert_description | Human-readable action or explanation from Meta. |
Dualhook Handling
Dualhook subscribes to account_alerts as a management field. These events land on Dualhook's app-level callback, not on your Webhook Override URL.
Dualhook uses the event metadata to surface account-health and capability alerts in the dashboard, classify alert severity, and forward the management event to your configured endpoint with Dualhook forwarding headers. Dualhook stores operational metadata about the alert and delivery status; it does not store message content because this field is not a message webhook.
Implementation Notes
- Treat
alert_typeas the stable routing key andalert_descriptionas display text. - Escalate
CRITICALalerts to an operator; they often indicate a rejection or blocked capability. - Keep the raw
entity_typeandentity_id, because an alert may target a business portfolio, phone number, or profile entity. - For OBA decisions, also check Official Business Account and Display Names.