Quick answer: Meta runs a continuous quality gate on every WhatsApp Business number and on every marketing template a business sends. The phone number carries a live red / yellow / green rating computed from recent recipient feedback — blocks, reports, and negative responses relative to volume. Individual marketing templates carry their own standing: when negative feedback on one template crosses Meta's internal threshold, Meta pauses that template outright, holding it out of the send path until the pause lifts. Alongside those two gates, per-recipient marketing caps limit how many marketing conversations one customer will accept in a rolling window, so unopened marketing messages now fail to deliver rather than merely costing more. The rating and the pauses are Meta's; what determines them — who you message, with which template, at what cadence — is your call, and each of those levers is a tenant-owned control on the platform.
What Meta's quality telemetry gates
The quality rating is a per-phone-number signal, not an account-level verdict. One WABA can hold a green-rated support number and a red-rated marketing number at the same time, and Meta's remedies track the number, not the account. Three boundaries define where the telemetry applies:
- Per number. Meta computes the rating from the recent block, report, and bad-response rate on messages sent from that number, weighted against volume. Sustained red progressively lowers messaging limits — the tier cap on how many unique customers a number can reach per day — before it escalates.
- Per template category. Templates are judged inside the category they were submitted under. Marketing templates face the strictest standing and the pause machinery below; utility and authentication templates are feedback-gated too, but at different thresholds, because a customer opens a utility send expecting it.
- Templated against freeform. The rating and pauses measure business-initiated traffic — template sends. Freeform replies typed inside the customer-opened 24-hour service window are unpriced and unthrottled, but they do not repair the rating either: the repair comes from the next business-initiated sends earning clean feedback.
The 2026 wave the buyer sees is Meta tightening this from a slow background signal into gates that fire inside the week: marketing templates paused on feedback spikes, per-recipient marketing caps enforced at delivery, and rating-driven tier movement landing while a campaign is still running. The per-message repricing handles the second wave — granular per-message billing on the same sends the quality gates now police.
The metrics state, and what a template pause is
The rating is continuous, not a score handed down periodically. Meta displays it per number as red, yellow, or green, and it moves with the rolling feedback window — so a bad campaign degrades the number within days, and stopped sends start recovering it as the window ages past the campaign.
A template pause is per-template, per-status, and time-boxed:
- The trigger. Recipient feedback on one marketing template — blocks and reports attributed to that template specifically — crosses Meta's threshold. Meta marks the template paused and returns it to the business out of the sendable set. The business keeps the rest of its template library; only the flagged template is held.
- The duration. Pauses are fixed windows. An early pause holds for hours; repeat pauses on the same template hold longer, escalated per recurrence. Sends attempted against a paused template fail with a paused status rather than silently delivering.
- The unblock mechanics. Meta lifts the pause when the window expires, and a template that returns from multiple pauses is a template Meta will eventually disable. The durable unblock is a revision: edit the template, resubmit it through review, and send the revised version. In practice the fastest route is often a sibling template — revise the copy in a related template, submit that, and re-point the campaign while the flagged template sits out its window.
Where the tenant-owned levers sit
The gates are Meta's; every input they measure is a posture the business sets. On Orbit those levers are tenant-owned settings, not platform mandates:
- Template discipline. You author, submit, and revise templates under Channels → WhatsApp → Templates, and each template's current status — review outcome, pause, revision — stays visible there. The template lifecycle concept page documents the full draft → pending → approved → revision-and-resubmit flow a paused template moves through; the same edit-and-resubmit step that clears a rejection is the one that clears a flag.
- Send-rate and timing discipline. Throttling a campaign so feedback arrives steadily instead of in one spike is the same discipline the quiet-hours send-timing post describes for SMS — residential timing windows, capped per-recipient frequency, and pacing that keeps a single-day blast from defining your rating. Frequency caps on the tenant side ceiling how often one contact receives outbound templates at all.
- Consent state. Every send pipeline checks recorded consent on the contact profile before dispatch. Feedback gates punish exactly the sends consent gates prevent: the unsolicited marketing template is what gets blocked and reported.
- Category hygiene. Marketing templates are the cohort the pause machinery targets, so a template that drifts into promotional language is the one that feeds it. The same classification discipline the pricing shift makes load-bearing for the bill, the quality wave makes load-bearing for deliverability: utility intent must read as utility, or the template bills and now also gates as marketing.
None of this is a deliverability guarantee — Meta owns the thresholds. The controls above decide how you arrive at them.
How to bring a paused template back — resubmit and revise
- Read the pause in the template list. The template sits under Channels → WhatsApp → Templates with a paused status, distinct from a rejection — the copy was approved and sent; the recipients judged it in production.
- Treat it as source material, not a retry. Re-sending the identical body after the pause lifts replays the trigger and escalates the next window. Isolate what fed the complaints: the offer, the opener, the audience, or the frequency.
- Revise and resubmit. Edit the template in place or author the corrected version as a related template, and submit it through the normal review queue — the resubmit-revision flow the template lifecycle concept page documents end to end.
- Re-point the campaign at the approved revision. Once Meta approves the revision, update the campaign or flow to the new template name and restart at a reduced volume while the number's rating recovers.
- Hold the cadence caps through recovery. The rating repairs on the next clean business-initiated sends; the caps and quiet-hours pacing keep the recovery traffic from re-triggering the same feedback pattern.
Frequently asked questions
What is the WhatsApp quality rating?
A per-phone-number standing Meta computes from recent recipient feedback — blocks, reports, and negative responses relative to send volume — displayed as red, yellow, or green. Sustained low ratings progressively lower a number's messaging tier, the daily cap on unique customers reached.
What happens when Meta pauses a template?
Meta removes that one marketing template from the sendable set for a fixed window — hours on an early pause, longer on recurrences — and sends against it fail with a paused status until the window expires. The rest of the library stays sendable; repeat pauses on the same template escalate toward it being disabled outright.
How do I unpause a template?
The pause lifts on its own when the window expires, but the durable fix is revision: edit the template or author a corrected related template, resubmit it through review, and re-point the campaign at the approved revision. The edit-and-resubmit flow is the same one a rejection takes — both are documented on the template lifecycle concept page.
Are utility and authentication templates affected?
Less directly. The pause machinery targets marketing templates, which face the strictest feedback thresholds and the per-recipient marketing caps. Utility and authentication templates still feed the number's overall quality rating, and promotional copy drifting into a nominally utility template invites the marketing treatment on both quality and price.
Which parts of this are my controls to set?
All of the inputs: who receives a template, under which recorded consent, at what frequency, in which category, with which copy. Meta owns the thresholds and the gates; platform settings like frequency caps, quiet hours, and consent checks are tenant-owned postures the gates measure.
Resources
- WhatsApp Business API on Orbit — templates, session windows, and broadcast mechanics as shipped.
- Compare WhatsApp alternatives — the channel shortlist behind a WhatsApp-first posture.
- WhatsApp per-message pricing, decoded — the repricing wave this quality wave polices.
- WhatsApp Business Calling GA analysis — the channel's 2025-2026 voice shift.
- RCS vs WhatsApp for business messaging — RCS against WhatsApp on the same buyer rows.
- Apple Messages for Business in 2026 — the parallel channel wave.
- Click-to-WhatsApp ads entry point — Meta's attributed campaign entry onto your number.
- WhatsApp channel docs — template management and send mechanics end to end.
- Consent management docs — recording and enforcing opt-in before any send.
Published 11 September 2026.