WhatsApp Template Statuses & Rules

Summary

A message template does not stay approved forever. Even an approved template can move to paused or disabled if customers start blocking it or marking it as spam. This article explains all the possible statuses at Meta, the statuses Mumble actually displays, the rules that cause a rejection or a shutdown, and the quality rating Meta uses to decide whether to keep allowing you to send.

Background: why the status stays alive even after approval

Sending a message template is not like sending an email. On WhatsApp, Meta continuously evaluates how your customers respond to the messages you send. If many of them block you, mark you as spam, or simply ignore you, Meta lowers the quality of the number and of the specific template, and at some point stops allowing you to send. All of this happens without you doing anything. That is why managing message templates is not a one-time act of “create and approve,” but an ongoing process in which you have to monitor, review results, and correct course.

The statuses

What Meta knows

In Meta’s system, every message template has one of the following six statuses:

Pending. The template has been submitted for approval and the review is underway. This usually takes minutes to hours.
Approved. The template was approved and you can send it.
Rejected. The template was rejected. The reason will appear in the description.
Flagged. The template was approved but Meta has detected a drop in its quality. Sending is still allowed, but there is a growing risk of a shutdown if the trend continues.
Paused. Meta has temporarily paused the template. You cannot send it until the quality recovers or enough time passes.
Disabled. The template has been permanently disabled. It cannot be brought back to life. You have to create a new template.

What Mumble displays

On the message templates screen in Mumble, there are only three filter tabs:

Approved. Includes all templates in Meta’s Approved state.
Pending. Includes all templates in the Pending state.
Not approved. Includes all templates in the Rejected state.

The Flagged, Paused, and Disabled statuses do not get separate tabs. If a template of yours is approved but suddenly stops reaching customers, it is likely in the Paused or Disabled state at Meta, even if in Mumble it still appears under “Approved.” In that case, look at the WhatsApp account status card on the main screen, or contact Mumble support for an account-specific check.

The quality rating

Meta measures how customers respond to your messages over the last 7 days, and assigns each of your numbers and each message template a quality rating. Three levels:

High. High quality. No special limits, and a better chance of moving up at the next jump in daily sending limits.
Medium. A drop in quality. Meta is watching closely. It is worth reviewing the content and the audience before it deteriorates.
Low. Low quality. Meta reduces the number of new customers you can initiate a conversation with in 24 hours, and in extreme cases pauses the template entirely.

The factors that lower quality:

Blocks. Customers who tap “Block” in their WhatsApp after receiving a message.
Spam reports. Customers who mark the message as spam.
Widespread non-response. Meta also looks at whether customers open the messages at all. A very low open rate is a bad sign.
Irrelevant messages. Sending to a customer who is not expecting it (for example, someone who opted out or never opted in).

The structural rules Meta enforces

The template name

Lowercase English letters, numbers, and underscores only. No spaces, no Hebrew, no special characters. An invalid name is rejected immediately, even before the content review.

One language per template

The body of the template must be in a single language. Mixing Hebrew and English in the body will be rejected. Isolated technical words like URL or SMS are an exception.

Variables

Numeric format only. {{1}}, {{2}}, {{3}}. Names like {{name}} are not supported in a message template (that only applies in the chatbot canvas).
Sequential with no gaps. If you used {{1}}, there must be a {{2}} before {{3}}.
You cannot start or end the body with a variable. “{{1}}, welcome” will be rejected. “Welcome {{1}}” will pass.
You cannot place two variables next to each other. {{1}}{{2}} will be rejected. There must be at least a comma, or a space with a word, between them.
The variable’s content at send time cannot contain line breaks, tabs, or 4 consecutive spaces. This rule is checked for every variable value before sending to the customer, and you must make sure there are no such values in your data.

Content

Clear context. The customer needs to understand why they are receiving the message. A generic message along the lines of “Hi, we have something for you” increases the chance of blocks and a quality drop.
Trustworthy links. Short URLs like bit.ly are considered suspicious by Meta. Use a full link to your own domain.
In a marketing message, an opt-out option. A Quick Reply button triggered through the opt-out picker removes the customer automatically in Mumble.

