On this page
A quality rating drop is not something you need to configure or click a button to respond to; VGraple CRM has already reacted automatically before you even see the alert. This article walks through exactly what happened automatically and the specific, ordered steps that actually move the rating back up, without repeating the full background on what quality rating means (see understanding your phone number quality rating for that).
Symptom
The WhatsApp channel card in Settings, then Channels, then WhatsApp shows a quality badge change from High quality (GREEN) to either Medium quality (YELLOW) or Low quality (RED). An in-app alert, a mobile push notification, and, where configured, an email reach the organisation owner naming the drop. If the drop was to RED, one or more running broadcasts show a paused status with the reason naming the quality collapse. Sends from the number, if RED, or the campaigns that are still running, if YELLOW, are noticeably slower than usual.
Why it happens
Meta calculates quality from real-time recipient signals, blocks, spam reports, low engagement relative to volume, over a rolling 7-day window weighted toward the most recent activity, so a bad day is much more influential than an equally bad day three weeks ago. A drop almost always traces back to one of two patterns: a single broadcast sent to a cold, purchased, or overly broad audience that generated a spike of blocks and reports in a short window, or a gradual decline from sustained low engagement across several sends, template content that reads as vague, repetitive, or mismatched with what recipients expected.
Fix
- Stop planning any further sends to broad or cold segments until the rating recovers. This is the single highest-leverage action; continuing to send at the same audience and pace is what turns a YELLOW into a RED, or extends a RED's recovery time.
- Identify what was sending when the drop happened, if anything. Open the broadcast history around the time the alert fired; a specific campaign to a specific audience is the most common and most fixable cause.
- For your next sends, restrict the audience to recently engaged, opted-in contacts only. People who have replied, clicked, or interacted with your business in the last few weeks are far less likely to block or report than a cold or long-dormant list.
- Review the content of whatever template was sending at the time of the drop. Vague copy, unclear sender identity, or a mismatch between what the message promises and what the business does all earn disproportionate reports.
- Let the 7-day window roll forward with cleaner sends. There is no faster path; a sustained run of low-report, low-block sending genuinely and reliably moves the rating back toward GREEN over the following days.
- Resist the instinct to send a large "make up for it" campaign once the rating starts to recover. A big send right as the rating is climbing back risks the exact spike in reports that caused the original drop, resetting the recovery.
How VGraple CRM handles it automatically
The pacer for the affected number adjusts its sending rate the instant the drop is detected: 25 messages a second on YELLOW, half the default 50/s rate, and 5 messages a second on RED, a tenth of default, without any configuration needed. On a drop to RED specifically, every broadcast currently sending from that number is paused outright, not just slowed, because continued sending at any rate risks making an already-bad rating worse, and the pause reason is written in plain language directly on the affected campaign. The organisation owner is alerted across in-app, mobile push, and email the moment the drop is detected, so the business hears about it from VGraple CRM rather than from a customer complaint or a wall of failed sends discovered later. None of this requires any setting to be turned on; it runs identically on every plan, including Free.
Example
A salon's Friday promotional broadcast to 3,000 contacts, including a chunk of numbers that had not engaged in over a year, drives a spike of blocks that drops the number's rating to YELLOW within the hour. The pacer halves the sending rate on the still-running campaign automatically, and the owner gets a push alert naming the drop. The salon lets the campaign finish at the slower rate, sends nothing further to the full list for several days, and instead sends a small, well-targeted booking reminder only to recently active customers; the rating recovers to GREEN within the following week.
Prevention
The most durable prevention is treating audience quality as seriously as message content: build broadcast audiences from segments of genuinely engaged contacts rather than defaulting to "everyone," and be especially cautious with any list gathered from a source that never confirmed the number was live and interested (a purchased list, an old export, a form with no verification step). Space marketing sends to the same list by more than a day where possible, and review template copy for specificity and honesty before every send, not just at initial approval, since a template that performed well on one audience can still earn poor reactions when sent to a colder or less relevant one later.
What is the difference between this and a broadcast simply being slow?
A broadcast can also send more slowly than expected for reasons entirely unrelated to quality rating, most commonly the daily portfolio messaging budget running low, or Meta's own throughput ceiling being reached temporarily (error 130429). The distinguishing signal is the channel card's quality badge itself: if it shows YELLOW or RED, the slowdown or pause is quality-driven and the recovery guidance above applies directly. If the badge still shows GREEN, a slow or paused campaign has a different cause, and broadcast paused: every reason and what to do covers the full list of what else can be responsible.