WhatsApp template paused or disabled: why it happens and how to recover

Updated on October 29, 2026

A WhatsApp message template gets paused when Meta detects negative customer reactions to it, such as blocks, reports and low read rates. The first pause lasts 3 hours, the second lasts 6 hours, and the third time the template is disabled and can no longer be sent. To recover, find out who received the message and why it bothered them, change the copy or the audience, and lower the frequency before sending again.

This article covers templates that were already approved and were taken down for quality. If your template was never approved, that is a different problem: see WhatsApp template rejected. If what dropped was the rating of the whole phone number, read WhatsApp phone number quality rating.

Rejected, paused, disabled: what is the difference

Situation	What it means	Can you send it?	How to fix it
Rejected (REJECTED)	Meta did not approve the template in review	No	Edit and resubmit, or appeal
Paused (PAUSED)	The template was approved and got negative feedback	No, while paused	Wait for the pause to end or unpause manually; fix the cause
Disabled (DISABLED)	It was paused too many times for low quality	No	Create a new template with different content
Low phone number quality	The problem is the number, not one template	It depends	See the phone number quality article

In practice: a rejection is a review problem (copy, category, format). A pause or a disablement is a reception problem: the copy passed review, but the people who got it did not like it.

How Meta measures template quality

Every approved template has a quality rating, shown in WhatsApp Manager and returned by the API:

Rating	What Meta says it means
GREEN	High quality: little or no negative feedback
YELLOW	Medium quality: negative feedback from multiple users or low read rates; may soon be paused or disabled
RED	Low quality: can still be sent, but at risk of being paused or disabled
UNKNOWN	No score yet; every new template starts here

The signals that count come from customers: blocking the number, reporting the message and not reading it. A YELLOW template can still be sent, but it is your cue to stop and review before it turns into a pause.

Want to try it while you read? Create a Vectalk account and send your first message through the official API. Create free account →

The pause ladder: 3 hours, 6 hours, disabled

According to Meta’s template pausing documentation, the penalty escalates:

1. First time: template paused for 3 hours.
2. Second time: template paused for 6 hours.
3. Third time: template disabled.

While it is paused, the API rejects sends with error 132015 (“template is paused due to low quality”). Once it is disabled, the error becomes 132016 (“template has been paused too many times due to low quality and is now permanently disabled”). In the error code list, Meta’s guidance for 132016 is to submit a new template with different content.

A pause ends on its own when the time is up. You can also unpause early with the manual unpause link in WhatsApp Manager or through the API with POST /{template_id}/unpause. After that, quality is recalculated from the most recent feedback.

One special case: templates paused by template pacing, the mechanism that holds back part of the sends of a new or non-green template until Meta measures the reaction. According to Meta, those only come back with a manual unpause. We cover pacing in our Black Friday on WhatsApp guide.

The webhooks that warn you before it breaks

You don’t have to find out about a pause from an error in the middle of a campaign. Two webhook fields on the messaging account tell the story:

• message_template_quality_update: fires when the rating changes, for example from GREEN to YELLOW.
• message_template_status_update: fires when the status changes, including PAUSED, DISABLED, FLAGGED (got negative feedback and is at risk of being disabled) and REINSTATED (can be sent again).

A quality change, in the format of the webhook reference:

{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102290129340398",
      "time": 1674864290,
      "changes": [
        {
          "field": "message_template_quality_update",
          "value": {
            "previous_quality_score": "GREEN",
            "new_quality_score": "YELLOW",
            "message_template_id": 806312974732579,
            "message_template_name": "payment_reminder",
            "message_template_language": "en_US"
          }
        }
      ]
    }
  ]
}

On the status webhook, a pause arrives with event: "PAUSED". According to the message_template_status_update reference, the other_info object carries a title that says which step of the ladder was reached (FIRST_PAUSE, SECOND_PAUSE, RATE_LIMITING_PAUSE, UNPAUSE or DISABLED) and a text description.

Minimal handling in your backend:

function onTemplateEvent(change) {
  const v = change.value;
  if (change.field === "message_template_quality_update" && v.new_quality_score !== "GREEN") {
    alert(`Template ${v.message_template_name} dropped to ${v.new_quality_score}`);
  }
  if (change.field === "message_template_status_update") {
    if (v.event === "PAUSED" || v.event === "DISABLED") {
      suspendCampaigns(v.message_template_name); // stop the queue, not just the current send
      alert(`Template ${v.message_template_name}: ${v.event} (${v.other_info?.title ?? ""})`);
    }
    if (v.event === "REINSTATED") resumeCampaigns(v.message_template_name);
  }
}

