Template categories, and why templates get rejected

A message template is the only way to reach someone on WhatsApp once their conversation window has closed. You write the format in advance, Meta reviews it, and afterwards you send it with the variables filled in.

Two things about that process cause most of the pain. The first is that the category is decided by Meta rather than by you, and it governs both what the template may contain and what each send costs. The second is that rejections are usually mechanical rather than editorial, so they are fixable once you know what the reviewer is checking.

The three categories

Utility is where most businesses want their templates to sit, because those messages are cheaper and are treated as part of a service conversation rather than as outbound marketing. The category is not a setting you choose to get that treatment. It is a description of what the message actually is, and Meta reads the words.

Category is decided at review, and can be revised

You submit a template with a proposed category. The reviewer either agrees, or reclassifies it. Reclassification is the quiet one: the template is approved, sending works, and the cost per message is higher than you planned. Nothing breaks, so nobody investigates.

The way to catch it is to read the billing category off the delivery receipt rather than off your own submission. Meta reports the category it applied when the message is delivered, and that value is the one you will be invoiced on. A platform that surfaces it per message turns a category question into a number you can look at.

The most common cause of reclassification is a single sentence. An order-shipped template that ends with "and here is 10% off your next order" is a marketing template with tracking information attached. Split it into two templates and the transactional one goes back to the utility rate.

Authentication is a special case

Meta constrains authentication templates tightly. They are meant to carry a code and nothing else, they generally use a fixed body form with a button that copies or autofills the code, and content that strays outside that pattern is rejected rather than reclassified.

If you are sending a passcode, use the authentication category and accept the constraints. If you are sending anything else, do not label it authentication because the rate looks attractive.

Why templates get rejected

Rejections are frustrating mainly because the stated reason is often terse. Most fall into a small number of causes.

Missing or unhelpful example values

Every variable in a template needs a sample value supplied at submission time. The reviewer uses those samples to understand what the message will actually say when it is sent. A template submitted with empty examples, or with examples that repeat the placeholder, gives the reviewer nothing to review and is rejected.

Supply realistic examples. {{1}} with the example Priya and {{2}} with A-4471 tells the reviewer this is an order update for a named customer. The same template with examples text and text tells them nothing.

A variable doing too much work

A body that is mostly placeholder is the classic pattern of a template built to send arbitrary content, which is exactly what the review process exists to prevent. A message that reads Hi {{1}}, {{2}} will be rejected regardless of what you intend to put in the second slot.

Related: templates that open or close on a variable, or place two variables next to each other, are frequently flagged because the reviewer cannot tell what the surrounding sentence will be. Write real sentences and let variables fill in the facts.

Promotional content submitted as utility

Covered above, and worth repeating because it is the single most common category error. A discount code, an upsell, an invitation to browse, or a line about a sale makes the template marketing. So does re-engagement copy of the "we miss you" variety, even without an offer.

Content that reads as spam

Excessive capitals, strings of emoji, urgency stacking, and vague claims all attract rejection. So do links that hide their destination behind a shortener, which reviewers cannot verify and recipients cannot trust.

Restricted or misleading subject matter

Meta's commerce and business messaging policies rule out several categories of goods and several kinds of claim outright. If your product sits near one of those lines, read the policy before writing the template rather than after the third rejection.

Duplicates and near-duplicates

Submitting the same template several times with tiny wording changes, or maintaining twenty variations of one notification, invites rejection and makes quality impossible to track. A small, well-named set of templates is easier to get approved and much easier to diagnose later.

Approved is not permanent

A template that passed review can be paused afterwards. That happens on the basis of how recipients react to it: blocks and reports on messages using a specific template feed a per-template quality signal, and a template that keeps attracting them stops being sendable.

This is worth internalising, because it changes what a template is. It is not a form you fill in once. It is an asset with a reputation, and the reputation is set by who you send it to as much as by what it says. The same approved template will hold its quality when sent to people who asked to hear from you and lose it when sent to a purchased list.

At send time, failures in the 132000 range mean the template itself is the problem: paused, no longer approved, or sent with variables that do not match the approved placeholders. None of those are worth retrying. Fix the template or the mapping, then send again.

Writing a template that passes the first time

• Name yourself. A recipient should be able to tell who is messaging from the first line. Reviewers check this and so do customers.
• Say the specific thing. "Your order A-4471 shipped this morning and should arrive Thursday" reads as a real notification. "Your order has an update" reads as a hook.
• Keep the categories separate. If a message has a transactional half and a promotional half, it is two templates.
• Fill in every example. With realistic values, in the format the variable will actually carry.
• Give the buttons an honest destination. A full URL to your own domain, not a shortener, and a label that matches what the page is.
• Write the language you selected. A template submitted as English with a body in another language is rejected, and mixed-language bodies confuse both the reviewer and the recipient.

After approval, track quality per template

Once several templates are live, the useful question stops being "was it approved" and becomes "which of these is costing us reputation". Both blocks and reports attach to the specific template that prompted them, so a per-template view tells you which message to rewrite or retire.

The template that gets the most complaints is rarely the worst written one. It is usually the one sent to the widest, least engaged audience. That is a targeting fix, not a copy fix, and reading the numbers per template is what makes the difference visible.