Want help applying this guide?Ask the DripTell team
When a WhatsApp campaign stops because its message template is paused, stop the campaign at your side too. Do not keep retrying the same send, and do not assume this is a temporary API outage. First preserve the affected audience and schedule. Then identify whether Meta applied a timed quality pause or a pause during template pacing. The recovery is different.
This matters because the failure is about the template and its reception, not simply the delivery connection. A retry loop cannot repair poor targeting, weak relevance, or a message that arrived at the wrong time.
Stop the campaign before doing anything else
A paused template cannot be sent. Meta says attempts are rejected, even though those attempts are not charged and do not count against the messaging limit. Letting an automation continue only fills logs with avoidable failures and makes it harder to see which customers still need a message.
Pause every campaign and automation that depends on the template. Keep a record of the template ID, language, campaign, intended recipients, scheduled time, and the last successful send. Do not quietly switch to another template merely to keep volume moving. The replacement might carry the same problem and make the evidence harder to read.
If the message was time sensitive, decide whether another appropriate channel or a human follow-up is justified. That is a customer decision, not a reason to bypass WhatsApp controls.
Work out which pause happened
WhatsApp exposes template status in WhatsApp Manager, through the Template API, and through the message_template_status_update webhook. Capture that evidence before anyone edits the template.
- Stop dependent sendsFreeze campaigns and retries that use the paused template.
- Capture status evidenceKeep the template ID, status event, audience, schedule and last successful send.
- Classify the pauseSeparate a timed quality pause from a pacing pause that needs manual action.
- Correct the causeReview message relevance, audience, consent, frequency, timing and workflow logic.
- Test before scalingResume with a small eligible group and stop again if quality weakens.
Meta's current template pausing documentation says a template that reaches the lowest quality rating can be paused for three hours on the first instance and six hours on the second. A third instance disables it. Those timed pauses can end automatically.
A pacing pause is different. Template pacing holds some marketing or utility messages while Meta waits for early customer feedback. If the signal turns negative, held messages are dropped with error 132015 and the template becomes paused. Meta's template pacing documentation says a template paused during pacing must be manually unpaused in WhatsApp Manager or through the API.
| Signal you see | What it tells you | Safe next action |
|---|---|---|
| Active with low quality | Sending still works, but the template is at risk | Stop expansion and review content, audience, and timing |
| First or second timed pause | Low quality triggered a temporary pause | Keep campaigns stopped and use the pause to correct the cause |
| Paused during pacing | Early feedback caused held messages to fail | Correct the cause and manually unpause before a controlled test |
| Disabled | Repeated poor feedback ended normal sending | Edit and resubmit or appeal only with defensible evidence |
The distinction should also be visible in your template approval process. A status called “paused” is not enough for an operator to choose the right recovery.
Fix the cause instead of waiting for the clock
Quality rating reflects usage, customer feedback, and engagement. A pause does not tell you which sentence to change. Review the whole sending decision.
Start with the message. Does it clearly match the purpose the customer expects? Are variables complete and understandable? Is promotional intent hiding inside something presented as a service update?
Then inspect the audience. A useful message sent to the wrong people is still unwanted. Check consent, recent engagement, exclusions, frequency, and whether the customer has already completed the action. Review timing too. A class reminder sent after a booking was cancelled can produce negative feedback even when its wording is polite.
Use recipient-level delivery evidence, not a campaign total alone. Compare the last successful cohort with the cohort that produced the quality decline. Look for a changed segment, language, offer, frequency, or trigger. Do not invent a cause from one complaint.
Editing a paused template may be the right choice, but it has a consequence. Meta says an edited template returns to review and cannot be sent until it is approved and active again. If the content is sound and the problem was targeting or timing, fix the business logic instead of rewriting words that were not responsible.
Resume with a small controlled test
Wait for a timed pause to end, or manually unpause a pacing pause after the cause is addressed. Confirm the status is active before releasing anything. Then send to a small, clearly eligible group rather than reopening the full queue.
Watch the template status, quality updates, message failures, delivery, and replies. Keep the test separate from the old campaign so its evidence is readable. If quality weakens again, stop. A successful API response is not proof that the template is healthy.
Only widen the send when the message remains relevant and the early group behaves as expected. Keep the customers who became ineligible during the pause out of the recovered queue. Someone who purchased, opted out, or already received a human answer should not receive a stale automated message later.
Make pauses part of normal operations
Template pauses should have an owner and a runbook before the next campaign. Route status and quality webhooks to a monitored queue. Connect each template to the campaigns and workflows that depend on it. Define who can stop sending, who reviews audience logic, who can edit and resubmit, and who authorizes the controlled restart.
In DripTell, teams can keep WhatsApp conversations, template management, campaign activity, and customer replies close to the same operating workflow. The important control is still human. A platform can preserve status and evidence, but someone must decide whether the message deserves to resume.
Treat a pause as customer feedback arriving through an operational signal. The safest response is not to push harder. It is to stop, understand, correct, and test.
Frequently Asked Questions
Can a paused WhatsApp template still be sent
No. WhatsApp rejects attempts to send a paused template. Stop dependent campaigns until the template is active again.
Does every paused template unpause automatically
No. Timed quality pauses can end automatically after the documented period. Templates paused during pacing must be manually unpaused through WhatsApp Manager or the API.
Should I edit the template or wait
Wait only when the message, audience, and timing are still sound and the pause is temporary. Edit when the content is part of the problem. Remember that an edit sends the template back for review.
Are rejected attempts billed
Meta says attempts to send a paused template are not charged and do not count against the messaging limit. They are still rejected, so repeated attempts create noise without reaching customers.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy