# WhatsApp Template Pacing
### What is Template Pacing?
* [**Template Pacing**](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-pacing) is a process where WhatsApp gradually sends template messages in batches rather than delivering them to all users immediately.
* An initial set of messages is sent to a small audience, and based on user feedback (such as engagement, blocks, or reports), WhatsApp either scales delivery or slows it down.
#### Here is the simple 3-step process:
* **Step 1: The Test Run** – You trigger a large blast of messages. WhatsApp sends a small batch immediately but puts the rest on "hold."
* **Step 2: The Listening Phase** – WhatsApp waits for a short period (usually under an hour) to see if customers are clicking "Report" or "Block."
* **Step 3: The Verdict** –
* **If the feedback is good**, the "held" messages are released and sent to everyone else.
* **If the feedback is bad,** the template is [paused](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-pausing/), and the remaining messages are deleted (dropped) so you don't get banned.
Why does Template Pacing happen, and why are messages delivered in phases instead of all at once?
Template Pacing is applied when WhatsApp needs to **evaluate the quality and performance of a template before delivering it at scale**. Instead of sending messages to all users immediately, they are delivered in phases to monitor user feedback.
This typically happens when:
* The template is **new or has limited performance history**
* The template was **recently paused and reactivated**
* The template has a **low or uncertain quality rating** (not *High/Green*)
How will I be notified if my template is paused?
When a template is paused because of Template pacing, WhatsApp notifies the business through several channels to ensure the message is seen quickly:
* **Meta Business Suite Notifications:** You will receive a direct notification within the Business Suite platform.
* **WhatsApp Manager Banner:** A warning banner will appear at the top of your WhatsApp Manager dashboard.
* **Email:** An automated alert is sent to the email address associated with your WhatsApp Business Account.
* **Webhooks:** If you have set up developer webhooks, you will receive a `message_template_status_update` with the event value set to `paused`.
**What happens to the messages?**
Once the template is paused, any messages that were being "**held**" are dropped (deleted). If you are using the Cloud API, these will show a status of `failed` with Error Code 132015.
What happens if my template is paused due to low quality?
When a WhatsApp template gets a **Low Quality Rating** (shown as *Red* or *Active – Low Quality*), Meta pauses it to protect your number’s reputation.
**1. Pause Duration (Escalation)**
When a template receives **negative user feedback** (such as blocks, reports, or low engagement), Meta assigns it a **Low Quality Rating**.
If this happens, the template is **automatically paused**, and repeated issues lead to stricter actions over time.
**How the escalation works**
**1st Instance — Temporary Pause (3 hours)**
* The template is paused for **3 hours**
* This acts as a **warning stage**
* You can use this time to:
* Review the message content
* Check if the audience targeting was correct
👉 After 3 hours, the template becomes active again\
👉 However, the **quality risk still exists** if no changes are made
***
**2nd Instance — Extended Pause (6 hours)**
* If the same template again receives poor feedback, it is paused for **6 hours**
* This indicates a **pattern of negative user response**
At this stage:
* Meta is signaling that the template is **not performing well**
* Continuing to use it without changes is risky
👉 Even after unpausing, sending the same content to the same audience can quickly lead to the next stage
***
**3rd Instance — Permanent Disablement**
* If the template again reaches low quality:
* It is **permanently disabled**
* It **cannot be used again**
At this point:
* The template is considered **harmful to user experience**
* You must **create a new template** with improved content
What should I do when my template is paused?
A paused template indicates negative user feedback (e.g., blocks or reports). Review and improve it before reuse, as sending it unchanged may lead to permanent disablement.
#### Best Practices
**1. Pause ongoing campaigns and automations**
Immediately stop any **campaigns or workflows** that are using the paused template.
**Why this matters:**
* Continued attempts to send the same template can reinforce negative signals
* Even after the template becomes active again, sending it without changes can quickly trigger another pause
**What to do:**
* Pause campaigns manually
* Disable or edit flows that include this template
***
**2. Review the message content**
Carefully evaluate the template content to understand why users may have reacted negatively.
**Common issues:**
* The message feels **too promotional or repetitive**
* Content is **not relevant** to the recipient
* Message is **unexpected** (user did not opt in or recently engage)
* Tone is too aggressive (e.g., heavy discounts, urgency spam)
**What to do:**
* Simplify and clarify the message
* Focus on **value instead of just offers**
* Ensure the message aligns with what the user expects
***
**3. Check audience targeting**
Poor targeting is one of the most common reasons for low-quality ratings.
**Why this matters:**
* Sending messages to uninterested users leads to **blocks and reports**
* Even a good message performs poorly with the wrong audience
**What to check:**
* Are you sending to **recently engaged users**?
* Are you targeting users who showed **interest in this category**?
**What to do:**
* Use segmentation (e.g., Conversation Tags)
* Avoid sending to cold or inactive users
***
**4. Improve the template before reusing it**
Do not reuse the template as-is. Update it to reduce the chances of negative feedback.
**Ways to improve:**
* Make the message more **personal and relevant**
* Reduce overly promotional language
* Add **context** (why the user is receiving this message)
* Keep the message concise and clear
**Example improvement:**
❌ “Flat 50% OFF! Buy now!!!”
✅ “Hi {{name}}, based on your recent interest in sneakers, here’s a limited-time offer you might like.”
***
#### 5. Restart with a smaller and active audience
Once the template becomes active again, avoid sending it to your full audience immediately.
**Why this matters:**
* Template pacing will evaluate early feedback again
* A poor response in the next batch can lead to **faster escalation (6-hour pause or disablement)**
**What to do:**
* Send to a **small, highly relevant segment first**
* Monitor early performance (engagement, complaints)
* Gradually scale only if feedback is positive
Does Meta provide the reason why a template was paused?
No, Meta does not provide a specific reason for each pause.\
Templates are paused based on **negative user feedback signals**, such as blocks, reports, or low engagement.
You can monitor:
* Template quality rating
* Template status (Active, Paused, Disabled)
Does Template Pacing apply to all templates?
No, Template Pacing is more likely to apply when:
* A template is **new**
* It has **limited performance history**
* You are sending messages to a **large audience**
Templates with strong performance history may experience less pacing.
What is the difference between Template Pacing and Template Pausing?
* **Template Pacing:** Messages are sent in batches and evaluated before scaling delivery
* **Template Pausing:** The template is temporarily stopped due to negative feedback and cannot be sent
Does Template Pausing affect my WhatsApp number quality?
Yes, indirectly.\
Repeated negative feedback on templates can impact your **overall messaging quality and reputation**, which may affect future message delivery.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.mercuri.cx/communication-channels/whatsapp-integration/whatsapp-template-pacing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.