The three categories and the trap between them

Marketing

Promotions, launches, surveys, cart abandonment. The most flexible category in terms of content (emojis, media, and multiple buttons are allowed), but also the most expensive in Meta’s pricing.

Utility

Service messages that relate to an action the customer took. Order confirmation, shipping status, appointment reminder. It must relate to a specific customer event. You may not add any marketing sentence, not even a small “deal of the week” at the end.

Authentication

OTP codes only. Text only, no emojis, no links, no branding. The code itself goes in a variable ({{1}}). This is the cheapest category, but also the most restricted.

The trap

If a message that is 90% service-related also contains a single marketing sentence, Meta will classify it as Marketing and charge it at marketing pricing. A classic example: “Your order {{1}} is on its way. By the way, this week’s deal: 10% off.” This is not a service message. The way to save money: create two separate templates. One pure UTILITY (“Your order is on its way”), and a separate MARKETING one (“This week’s deal”).

Opt-in: you cannot send without it

Meta requires that you be able to prove that every customer who receives a message from you outside the 24-hour window gave explicit consent to receive messages from you. Ways Meta accepts as valid opt-in:

An explicit checkbox on a form. The customer checked a box that says “I agree to receive WhatsApp updates from [business name].” A pre-checked box is not valid.
The customer messaged you first. In response, you have 24 hours of freedom without a message template, and an option to reach out afterward as well.
Starting a conversation from a link or a widget. The customer clicked a WhatsApp link on your site or a widget and started a conversation.
A documented verbal consent. A sales agent recorded the consent during a call. The proof bar is high; it is recommended to note the date and time.

What is not valid: a purchased list, contacts that sales reps collected without a specific question, or general agreement to terms of service. Sending without valid opt-in is the number-one cause of blocks, quality drops, and temporary suspension of entire numbers.

What to do in each status

If the template is “Pending” for more than 24 hours

Check the WhatsApp account status card on the main screen. If the account quality is fine and the number is active, wait longer. If the status does not change even after 48 hours, contact Mumble support.

If the template was rejected (“Not approved”)

A message template cannot be edited after it is created. The only way to fix it is to delete the existing template and create a new one with a different name (names must be unique). Before recreating it, read the rejection reason in the description, and fix the specific problem. The common reasons are: a wrong category, marketing content in a service category, a variable at the start or end of the body, or a suspicious URL.

If the template was approved but stopped working

This means Meta moved it to Paused or Disabled, even if in Mumble it is still marked as approved. Your steps:

Stop sending that template for 24 to 48 hours.
Check the quality rating (the WhatsApp account status card on the main screen).
If the quality dropped, reduce the audience size. Send only to customers who expect the message and have engaged in the past.
If the template is in the Disabled state, it will not come back to life. Create a new template with different wording and a more focused audience.

Examples of common mistakes

Marketing content in a service message

Body: “Your order {{1}} is on its way. This week, get 15% off additional items in the summer category.”
Result: the message will be classified as Marketing. It will be charged at a higher rate. It also raises the chance of blocks if customers were not expecting marketing content.
Fix: two templates. The first UTILITY with the status only. The second MARKETING, sent only to those who gave a marketing opt-in.

A variable at the start of the body

Body: “{{1}}, we have an update for you about {{2}}.”
Result: automatic rejection by Meta.
Fix: “Hi {{1}}, we have an update for you about {{2}}.”

Sending to customers without opt-in

Situation: you imported a list of 5,000 customers from your old system and sent them a greeting message.
Result: a high block rate, a quality drop for the entire account, and a temporary suspension of the number.
Fix: send only to customers with a documented opt-in. For those without one, use other channels (email, advertising) to invite them to actively join your WhatsApp channel.

The bottom line

A message template is an ongoing relationship with Meta, not a document that was approved once. As long as you send only to customers who are expecting you, stay in the correct category, and keep a low block rate, the template will stay available. The moment the quality drops, the template will be paused even if it was once approved.

Want to Use WhastApp API?

WhatsApp Message Templates: Statuses, Rules, and Quality Rating

Mumble Team