WhatsApp Business Account locked (error 131031)
1

Hello,

My WhatsApp Business Account is locked with error 131031 "Business Account locked", restriction category RESTRICTED_BIZ_INITIATED_CONV_AND_ADD_PHONE_NUMBER, which is preventing me from sending new templates and adding new phone numbers.

Account identification:

WhatsApp Business Account (WABA) ID: 1788702312291804 Business name: Rankim Soluções em Software Business Manager ID: 1809218415979893 App ID: 1603925144688206 Affected phone numbers: 1210590465475893 and 1234898449710364

Diagnostics already performed, all showing normal status:

Invoice paid and payment method active Phone numbers show status "Connected" with "High" quality rating Message template already approved Access token regenerated — the error persists even with a new token API health_status shows AVAILABLE at every level (phone number, WABA, Business, App) None of Meta's own diagnostic tools indicate the reason for the lock — only the actual send call fails Webhook configured to receive account_update/account_review_update/account_alerts events — no event has been received so far

I've confirmed there is no visible policy violation, no detailed restriction notice, and no automated notification explaining the reason for this lock. Could you please perform a manual review of the account to identify and remove this restriction, since every available automated indicator shows the account as healthy?

I'm happy to provide any additional information needed.

Thank you.

Renato
Asked about a month ago
Renato

Phone numbers are showing status "Connected" with "High" quality rating Invoice is paid and payment method is active — no billing issue WhatsApp Business Account and phone numbers pass Meta's own health_status check (AVAILABLE) at every level (number, WABA, Business, App) No policy violation notice has ever been received on this account Message template is already approved

Everything above was double-checked before opening this thread, so this really does look like it needs a manual review rather than a self-service fix on our end. Appreciate any help getting this in front of someone at Meta who can look into it.

September 7 at 5:12 PM