WhatsApp continuously monitors the quality of every registered business phone number based on how customers respond to messages sent from it. A poor quality rating limits your ability to send messages and, in serious cases, can result in your number being restricted or your templates being paused by Meta. Maintaining a good quality rating is an ongoing responsibility — it is the direct result of how relevant, well-timed, and consent-respecting your messaging is.Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
What this covers
- How WhatsApp calculates phone number quality
- What happens when quality degrades
- Best practices for protecting deliverability
- Common violations to avoid
How quality is calculated
WhatsApp assigns a quality rating to your phone number based on signals from customers who receive your messages. The main signals are:- Block and report rates — how often recipients block your number or report messages as spam
- Template rejection patterns — whether your submitted templates are frequently rejected for policy violations
- Message frequency vs. engagement — whether customers are receiving messages they did not expect or are not engaging with
What happens when quality degrades
Quality degradation follows a progression:| Quality Level | Impact |
|---|---|
| High | Full messaging throughput, no restrictions |
| Medium | Warning state — no immediate restriction but continued degradation will escalate |
| Low | Reduced per-day message throughput limits applied to the phone number |
| Flagged / Restricted | Messaging may be paused; templates may be suspended by Meta |
Best practices
- Only message opted-in customers. Sending to customers who have not explicitly opted in is the fastest path to high block rates. Galantis enforces this automatically, but imported lists should be reviewed carefully before use.
- Use personalization variables. Messages that address the customer by name or reference their specific order or product are less likely to be perceived as generic spam.
- Respect frequency caps. Configure per-automation frequency caps to prevent a single customer from receiving too many messages in a short period. Over-messaging is a primary driver of blocks and reports.
- Honor opt-outs immediately. When a customer replies STOP, Galantis moves them to
UNSUBSCRIBEDimmediately. Do not attempt to re-engageUNSUBSCRIBEDcustomers through other channels or lists without a new explicit opt-in. - Match template category to content. A Utility template that delivers marketing content will be flagged by Meta during review. Use the Marketing category for all promotional messages, even if the Utility category offers lower per-message costs in some markets.
- Avoid overly promotional language in Utility templates. If you submit a Utility template for transactional use, keep the content transactional. Embedding promotional CTAs or offer language in Utility templates is a common rejection reason.
Common violations
These are the most frequent causes of quality degradation and template rejection:- Sending marketing messages to customers with
NOT_SUBSCRIBED,UNKNOWN, orUNSUBSCRIBEDconsent status - Submitting templates that misrepresent their purpose — for example, categorizing a promotional announcement as a Utility message
- Exceeding per-user message frequency — sending multiple campaign broadcasts or automation sequences to the same customers within a short period without frequency caps
- Using template variables in misleading ways — for example, a button URL that navigates somewhere different from what the template text implies
Monitoring quality in Galantis
Galantis surfaces message-level delivery data —SENT, DELIVERED, READ, and FAILED statuses — per campaign and automation. Tracking read rates and failed delivery rates across sends is an early indicator of quality issues before they escalate to phone number restrictions.
For phone-number-level quality data, refer to your WhatsApp Business Account settings in Meta Business Manager directly.
Related guides
- Opt-in & Consent — How Galantis enforces consent to protect deliverability
- Templates — Quality Metrics — Template-specific quality signals and optimization
- Automations — Frequency Caps — Configuring per-automation send limits