A suspended WhatsApp Business Account is one of the few failure modes that can take a messaging programme to zero overnight — and unlike a rejected template, it is slow and painful to reverse. The good news: WABA bans in India are almost never random. They trace to three causes, every one of which is preventable. Here is how Meta's quality system actually decides, and the playbook to stay green.
How Meta's quality system works
Every WABA phone number carries two signals that move together:
- Quality rating — Green (high), Yellow (medium), Red (low). It is computed from recent user feedback: blocks, "report" taps, and how many of your sends are read vs ignored over a rolling window.
- Messaging limit tier — the number of unique users you can message in 24 hours: 250 → 1K → 10K → 100K → unlimited. You climb tiers by sending quality traffic; you get knocked down (or frozen) when quality drops.
A ban is the end state of a quality spiral: Red rating → rate-limited → flagged → restricted → disabled. The system is reactive, so the damage is usually done before you see the Red badge. Prevention beats remediation by a wide margin.
Cause 1 — marketing-categorised bulk sends
The single most common trigger. Teams push transactional-natured messages (order updates, payment alerts, reminders) through the MARKETING template category — either by mistake or because the copy reads promotional — then blast them at volume. Marketing templates require opt-in, are quality-scored aggressively, and generate the block/report feedback that tanks your rating fastest.
The fix is categorisation discipline: route every message that genuinely is utility (the user expects it, it's tied to an action they took) through the UTILITY category, and write the copy so Meta agrees. If you find your rating dropping on "transactional" sends, check the actual category on Meta — it is probably marketing. See our template categorisation playbook for the rewrite rules.
Cause 2 — low-quality template copy
Even within the right category, copy quality drives the block rate. The patterns that generate complaints:
- Messages the user didn't expect. If a recipient can't immediately tell why you're messaging them, they block. Lead with the context ("Your Acme order #1234 has shipped"), not a greeting.
- Too-frequent sends. Three notifications about the same order in an hour reads as spam regardless of category.
- Stale or scraped lists. Messaging numbers that never opted in or haven't engaged in months produces a spike of blocks that the quality model reads as a spam signal.
Rule of thumb: every template should map to a real event the user would expect a notification for. If you can't name that event, don't send it.
Cause 3 — naive flat-rate blasting
New or recently-warmed numbers that suddenly send tens of thousands of messages in a flat burst look exactly like a compromised account to Meta's systems. The pattern, not just the volume, is the flag.
The fix is rate shaping: ramp volume gradually so it tracks your tier, spread sends across the day rather than one spike, and let early engagement (reads, replies) earn the next volume step before you take it. This is the same logic as email IP warming, applied to WhatsApp.
The stay-green checklist
- Categorise honestly. Utility content in the utility lane; only true promotions in marketing, with opt-in.
- Review copy before submission. Lead with context, cut promotional language, one clear purpose per template.
- Warm new numbers. Ramp volume over days, not in one burst; let the tier climb earn the next step.
- Clean your lists. Only message users who opted in or transacted; drop long-dormant numbers.
- Watch the rating daily. A drop from Green to Yellow is your early warning — pause and diagnose before it hits Red.
- Cap frequency. De-duplicate and rate-limit per user so nobody gets three messages about one event.
If you're already restricted
If your number is rate-limited or flagged: stop all non-essential sends immediately, let the rating recover over the rolling window (days, not hours), and open a Meta Business support case if you believe the action was wrong. Do not spin up a fresh number and blast the same content — Meta links numbers under a business and the pattern follows you.
How QuickAuth keeps accounts green
Avoiding bans is mostly process, and process is easy to skip under launch pressure. QuickAuth's onboarding bakes the three protections in by default: template categorisation (so utility content doesn't get classed as marketing), copy review (so templates aren't borderline), and adaptive rate shaping (so volume ramps in a way Meta's quality systems are happy with) — a setup designed to keep your number and templates out of trouble. The full list of what's included is on the WhatsApp marketing and WhatsApp utility pages.
A ban is preventable. Categorise honestly, write for the user, ramp gradually — and watch the rating like you'd watch error rates on any other production system.