The key point is to stop the queue. If your sender keeps trying, every attempt comes back with 132015 and the whole campaign turns into a pile of errors. For the full format of message status events, see WhatsApp API message status webhook.

Why the template was paused: the usual causes

Meta does not tell you which message triggered the blocks, but the pattern is usually one of these:

• A list without clear consent. People who didn’t ask for the message block it. This is the number one source of negative feedback.
• High frequency. The same template, to the same person, several times a week. See messaging frequency.
• Wrong audience. A product offer to someone who already bought, a payment reminder to someone who already paid, an event reminder to someone who never signed up.
• Copy that doesn’t explain itself. The recipient doesn’t recognize the business or why they got the message.
• No way out. Without a button or instruction to stop receiving messages, customers use the button they have: block.
• Bad timing. A marketing message in the middle of the night gets reports it would not get at 10 a.m.

How to recover, step by step

1. Stop sending that template. Don’t try to get around the pause by renaming it or cloning it word for word: the problem is the content and the audience, and it will happen again.
2. Find out who received it. Cross the sends from the last 24 to 48 hours with replies, reads (read status) and opt-out requests. See which segments had the worst read rates.
3. Trim the list. Remove people who haven’t read anything in a long time, who asked to leave, and who joined without a clear opt-in. A smaller, engaged list beats a large, cold one.
4. Rewrite the copy. Open with the business name and the reason for the message (“You asked to get updates about…”). One idea per message, one call-to-action button and a way out (“Stop updates”). Tips in how to write a WhatsApp marketing message.
5. Check the category. If the template is utility but sounds promotional, it shouldn’t be utility. See how Meta categorizes your template.
6. Ramp up slowly. After editing (the template goes back to review) or creating a new one, send to your most engaged segment first and watch the quality webhook before opening it to the whole list.
7. Keep a backup. For critical campaigns, keep a second approved template with different copy, so you don’t depend on a single one.

Edit the paused template or create a new one?

Meta’s pausing page says a paused template can be edited: when you resubmit it, it goes back to “In review” and can only be used after it is approved again. For a disabled template, the guidance on code 132016 is to create a new template with different content. In practice, if the copy was the problem, a new template with a different approach is the cleanest path. Creating and editing through the API is covered in how to create, edit and delete templates via the API.

How to lower the risk of a pause

Practice	Why it helps
Explicit opt-in, recorded with date and source	People who asked don’t report
A “Stop updates” quick reply button, with opt-out handled in the backend	Gives a way out that isn’t blocking
Segment by behavior (bought, clicked, read)	Relevant messages get read
Cap frequency per contact	Reduces list fatigue
Monitor message_template_quality_update	You act on yellow, before the pause
Keep utility and marketing separate	Service messages don’t inherit the rejection of promotions
Respect error 131049 and wait 24 hours before resending	Pushing people who are saturated creates more rejection

About the last item: 131049 is the per-user marketing limit, a separate Meta mechanism. It does not pause the template, but resending in a loop to people who were capped is a fast way to generate negative feedback.

How to do this with Vectalk

Vectalk is a proxy for the official WhatsApp API: the templates are the ones in your Meta account and the webhooks follow Meta’s format, so the events and codes in this article are the same. With the Vectalk API you can list templates with their status, create a new template and edit templates whose status is APPROVED or REJECTED. Incoming webhooks are forwarded with the same payload to the URLs you register on the instance, and the dashboard logs help you find sends that failed with 132015 or 132016. Sign up at apps.vectalk.com.br/register.

Frequently asked questions

How long does a WhatsApp template pause last?

Three hours the first time and six hours the second time. The third time, the template is disabled. The pause ends on its own, but you can unpause earlier in WhatsApp Manager or through the API.

Am I charged for a paused template?

A message the API rejects with 132015 is not delivered, and Meta only charges for delivered messages. The real cost of a pause is a stalled campaign.

Does a template pause take down the phone number?

Not directly: the pause applies to the template. But the negative feedback that caused it also weighs on the number’s quality rating, so handle both together.

Can I appeal a disabled template?

The pausing documentation talks about editing and resubmitting for approval; the error list says to create a new template with different content. A formal appeal is the path for templates rejected in review, not for quality takedowns.

Why was my new template paused after only a few sends?

Most likely because of template pacing: Meta holds part of the sends of new templates until it measures the reaction and, if the signal is bad, pauses the template. In that case, you have to unpause it manually.

---

Official sources checked on October 29, 2026: Template pausing, Template quality, message_template_status_update webhook, message_template_quality_update webhook, Error codes, Per-user marketing limits.