Your WhatsApp Number Has a Quality Rating. Here's How Not to Lose It.
Green, yellow, red. The colour decides how many messages you can send tomorrow. Here's what affects it, and how to fix it before it costs you a customer.
Most teams discover their WhatsApp quality rating exists about 10 minutes after it drops to yellow. By then they’re already losing reach, and they don’t know why.
This post is the version of “how WhatsApp quality rating actually works” we wish someone had handed us. No jargon, just the rules and the levers.
What it is
Meta assigns every WhatsApp Business number a quality rating: Green, Yellow, or Red. It’s not a vibe — it’s a real number that decides:
- How many messages you can send per day (your tier — 1k → 10k → 100k → unlimited)
- Whether your templates get rejected
- Whether your number gets banned
| Rating | What it means | What happens |
|---|---|---|
| 🟢 Green | Healthy | Send freely, you can apply to upgrade tier |
| 🟡 Yellow | Warning | Sending continues but expect throttling. Stop and audit. |
| 🔴 Red | Penalty | Daily messaging cap drops sharply. Templates may be rejected. Recovery takes weeks. |
A number that drops to red is sometimes never recovered. Treat yellow like a fire alarm.
What actually moves the rating
There are exactly four things that affect quality:
1. Block rate
When customers tap “Block” on your number, your rating tanks. This is the single biggest signal.
The fix: Only message people who explicitly opted in. Imported lists are the #1 cause of block-rate spikes.
2. Report rate
When customers tap “Report” — usually after a “report spam” pop-up that WhatsApp itself surfaces. This is worse than blocking, because Meta sees it as a stronger signal.
The fix: If you’re sending marketing, make sure the message looks like marketing they signed up for. Don’t try to disguise marketing as a service notification.
3. Reply rate (in reverse)
Counter-intuitively, low reply rates can hurt you. Meta interprets a stream of one-way broadcasts as low-engagement spam.
The fix: End broadcasts with a reason to reply. “Reply YES to confirm.” “Tap if you want more.” “Let us know what colour fits best.”
4. Template usage
Sending utility templates as marketing (or vice versa) is a fast way to get flagged. Meta categorises every template at submission, and using them for the wrong purpose triggers automated review.
The fix: Submit templates honestly. If it’s a discount code, it’s marketing. If it’s an order update, it’s utility. Never one masquerading as the other.
The early-warning signs
Before your rating officially drops, you’ll see one or more of these:
- Delivery rate falling — messages get queued or rejected upstream
- Templates getting rejected that used to be approved
- One specific template suddenly throttled — Meta’s tagging it as low-quality
- Block rate spike in your dashboard — you see this before Meta does
When any of these show up, stop sending and audit. The cheapest fix is the one you make before yellow.
What to do at yellow
If you’re already yellow:
1. Stop the bleed today. Pause your highest-volume broadcast. The one with the most blocks is probably the one with the lowest engagement.
2. Audit your contact list. Pull every phone number added in the last 30 days. Who actually opted in? Who came from an imported file? Suspect the imports.
3. Slow down and resegment. Send to your top 20% most engaged customers only. Skip the rest entirely for 7–14 days.
4. Fix the templates. Re-read your active templates from the perspective of someone who didn’t ask for them. Ruthless.
5. Wait. Quality recovers in 7–14 days of clean sending. There’s no shortcut.
What to do at red
If you’re red, it’s serious. The recovery path:
1. Pause everything except utility messages (order confirmations, delivery updates) for at least 7 days.
2. Open a support case with Meta. Be specific about what changed and what you’re doing to fix it.
3. Don’t migrate. Some teams panic and try to switch numbers. This usually makes it worse — Meta tracks the business behind the number, not just the number.
4. Be patient. A number recovers from red in roughly 2–6 weeks of clean sending. Your daily message cap will be reduced during that time — plan accordingly.
The structural defences
Some things you can build in once and never worry about again:
- Auto-pause on failure spike. If your platform sees an unusual error rate, it should stop the broadcast automatically. Lose 100 sends; save your number.
- Throttling by default. Don’t send 10,000 messages in 5 minutes. Spread them over an hour. The natural rhythm of replies that comes back gives Meta the engagement signal it wants.
- Per-segment limits. Tag your “engaged” segment and your “newer” segment. Send marketing only to engaged. Newer contacts only get utility (welcome series, order updates) until they’ve shown they want more.
- Real opt-out. Every marketing message should have a one-tap “Stop” button. The customers who tap it would have blocked you anyway — losing them quietly is much better than losing them with a quality hit.
The honest line
A WhatsApp number is a long-lived asset. Treat it like one. The teams who are still on green a year from now didn’t get there by sending more — they got there by being more selective about who they send to.
Whatever platform you use, make sure it has auto-pause and per-segment controls built in. If yours doesn’t, switch before the next campaign.
For the broader broadcast playbook, see 10 Things That Decide Whether Your WhatsApp Broadcast Works.
Need a platform that protects your quality rating by default? See pricing and start free for a month.