WhatsApp quality rating: the indicator that warns you before your number drops

WhatsApp's quality rating is the quality score Meta assigns to every number connected to the official API, in three colors: green, yellow, and red. It's calculated on how recipients reacted to your messages over the last 7 days, shows up in WhatsApp Manager, and can be read via the API. In practice, it's an early-warning alarm: when the color changes, you still have days to act before your sending limit drops.

What does quality rating measure — and what doesn't it measure?

Meta doesn't read the content of your conversations: encryption prevents that. What it measures is how recipients reacted:

• how many people blocked your number after receiving a message;
• how many reported it;
• what reason the person selected when reporting ("I didn't ask to receive this," "offensive content," and so on).

The calculation looks at the last 7 days — a window stated in Meta's documentation, in effect as of August 2026 —, weighting the most recent days more heavily.

What it doesn't measure: volume, sending speed, or company size. Sending 50,000 messages doesn't tank the score — sending 500 to people who never asked does.

The score is per number, not per company

Two practical consequences change who you should blame when the color changes:

1. The score is per phone number, not per account (WABA) or per company. Two numbers on the same account can be different colors on the same day, because they do different things.
2. Templates have their own separate rating. A message template can get paused for quality with no change to the number's color — and vice versa.

In other words: the investigation starts narrow. One number, and inside it, one template — almost never the whole operation.

What does each quality rating color mean?

Here's where the most expensive confusion in corporate WhatsApp lives: yellow blocks nothing. No message stops going out — which is exactly why it slips by: the operation keeps running normally and nobody looks at the dashboard until the limit collapses.

The 7-day window and the flagged state

When the score drops to red, the number enters a flagged state. From there:

• you keep sending normally;
• Meta observes for 7 days;
• if quality climbs back up within that window, the number returns to normal and nothing happens;
• if it's still low at the end of the window, the sending limit gets reduced — you drop a tier.

The rolling window explains two things that look like a bug but aren't. The color takes time to improve: fix the campaign today and the score won't change tomorrow, because it needs clean days to dilute the bad ones. And the color takes time to worsen: Monday's unfortunate send might only show up on Wednesday — check the 7-day history before concluding "it wasn't that."

Where do you check your number's quality rating?

In WhatsApp Manager, go to Account settings → Phone numbers. The table lists each number with the three columns that matter together — status, quality, and messaging limit — and shows whether the number is flagged. Also check the message templates tab: each template has its own status (active, paused, rejected), and that's where you'll find the specific template dragging your reputation down.

Via the API, a call to your account's phone numbers endpoint does it:

GET /{WABA_ID}/phone_numbers?fields=display_phone_number,quality_rating,messaging_limit_tier

The quality_rating field returns GREEN, YELLOW, RED, or UNKNOWN — the last one for a new number, still with no history. Running this once a day into an internal dashboard turns the score into a time series: the format where it's actually useful for anything.

How do you get notified without having to check the dashboard?

By subscribing to a webhook. Two fields on your account:

• phone_number_quality_update — fires when the number gets flagged, when it returns to normal, and when the sending limit changes. Carries the event and the current limit.
• account_update — carries account state changes, including the waba_ban_state field, with values DISABLE, SCHEDULE_FOR_DISABLE, and REINSTATE.

That second field deserves an honest pause: it exists because a number on the official API can, in fact, be deactivated. Anyone selling the official API by claiming it "eliminates ban risk" is lying — what it gives you is something else, and better than it sounds. The quality rating and messaging tier glossary entry covers the conceptual side.

What tanks the quality rating?

In order of weight:

1. Sending to people who never gave opt-in. This is item number one, by a wide margin. The policy requires both things: the person gave you the number and authorized contact. A purchased base or a list scraped from a group falls here — the detail of what Meta treats as abuse is in what is spam on WhatsApp.
2. Frequency that's too high. The limit of marketing messages per person is adaptive — it varies by user and by business, and Meta doesn't publish a figure. When you exceed it, the API responds with error 131049 and the message isn't delivered. This isn't a punishment: it's the system holding back before it turns into a report.
3. A template that promises one thing and delivers another. A template approved as utility that arrives as an offer is the fastest recipe for a report — and for the template getting paused for quality (3 hours the first time, 6 hours the second, deactivated on the third; rule in effect as of August 2026).
4. An old base and lazy segmentation. A contact from two years ago doesn't remember you. Reactivating a cold base tanks the score more than a campaign to an active base — and sending everything to everyone just multiplies who gets something irrelevant.
5. No visible way out. Whoever can't find a way to leave reports you. A genuinely honored "reply STOP" trades a report for an opt-out — and opt-out doesn't count against the score.

