Merkuva
All posts

September 16, 2026· 7 min read

The WhatsApp template approval guide: categories and rejection reasons

Why was your template rejected? Category selection, variable fields, the reasons reviews turn templates down, and how to fix and resubmit one.

By The Merkuva Team

Once the 24-hour customer service window closes on WhatsApp, your only way to speak is a pre-approved template message. Which is why template approval is where most teams get stuck for the first time: the message is rejected, the reason is short and technical, and it is not obvious what to do next.

The short answer: submit the template under the category that matches the message's real purpose (utility, marketing or authentication); give every variable a sample value; keep the text to one subject; and if it is rejected, work out whether the problem is the category or the wording before you rewrite anything.

What a template message actually is

A template message is a wording Meta has reviewed and approved in advance. It contains variable fields — {{1}}, {{2}} — that get filled with real values (a name, an order number, a date) at send time. After approval the wording itself cannot be changed freely; to change it you submit a new version and wait for approval again.

One question tells you whether you need a template: did the person write to you in the last 24 hours? If yes, you do not need one — free text is fine. If no, a template is the only way. For the detail, see the WhatsApp 24-hour rule guide.

Choosing the category: the decision that matters most

Meta sorts templates into three categories. The category sets both how strictly the message is reviewed and what it costs.

CategoryWhat it is forTypical example
UtilityInformation about an existing transaction, order or request“Your order has shipped”, “Your appointment is tomorrow at 2pm”
MarketingPromotion, campaigns, re-engagement“The new season sale has started”, “You left something in your basket”
AuthenticationOne-time codes and login verification“Your login code: 483920”

Per Meta's pricing documentation, the WhatsApp Business Platform has charged per message since 1 July 2025. Non-template messages sent inside an open customer service window are free, and the same document states that utility templates inside an open window are not charged either.

The most common mistake is submitting a promotional message under the utility category. Review usually catches it, and the template is either rejected or approved with its category changed. The second outcome is the sneakier one: your template works, but it is billed differently than you expected.

A simple test: is this message the direct continuation of something the person actually did? If yes, it is utility. If you are sending it because they “might be interested”, it is marketing.

Writing the text

Review reads the text the way a person would. What works:

  • One subject. A template that carries both a shipping update and a campaign announcement looks wrong in either category.
  • Put variables inside sentences. Starting or ending a message with {{1}} is a frequent rejection reason; a variable should carry meaning inside the text, not stand in for it.
  • Give sample values. When you submit, write a realistic example for every variable (“Alex”, “12345”, “2 business days”). Leaving them empty or typing “abc” can get the template rejected.
  • Don't abbreviate. Telegram-style wording like “Order no: {{1}} delivery: {{2}}” reads as meaningless in review. Write full sentences.
  • Capitals and punctuation. All-caps text and strings of exclamation marks are read unfavourably.
  • Don't promise. Phrases like “guaranteed results” are risky both under policy and under advertising rules.

For starting points, templates 5, 12 and 13 on the message templates page were written with approval in mind.

The most common rejection reasons

ReasonWhat it actually meansWhat to do
Wrong categoryThe text does not fit the chosen categoryReassess the purpose and resubmit under the right one
Bad variable formatVariable numbers skipped, or the text starts with oneNumber them in order; move the variable inside a sentence
Missing sample valuesNo examples given for the variablesWrite a realistic example for each
Policy violationRestricted product, health claim, exaggerated promiseSimplify the text, remove the claims
Content not meaningfulThe text does not make sense on its ownWrite full sentences and put the context in the text
Duplicate templateThe same content is already approvedUse the existing template

Rejection reasons tend to be terse. The practical approach: question the category first, then the variables, and only then the wording. Most teams do the reverse and rewrite the text over and over when the problem was the category.

After approval: quality rating

Approval is not the end. Meta assigns a quality rating to your number and your templates based on how people react to your messages. A template that collects blocks and reports can be paused even while approved, and your number's sending limit can drop.

Protecting it is a content question, not a technical one:

  • Send marketing templates only to people who genuinely consented.
  • Keep frequency low; more than one marketing message a week is too much for most lists.
  • Put the opt-out in every marketing message — and actually remove the people who use it.
  • Don't turn utility notifications into marketing material.

In Turkey there are also obligations under the commercial electronic message regulation and KVKK (the data protection law). Keep a record of who consented, when and for which channel; the relevant bodies are the Message Management System (iys.org.tr) and the Personal Data Protection Authority (kvkk.gov.tr). Ask your own legal counsel about your situation.

Don't make the whole flow depend on approval

A practical design suggestion: build the part of the flow that runs inside the window separately from the part that goes outside it. Then the whole flow does not stall while a template is in review — the in-window part keeps working, and you switch on the outside branch when the template clears.

The same structure helps on rejection: one rejected template affects one branch, not your entire automation.

Frequently asked questions

How long does template approval take?

Most templates come back within minutes; some take a few hours. It varies with the category, your account's history and review load. Submitting a template the day before a campaign is risky — get campaign wording into review at least a few days ahead.

Can I edit the text of an approved template?

Not the wording itself; you can put whatever you like into the variable fields at send time. To change the text you create a new template and submit it for approval again. That is why writing templates generically and personalising through variables is more sustainable than creating a separate template for every campaign.

Does sending a template open the 24-hour window?

No. Per Meta's documentation, the event that opens the window is the user messaging or calling you. Your template goes out, but the window does not open unless the user answers. The moment they do answer, a fresh 24-hour window starts and you can use free text again.

How many times can I resubmit a rejected template?

There may be a technical limit, but the real issue is that repeatedly submitting near-identical wording works against your account's review history. Resubmitting the same text unchanged achieves nothing. Review the category, then the variable format, then the wording, and change one thing per attempt — that way you also learn what the problem was.

Are utility templates free?

Per Meta's pricing documentation, utility templates sent inside an open customer service window are not charged. Utility templates sent outside the window are. Current unit prices vary by country, so check Meta's pricing page.

Is there template approval on Instagram?

No. Instagram and Messenger have no template concept; the way out of the window is one of the tags Meta permits. The best known is the human agent tag, which allows up to 7 days for replies written by a person and cannot be attached to automation. For the differences between the two channels, see the comparison table in the 24-hour rule guide.

In summary

Template approval looks like bureaucracy, but the logic behind it is simple: Meta wants to know in advance what a message the user did not ask for actually says. Read your text with that in mind — “how would I feel receiving this?” — and pick the category from the message's real purpose. Your rejection rate drops fast.

To manage templates and in-window flows from one place, have a look at WhatsApp automation; if a term trips you up, the automation glossary is there.

Subscribe to the newsletter

New features, guides and offers — a few emails a month.

Related posts