WhatsApp Error 131031: Account Locked Explained | ChatShree
Skip to content
Troubleshooting

WhatsApp error 131031: account locked or restricted

Quick answer

Error 131031 means Meta has restricted or locked your WhatsApp Business Account, usually for a Business Messaging Policy violation. All sends stop immediately. Fix by identifying the violation (check Business Manager's account status page), submitting an appeal with evidence of the fix, and — if it happens repeatedly — auditing your entire opt-in, template and content pipeline for policy compliance.

Disclaimer: Account restriction reasons and appeal processes evolve. Always confirm the current process in Meta Business Manager and the Business Help Center.

What error 131031 means

Meta returned 131031 because your WhatsApp Business Account (WABA) or a phone number under it is locked or restricted. All outbound messaging is suspended. No templates, no session messages, nothing goes through until the restriction is lifted or a specific phone number is re-enabled.

This is not a technical error — it is an enforcement action. Meta's Trust & Safety systems (or a human reviewer) decided your account crossed a policy line.

The most common triggers

  1. Opt-in violations. High rates of user blocks and reports, sending to purchased or scraped lists, or sending marketing without recorded consent.
  2. Content policy violations. Messages that promote prohibited content (regulated goods, gambling in restricted markets, illegal financial services, etc.).
  3. Template quality collapse. Multiple templates paused or disabled in a short window signals systemic problems and can trigger account-level enforcement.
  4. Payment method failure. Failed billing beyond Meta's grace period locks the account until payment succeeds.
  5. Business verification issues. Business Manager verification revoked, documents rejected, or business ownership disputed.
  6. Impersonation reports. Users reporting the business as fake, impersonating a brand, or misusing a well-known name.

How 131031 differs from cousin errors

CodeScopeCause typeRecovery path
131031Account or numberPolicy or billingAppeal in Business Manager
368NumberTemporary blockWait out block, fix root cause
133010NumberRegistration lapsedRe-register with PIN
131049Per-userFrequency capReduce send frequency

The first 30 minutes after a 131031

  1. Stop all outbound. Continuing to hammer the API generates more errors and worsens the incident timeline.
  2. Open Business Manager → Account quality. Read the restriction message exactly. Don't paraphrase — the wording tells you which policy clause you tripped.
  3. Check the account admin email. Meta usually sends a detailed notice within an hour of the restriction.
  4. Document the state. Screenshot the account quality page, save the notice email, timestamp everything. Appeals require timelines.
  5. Freeze template edits. Editing templates during an appeal window can confuse reviewers.

Writing an effective appeal

Meta reviewers see thousands of appeals. Generic "please unblock our account" text gets templated denials. A strong appeal:

  • Names the specific policy clause you're accused of violating.
  • Describes the concrete change you've made (updated opt-in flow, revised template copy, removed a specific list segment).
  • Includes screenshots or links proving the change is live.
  • Acknowledges the concern honestly. Denying obvious violations wastes the reviewer's time and makes reinstatement harder.
  • Runs 3-5 short paragraphs. Not one line, not five pages.

How to prevent a repeat 131031

Fix the opt-in first

Every marketing list should have a documented opt-in source per contact. If a customer complains, you should be able to show Meta exactly where and when they consented. If you can't, the contact should not be on the list.

Watch quality rating daily

Quality rating on a phone number drops from Green to Yellow to Red before Meta escalates to account-level enforcement. See our quality rating deep dive — a Red rating that stays Red for weeks often precedes 131031.

Rate-limit yourself below Meta's tier

Sending at 90% of your daily tier signals aggressive campaigning. Stay under 70% and use engagement-based prioritisation. Bursts near tier limits generate more complaints proportionally.

Clean your content quarterly

Once a quarter, audit your active templates for anything that could be flagged: unclear sender identity, misleading urgency, promotions that resemble scams, financial claims without disclaimers. Retire ambiguous templates before Meta does.

Separate workloads across multiple numbers

Run marketing on one phone number and transactional (utility) on another under the same WABA. If marketing gets restricted, transactional keeps flowing. This is standard practice at any high-volume Indian D2C business.

Keep billing current

Add a backup payment method and monitor Meta invoices. Billing-triggered 131031s are entirely preventable and embarrassing.

What not to do

  • Don't create a new WABA to "escape" a restriction. Meta detects related businesses and applies the same restriction to the new account. Repeat evasion attempts can result in permanent bans across all Meta properties.
  • Don't message users apologising for downtime via SMS with links to a new WhatsApp number — Meta treats this as evasion.
  • Don't panic-delete templates. Delete only after your appeal is resolved, based on reviewer feedback.
  • Don't hire "unblocking specialists" who promise guaranteed reinstatement. Only Meta reinstates accounts.

A recovery checklist

  1. All outbound stopped.
  2. Restriction reason captured from Business Manager and email.
  3. Root cause identified (opt-in, content, billing, verification, quality).
  4. Concrete fix implemented and documented with screenshots.
  5. Appeal submitted with the exact policy clause and evidence.
  6. Monitoring in place to detect the same pattern recurring.
  7. Post-mortem shared with the team and BSP.

How ChatShree helps you avoid 131031

ChatShree records opt-in source and timestamp per contact, tracks per-number quality rating and alerts before it turns Yellow, and separates marketing and transactional traffic across numbers by default. Our onboarding team also reviews your first three campaigns for policy risk before they run — most 131031s hit new senders who never had that review. See our team page for how our support model works.

Closing thoughts

Error 131031 is the loudest signal Meta will send you short of a permanent ban. Treat it as one. Fix the root cause, document the fix in the appeal, and use the incident to harden your opt-in, content and monitoring pipeline. Businesses that treat 131031 as a wake-up call typically never see it again. Businesses that appeal without changing behaviour see it repeatedly, each time with fewer chances at reinstatement.

Frequently asked questions

What does WhatsApp error 131031 actually mean?

Meta returned 131031 saying the account is locked, restricted or otherwise not permitted to send. The most common causes are Business Messaging Policy violations, payment method failures, and Business Manager verification lapses.

How do I know why my account was restricted?

Go to Meta Business Manager → Business settings → Account quality → your WABA. The restriction reason and appeal button appear there. Meta usually sends an email to Business Manager admins within 24 hours of the restriction.

Can I appeal a 131031 restriction?

Yes. Every restriction has an appeal button in Business Manager. Meta reviews within 1-5 business days. Include specific evidence of remediation — screenshots of updated opt-in flows, revised templates, updated policies — to strengthen the appeal.

Will my message templates be lost if my account is restricted?

No. Templates remain in your account. When the restriction lifts, your templates are still there. If templates were the cause, expect them to be paused or removed as part of the enforcement action.

Can I send from a different phone number while restricted?

If the restriction is on the entire WABA, no — every number under that WABA is blocked. If the restriction is on a single phone number, other numbers in the same WABA may still work but you're on notice.

How long does a 131031 restriction last?

It depends on severity. First-time policy warnings often lift within 24-48 hours of appeal. Repeat violations can be permanent. Payment-related restrictions clear as soon as billing is fixed. There is no fixed duration.

Sources