WhatsApp is far less forgiving of careless bulk messaging than SMS ever was. Meta actively tracks how customers respond to your messages — blocks, reports, and even simple non-engagement all feed into a quality rating that determines how many people you're allowed to message next. Get this wrong and your business number can be throttled or banned outright. Here's how to run bulk campaigns properly.
Every WhatsApp Business number has a quality rating (High, Medium, or Low) that Meta calculates from real user signals: how many recipients block your number, report you as spam, or simply never engage. This rating directly determines your messaging limit — the number of unique customers you're allowed to message per rolling 24-hour period. A low rating shrinks that limit; a badly damaged rating can get the number restricted entirely.
This is fundamentally different from SMS, where deliverability is mostly a technical/carrier problem. On WhatsApp, recipient behaviour is the deliverability problem.
This exact pattern is common enough across African markets that it's worth naming directly: a contact list without real consent is not a WhatsApp marketing asset — it's a liability that actively damages your sending number.
Customers, signups, or people who've explicitly opted in. Not purchased lists, not scraped numbers, not "similar audience" guesses.
Order updates, reminders, and OTPs belong in utility templates, not marketing — using marketing templates for transactional content both costs more (see our pricing guide) and invites unnecessary opt-out friction.
A frustrated customer who can't easily stop your messages is far more likely to hit "Report" than "Unsubscribe" — and a report hurts your quality rating far more than an unsubscribe.
If a number has never opened a message, or consistently fails to deliver, sending to it again doesn't recover the relationship — it just adds another risk signal against your quality rating. This is exactly the logic behind suppression lists: track delivery failures (Meta's error code 131026, "Message Undeliverable," is the key signal to watch for) and stop retrying numbers that are demonstrably not reachable on WhatsApp, rather than hitting them again on the next campaign.
A brand-new WhatsApp Business number sending a huge first-day blast looks statistically identical to spam, even with a genuinely opted-in list. Ramp volume up over days or weeks rather than starting at full scale.
Don't wait for messaging limits to visibly shrink before paying attention — quality rating is visible in Meta Business Manager and should be checked regularly, especially before and after any bulk send.
Ghana, Nigeria, and other African markets have seen a wave of businesses — legitimate and otherwise — adopting WhatsApp as a marketing channel quickly, and Meta's spam controls have tightened in response across the board. A business sending genuinely wanted messages can still get caught in stricter default limits simply because bad actors in the same market damaged trust for everyone. Clean sending practices matter more here, not less.
The technical version of "don't keep messaging numbers that fail" is a suppression list: when a send comes back as undeliverable, record it and skip that number on future sends automatically, rather than relying on someone manually reviewing failure logs. This protects your quality rating without requiring constant manual oversight, and it's a pattern worth building into any bulk-sending system from day one rather than retrofitting after a quality-rating drop.
It's a High/Medium/Low score Meta assigns based on recipient blocks, reports, and engagement, visible in your Meta Business Manager account under your phone number's settings.
Sometimes, through Meta's appeal process, but recovery isn't guaranteed and can take significant time — prevention through clean sending practices is far more reliable than hoping for a successful appeal.
There's no specific law banning bulk WhatsApp messaging, but general data protection and consumer protection rules around consent still apply, and Meta's own platform rules (which carry real enforcement, unlike most local marketing regulation) are the more immediate constraint.
There's no official pre-send lookup API — Meta removed that capability from the Cloud API specifically to prevent list-scanning abuse. The reliable approach is tracking real delivery failures and suppressing numbers that have already failed, rather than trying to check in advance.
Both hurt your quality rating, but reports are treated as a stronger negative signal than blocks — this is why making opt-out easy (reducing the chance of a frustrated report) matters more than it might seem.
This guide was last updated September 2026.
