The account_review_update webhook
account_review_update carries the outcome of a Meta review of the business account. Its decision field says what was decided, and a rejection is worth treating as a degraded connection rather than as information, because sending usually follows it downward.
- Carries a review decision
- A rejection precedes restriction
- Nothing appears on the phone
Nothing charged for 7 days. Cancel anytime.
Field that reports the outcome: decision.
The error a restricted account returns once enforcement follows.
The related error when the restriction involves verification details.
When does a review happen?
When Meta examines the business account, which can follow a verification submission, an appeal, or an automated flag raised by messaging behaviour.
The review itself is not something a provider triggers or sees the inside of. What arrives is the outcome, as an event with a decision. Approvals are unremarkable. Rejections are the ones worth acting on, because they often precede a restriction rather than closing a matter.
Nothing about a review is visible in the WhatsApp Business app, so a business can be under review, be rejected, and continue answering customers from the phone with no indication anything happened.
Why treat a rejection as degraded rather than as news?
Because it is usually the first of several events rather than the last.
A rejected review means Meta looked at the account and was not satisfied. What follows is frequently a restriction, which stops sending entirely and arrives as an account_update with an enforcement event. Marking the connection degraded at the rejection gives whoever is watching a head start on the conversation with the client.
The alternative, recording it as informational, means the first anyone acts is when sends start failing, at which point the business is already unable to reach customers and the discussion begins from a crisis rather than from a warning.
Common mistakes
- Recording a rejection without changing state. It is a leading indicator, not a footnote.
- Expecting the reason in this event. It carries the decision; the detail lives in Business Manager.
- Assuming the business will notice. Nothing about a review appears on the phone.
EasyCoexistence marks a connection degraded on a rejected review and records it on the timeline, so the warning arrives before the restriction does.
Frequently asked questions
Can a provider see why the review failed?
No. The enforcement notice and its reasoning live in Business Manager on the business account.
Does a rejection always lead to restriction?
Not always, but often enough that treating it as a warning is the right default.
Who can appeal?
The people with admin access to the business account. No provider can appeal on their behalf.
Is this the same as template review?
No. Template review outcomes arrive separately and concern one template rather than the account.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on