It dropped to yellow: what to do in the first 48 hours?

1. Pause your marketing campaigns. Support and utility keep going — the problem is almost never in replying to customers.
2. Find the culprit. Cross-reference the last 7 days of sending against your templates tab. In most cases it's one template and one list, not the whole operation.
3. Clean the list. Remove anyone who never replied across three straight campaigns and anyone who joined with no loggable opt-in. Those people aren't going to buy, and they cost reputation.
4. Rewrite the template. The company identified in the first line, explicit context ("you requested a quote on 08/12"), and an opt-out at the end.
5. Reduce frequency and send in smaller batches, monitoring between them.
6. Wait. The score needs clean days; ramping volume back up the next day is the classic mistake. Track it via the API until it returns to green and only then scale.

If the number's already been restricted, the path is different — it's in the WhatsApp banned: what to do guide.

Is quality rating the same thing as the sending limit?

No. They're two different indicators that show up side by side on the same dashboard and constantly get confused:

The relationship between the two runs one way: a low score that lasts through the end of the observation window is what drops the limit. Quality rating is the toll on scale — which is why it weighs much more heavily on anyone doing bulk sending than on anyone who just handles support.

The sending limit tiers (messaging tiers)

The messaging limit counts unique contacts you initiate per day — not messages sent, and not conversations where the customer spoke first. The tiers in effect as of August 2026:

To move up a tier you need consistent volume and a score that isn't red. That's why an operation growing fast while managing its list poorly locks itself: volume goes up, the score drops, and the score locks the volume.

What does the official API give you that QR code doesn't?

Here honesty is the strongest argument: neither path is immune to a ban. CRPRO sells both, so we have no reason to sell a fantasy. The difference is visibility and due process:

That last row usually goes unnoticed. On the official API, sending a free-form message outside the 24-hour window isn't an infraction — it's impossible: the API refuses with an error, and only a template reopens the conversation. On QR code, nothing stops you from sending, and what comes next is the report. On modified apps like GB WhatsApp, you add a Terms violation on top of that.

Translated: on the official API, you're a business with a record. On the regular app, you're an anonymous number Meta can shut off on a Tuesday, with no explanation and no deadline.

Frequently Asked Questions

Does a yellow quality rating block my sends?

No. Yellow is a flag: every message keeps going out normally. That's exactly why it demands immediate action — it's the only warning that arrives with no pain attached.

How long does it take for the score to return to green?

There's no guaranteed timeline. Since the calculation window is rolling, at 7 days, and weights recent days more heavily, recovery usually takes anywhere from a few days to a week of clean sending. Ramping volume back up before that resets the problem.

My number shows as UNKNOWN. Is that a problem?

No. That's the normal state for a new number or one with low volume: there isn't enough recipient feedback yet for Meta to calculate a score. It shows up once the history builds.

Can a low quality rating get my number banned?

It can contribute. A persistently low score first drops the sending limit; deactivation comes through escalation, with a warning beforehand. The official API doesn't eliminate ban risk — the waba_ban_state field in the webhook exists precisely because deactivation is possible. What it guarantees is that you're warned first.

Does a paused template drag down the number's score?

They're separate ratings: a template can be paused with no change to the number's color. But the cause is usually the same — reports and blocks — so a paused template is a sign that a score drop is right behind it.

Can I monitor quality rating without logging into WhatsApp Manager?

You can, and it's recommended. Query quality_rating on your account's numbers endpoint, or subscribe to the phone_number_quality_update webhook, which notifies you when the number gets flagged and when the limit changes. Platforms connected to the official API usually expose this in their own dashboard.

Check the color before it checks you

If you operate through the official API and have never looked at this score, open WhatsApp Manager today and see what color your numbers are in. On CRPRO, official connections and QR code sit on the same dashboard, with multi-agent support and template campaigns — and we'd rather tell you which of the two makes sense for your case than sell you an immunity nobody has.