Template approval is not the end of Meta’s evaluation — it is the beginning. Once a template is live and sending, Meta monitors how customers respond to it. Block rates, report rates, delivery failures, and category compliance signals all feed into a quality assessment that can affect your template’s status and your phone number’s throughput capacity. A template that passes approval but receives poor engagement signals can be paused by Meta without warning, removing it from active use in campaigns and automations mid-flight.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
- The quality signals Meta monitors for live templates
- What happens when template quality degrades
- How template quality connects to phone number quality
- Optimization practices for keeping templates healthy
Quality signals Meta monitors
Meta does not publish the exact formula used to calculate template quality, but the primary signals are well-documented: Customer block and report rates — When a customer blocks your WhatsApp number or reports a message as spam after receiving a template, it is a strong negative quality signal. A single block is not significant; a pattern of blocks across recipients of the same template indicates the message is unwanted. Delivery failure rates — Templates with high delivery failure rates — messages sent but not delivered — accumulate negative signals. This can result from targeting inactive or invalid numbers, but also from template-level issues that affect deliverability. Template category compliance — Meta reviews live templates against their declared category on an ongoing basis. A Utility template with embedded promotional content that passed initial review may be flagged through quality monitoring when actual send patterns reveal its marketing nature. Message frequency vs engagement — Sending a template to the same customers repeatedly in a short period without engagement signals — no reads, no replies, no clicks — indicates the message is not valued by recipients.What happens when quality degrades
Template quality degradation follows a progression that can affect both the template and the phone number it sends from:| Quality State | Consequence |
|---|---|
| High quality | No restrictions — full throughput, normal delivery |
| Medium quality | Warning state — no immediate action but continued degradation will escalate |
| Low quality | Template may be paused by Meta — messages using it fail until quality recovers or the template is revised |
| Paused / Suspended | Template cannot send — active campaigns fail and automation Action Nodes fail for customers who reach them |
FAILED status for every customer who reaches it. The automation does not stop; the individual message sends fail silently until the template is restored or replaced.
Phone number impact — Template quality issues aggregate at the phone number level. Multiple templates with poor quality signals simultaneously will degrade the phone number’s overall quality rating more rapidly than a single template issue. See Compliance — Quality & Deliverability for how phone number quality affects throughput.
Monitoring template quality
Template quality metrics in Galantis are tracked through message-level delivery data —SENT, DELIVERED, READ, and FAILED statuses per message, aggregated per template. This gives an indirect view of quality health:
- Read rate relative to delivered rate — a low read rate suggests customers are receiving the message but not opening it, which may correlate with high block rates
- Failed rate — persistent delivery failures on a specific template warrant investigation
- Trend over time — a declining read rate across sends of the same template is a leading indicator of quality degradation before Meta flags it formally For phone-number-level quality data and formal template status information from Meta, refer to your WhatsApp Business Account settings in Meta Business Manager directly. Galantis does not currently surface Meta’s internal quality score for individual templates within the dashboard.
Optimization practices
Match category to content precisely. The single most effective quality practice is accurate categorization. A Marketing template sent to opted-in customers who expected it has fundamentally better quality signal characteristics than a Utility template used for promotional content — because the recipients of the latter are more likely to block or report. Personalize with variables. Templates that address the customer by name and reference relevant data (their order, their browsed product, their location) generate better engagement signals than generic broadcast copy. Usecustomer.first_name and order variables wherever the template context supports it.
Respect frequency caps. A customer who receives the same template — or different templates from the same number — multiple times in a short period is more likely to block. Configure automation frequency caps to prevent over-messaging, and space campaign sends to avoid hitting the same audience repeatedly within a short window.
Honor opt-outs immediately. Customers who replied STOP and are incorrectly messaged again are almost certain to block and report. Galantis enforces opt-out automatically, but manually imported contact lists should be reviewed carefully to ensure no UNSUBSCRIBED customers are included.
Avoid spam-like language in Utility templates. Phrases like “Limited time offer!”, “Act now!”, or “Exclusive deal!” in a Utility template are consistent quality flags during Meta’s ongoing monitoring, even if they passed initial review. Keep Utility templates transactional in both structure and language.
Retire poorly performing templates. A template with consistently low read rates and high failure rates is better replaced than defended. Archive it, analyze what drove the poor performance, build a revised version, and submit the new template.
What to do when a template is paused
- Go to Templates → [Template Name] → Status in Galantis to confirm the current status and any reason provided by Meta
- Review the template content against Meta’s current content policies — policies evolve and a template compliant at approval may conflict with a later policy update
- Assess whether the quality signal cause is content-based (fix the template), audience-based (review who is being targeted), or frequency-based (adjust send cadence)
- Make the necessary changes and resubmit
- If the template is used in active automations, those automations will resume sending correctly once the template is restored to
APPROVEDstatus — no automation re-activation is required
Related guides
- Template Categories — Category accuracy as the primary quality lever
- Approval Lifecycle — How template status changes when quality degrades
- Compliance — Quality & Deliverability — How template quality aggregates to phone number quality
- Support — Template Rejection — Troubleshooting rejected and paused templates