WhatsApp message template approval: how to write one that isn't rejected

Working with the WhatsApp Business API, sooner or later you hit this wall: you want to send a customer a proactive message, but it stalls as "pending template approval" or, worse, "rejected." Because outside the 24-hour window you can only message on WhatsApp with pre-approved templates. A rejected template stops an entire campaign.

The good news: approval isn't luck, it's a learnable skill. This guide explains what a template is, its categories, why it gets rejected, how to write one that gets approved, and what to do when it's rejected — with examples.

What is a WhatsApp message template?

A message template is a reusable message format that WhatsApp has pre-approved. If a customer hasn't written to you in the last 24 hours, you can only reach them with one of these approved templates. The rule exists to protect users from unwanted messages; it also underpins bulk messaging and automated flows. Templates can include variables (like {{1}}) for personalization, so a single approved template goes out to thousands, customized with details like a name and order number.

We covered the API itself and the 24-hour rule in our WhatsApp Business API guide.

Template categories: marketing, utility and authentication

Every template is assigned a category, and the right category is half the approval:

• Utility: Notifications tied to a transaction — order confirmation, shipping status, appointment reminder, invoice. Usually lower cost and easier to approve.
• Marketing: Promotional messages like campaigns, discounts, new products, win-backs. More tightly reviewed and must go only to opted-in people.
• Authentication: One-time passwords (OTP) and login codes. Standardized in structure and subject to clear rules.

Trying to pass a marketing message off as "utility" is the most common mistake and the fastest to be penalized; WhatsApp notices and either rejects or re-categorizes it.

The parts of a template

A template has several parts, each with its own rules:

• Header: Optional; a short text or an image/document/video.
• Body: The main message. Variables are used here.
• Footer: Optional, a small note (e.g. "Reply STOP to opt out").
• Buttons: Quick-reply or action (website link, call) buttons.

HeaderHi {{1}},your order {{2}} hasshipped. Track: {{3}}FooterTrackHelp

How do you use variables (placeholders)?

Variables are how you personalize a single template to thousands of people, written as {{1}}, {{2}}. Mind a few rules to get approved:

• Provide sample values: You must supply a sample ("Alex", "12345") for each variable at submission; templates without samples are rejected.
• No adjacent variables: You can't put two variables side by side like {{1}} {{2}}; place text between them.
• Don't open/close with a lone variable: Starting or ending the body with only a variable is usually rejected.
• Don't overdo it: Templates that are almost entirely variables, with unclear meaning, won't be approved.

Why does a template get rejected? The most common reasons

A rejection usually comes from one of these:

• Wrong category: Trying to send marketing content in the "utility" category.
• Missing sample values: No examples provided for variables.
• Vague or meaningless text: Templates with no real content, like just "Hi {{1}}".
• Prohibited content: Region-dependent banned topics and policy violations.
• Formatting errors: Broken variable numbering, excessive emoji/caps, bad links.
• Aggressive sales language: All caps, over-promising and a spammy tone.

How to write a template that gets approved: the golden rules

The principles that minimize rejection are clear:

• Match the category: Choose the category the content actually is.
• Be concrete: The message should carry clear information or a clear benefit, not be vague.
• Use variables correctly: Provide sample values, avoid adjacent variables.
• Write cleanly: Grammar, punctuation and reasonable length; be measured with emoji and caps.
• Offer an exit in marketing: An easy opt-out in promotional messages aids both compliance and trust.

Good and bad template examples

Let's make the abstract rules concrete.

Bad (rejected): "HI {{1}} 🔥🔥 DON'T MISS!!! TAP NOW {{2}}" — all caps, over-hyped, vague, and a body ending on a variable.

Good (utility): "Hi {{1}}, your order {{2}} has shipped. Use the button below to track it." — clear, personal, a real notification.

Good (marketing): "Hi {{1}}, the {{2}} you looked at last month is 15% off this week. Reply to reserve one. Reply STOP if you'd rather not get messages." — personal, valuable, opted-in and offering an exit.

Using buttons and headers

Buttons both improve the experience and raise your approval odds, because they guide the user to a clear action. There are two kinds: quick-reply (e.g. "Yes/No", "Confirm appointment") and action buttons (open website, call). If you use an image in the header, make sure it's relevant and appropriate to the message; unrelated or misleading images get rejected.

What to do if a template is rejected

A rejection isn't an end, it's feedback. First read the reason — a short rationale is usually given. Most rejections are fixed in a few minutes: correct the category, add sample values, cut caps and emoji, add context to the body. Resubmit after fixing. If you believe a rejection is unfair you can appeal; but in most cases clarifying the text is the fastest path.

Template quality rating and pausing

Approval isn't the end of the process. An approved template also has a quality rating that changes based on how users react to it. A template that's frequently blocked or reported is first flagged "low quality" and, if it continues, paused (temporarily unsendable). So even after approval you need to watch delivery, read and complaint signals and update any template that performs poorly.

A checklist to speed up approval

• Does the content truly match the category you chose (utility/marketing/authentication)?
• Did you add a sample value for every variable?
• Does the body carry clear information or a benefit, not vague meaning?
• Any adjacent variables, excessive emoji or all-caps? (There shouldn't be.)
• If it's marketing, did you add an easy opt-out?

How many templates can I create?

The number of templates a business can create isn't unlimited; there's a cap tied to your account and approval tier. So rather than opening a separate template for every small variation, it's smart to design flexible, reusable templates with variables. A single "order status" template, for example, can cover dozens of scenarios by carrying the status in a variable. A few well-designed templates make both management and approval tracking easier than many scattered ones.

Multilingual templates: one message, three languages

If your customers speak different languages, you can create the same template separately for each language and pick the right version by the person's language at send time. This matters especially for businesses serving a multilingual audience — say Turkish, English and Russian: when a customer gets the message in their own language, both opens and conversion rise noticeably. Each language version goes through its own approval, so the translations must also be clear, correct and aligned with the category.

Starter templates to copy

Rather than starting from scratch, beginning with a few proven patterns improves your approval odds. Common starter templates that usually approve smoothly are: order confirmation ("Your order is received, number {{1}}"), shipping notification, appointment reminder, payment/invoice info, and feedback request. The healthiest start is to adapt these utility-focused patterns to your brand's voice and design marketing templates separately, aimed at an opted-in audience.

Template management with Rocketly

With Rocketly you create your templates in one place, submit them for approval, and track their status (approved, pending, rejected). You connect approved templates to your automated flows and chatbot scenarios and see send results in a single inbox. That way your campaigns flow compliantly and measurably, without hitting the "rejected" wall.