WhatsApp Business Platform policy and spam enforcement | Developer Documentation

Respond to a WhatsApp account restriction with ChatArchitect

If sending stops or Meta displays a policy notice for the WhatsApp account connected to ChatArchitect, first identify the affected account and the stated restriction. Stop the affected campaign launches while you establish the cause. A sending failure alone does not prove that the whole account is blocked.

Separate the possible causes

Find the account notice

1. Sign in to Meta Business Suite with access to the portfolio used for the ChatArchitect connection. Identify the account and number using the WhatsApp account guide.
2. Open Business Support Home and select the relevant WhatsApp account. Meta's enforcement reference documents this route. Check the current notice and its available actions rather than relying on an old restriction schedule.
3. Record the policy named, affected account or number, restricted activities, start or end time if shown, and whether review is available. If you cannot access the asset, use the business access guide.
4. If the scope is unclear, send ChatArchitect support the account and number, time with time zone, exact notice or error and any affected attempt references. Remove Secret values, access tokens and unrelated personal data from screenshots.

Meta can limit particular activities, lock an account or disable it. The actual notice determines the scope and next step. A better template quality rating or a higher messaging limit does not by itself reverse an account policy restriction.

Contain the affected sends and review the cause

Identify the CRM, help desk and scheduled workflows using the affected account. Pause future launches that depend on restricted activities. Confirm what the tool's pause action does to already queued requests before assuming those requests were cancelled; retain their references and known outcomes.

Use the policy notice checklist to connect the notice with the relevant content, audience or business activity. Review the audience permission records, withdrawals and actual message versions. Do not create a new number or account as a substitute for resolving the restriction.

Request review only when available

If the notice offers Request Review and you believe the decision is incorrect, prepare the facts and supporting material for that specific violation. Submit through the account's available Meta review action. Some spam restrictions are not appealable; if the action is absent, check the notice and ask support about the appropriate next step.

Record the submission reference and follow its result in Meta's support interface. A submitted review is not a reversal. ChatArchitect support cannot promise that Meta will remove a restriction or decide by a fixed deadline.

Resume only after checking the current state

Before a permitted new test, confirm that the affected activity is available again and the underlying issue has been addressed. Recheck the intended template and audience, then inspect the new attempt's outcome. Reconcile pending attempts from before the restriction before restarting a larger campaign. Keep the notice, actions and result in the team's incident record.