WhatsApp Message Templates: Categories, Approval and Examples

A WhatsApp message template is a pre-written, Meta-approved message format required for any business-initiated message sent outside a live 24-hour customer conversation. Templates fall into three categories — Marketing, Utility and Authentication — each with its own approval bar, and every template must clear Meta's review before it can send. This guide covers the categories, the anatomy of a template, the approval process, real example bodies, and how to write templates that get approved fast and keep performing.

Why WhatsApp requires templates at all#

WhatsApp's entire messaging model is built around consent. The moment a customer messages your business number first, a 24-hour customer service window opens, and inside that window you can reply with anything — free-form text, images, PDFs, whatever the conversation needs. The problem templates solve is what happens outside that window: if you want to reach a customer who hasn't messaged you recently, or start a conversation with someone who's never messaged you at all, free-form text isn't allowed. You have to use a message template that Meta has reviewed and approved in advance.

This isn't bureaucracy for its own sake. It's the mechanism that keeps WhatsApp usable as a platform. Without it, any business could type arbitrary text and blast it to any phone number the moment it got API access — which is exactly the spam pattern that made SMS and email inboxes unpleasant. By forcing outbound-initiated messages through a review process, Meta can catch scammy phrasing, missing opt-outs and misleading content before it ever reaches a phone, and it can hold businesses accountable afterward through the quality-rating system covered later in this guide.

For the deeper mechanics of the 24-hour window, conversation-based pricing and API architecture, see the pillar guide on the WhatsApp Business API. This article focuses specifically on templates: what they are, the three categories, how approval works, and how to write ones that get through review quickly.

It helps to think of templates as sitting at the intersection of two different goals that would otherwise pull against each other. Businesses want to reach customers reliably, at scale, whenever something needs saying — a shipment moved, a sale started, a code needs verifying. Customers want their inbox to stay predictable, free of the arbitrary cold-outreach that made older channels exhausting. Templates are the compromise: businesses get a durable, repeatable way to reach people outside a live chat, and customers get the guarantee that whatever lands in that message was checked against a consistent policy first, not typed and fired off on a whim. Once you see the system through that lens, most of the specific rules — categories, opt-out footers, variable formatting — stop looking arbitrary and start looking like the natural consequence of that one trade-off.

It's also worth being clear about what a template isn't. It isn't a one-time application you file and forget, and it isn't a loophole around the 24-hour rule that lets you send anything as long as it's "pre-approved" once. Every send of an approved template still counts as reaching outside a live conversation, still contributes to your messaging limits and quality signals, and can still be paused if the pattern of sends looks unhealthy. Approval clears the content for use — it doesn't insulate the template, or your number, from how real recipients respond to it afterward.

The three template categories, in depth#

Every template you submit gets classified into exactly one of three categories. The category isn't a label you can quietly ignore — it determines what content is allowed, how strictly Meta reviews it, and in many BSP billing models, how the message is priced. Getting the category right, and being honest about it, is the single highest-leverage decision you make when writing a template.

Marketing#

Marketing templates cover promotions, discounts, new-product announcements, sales events, newsletters and re-engagement nudges to lapsed customers. This is the broadest category — almost anything designed to sell, upsell or win back a customer lands here — and it's also the one Meta scrutinizes hardest, because it's the category most likely to be abused for spam. Marketing templates generally require a clear way to opt out, and vague, hype-heavy phrasing ("LIMITED TIME!!! ACT NOW!!!") is a common rejection trigger.

Utility#

Utility templates cover transactional, service-related updates tied to something the customer already did or is expecting — an order confirmation, a shipping update, a payment receipt, an appointment reminder, an account alert, a subscription renewal notice. The defining test is: did the customer take an action, or is something already in motion, that this message is following up on? If yes, it's Utility. If you're trying to get them to take a new action they weren't already expecting — buy something, renew early, check out a new feature — that's Marketing wearing a Utility costume, and Meta's reviewers are trained to catch it.

Authentication#

Authentication templates are reserved strictly for one-time passcodes (OTPs) and login/verification codes. This category has the tightest, simplest format Meta enforces on purpose: typically just a code and a short, standardized surrounding phrase, with restrictions on adding marketing language, links or extra buttons beyond a copy-code button. The narrowness is a security feature — it keeps OTP messages instantly recognizable and hard to spoof or dress up with phishing content.

A useful way to sanity-check your own category choice is to ask who benefits from the message existing at all. A Marketing template exists because you want the customer to do something new — buy, renew, come back. A Utility template exists because the customer is already mid-transaction with you and simply needs to know what's happening next. An Authentication template exists purely so the customer can prove they're the one logging in. If you can't cleanly answer "which of these three is this message actually for," that's usually a sign the copy itself needs tightening before you submit it, not just the category dropdown.

Anatomy of a template: header, body, footer, buttons, variables#

A template isn't a single block of text — it's assembled from optional and required components, and understanding each one is what lets you design messages that feel complete rather than bare.

• Header (optional). A short line of text, or media — image, video or document. A shipping-update template might use an image of the package; an invoice template might attach a PDF document header. Headers can also carry one variable (e.g. an order number in the header text).
• Body (required). The main message content. This is where most of your variables live — numbered placeholders like {{1}}, {{2}}, {{3}} — that get replaced with real data (a name, an amount, a date) at send time. Body text can't start or end with a variable; there needs to be surrounding text so Meta — and the recipient — can tell what the variable will contain.
• Footer (optional). A short, secondary line, commonly used for a brand tagline or, critically for Marketing templates, opt-out language like "Reply STOP to unsubscribe."
• Buttons (optional, up to a limit). Quick-reply buttons (fixed responses like "Yes" / "No" / "Talk to agent"), call-to-action buttons (open a URL, dial a phone number), or a button that opens a WhatsApp Flow for structured in-chat forms. A copy-code button is standard on Authentication templates.
• Variables. Numbered placeholders inserted via {{1}}, {{2}} syntax, mapped at send time to real values — typically pulled straight from your CRM record for that contact (name, order ID, due date, amount).

Buttons deserve their own closer look, since the button type you attach changes what the template can do once it's live. A quick-reply button returns a fixed, predictable response — useful when you want to route a "Confirm" or "Reschedule" tap straight into an automation or your shared inbox without the customer having to type anything. A call-to-action URL button opens a link, ideal for driving traffic to a product page, a tracking link, or a payment page, and can itself carry a dynamic per-customer suffix. A phone-number button lets the recipient tap to call you directly, which is a small but real conversion lever on appointment and service templates. And a Flow button launches a WhatsApp Flow — a structured, multi-step form that opens inside the chat itself, which is worth reaching for whenever you need to collect several fields (like a booking form or a feedback survey) rather than a single tap. Each template is limited in how many buttons it can carry and in mixing button types, so pick the one button behavior the message actually needs rather than stacking on every option available.

Template naming and language also matter more than they first appear to. Each template has an internal name (lowercase, underscores, no spaces — order_shipped_update rather than "Order Shipped Update") that's for your own organization and doesn't appear to the customer, plus a specified language/locale, since the same logical message often needs separate approved versions for, say, English and Hindi. If your customer base is genuinely multilingual, budget for that upfront: a Marketing template written only in English will read as an English-only business to a segment that would have engaged far better in their preferred language, and each language variant goes through its own review.

app.sabnode.com

The submission and review process#

Submitting a template is a structured form, not a blank text box — you fill in the category, the language, the components, and Meta's automated and human review checks it against policy before it goes live.

Once approved, the template's status and history are visible in Meta Business Manager / WhatsApp Manager under your business account. A BSP platform like SabNode WaChat mirrors that same status — pending, approved, rejected — inside a friendlier interface, so you're not context-switching to Meta's own tools just to check whether a template cleared review.

How to submit a template that gets approved fast#

Most rejections are avoidable. Follow this sequence and you'll clear review on the first attempt far more often than not.

1. Pick the honest category first. Before writing a word of copy, decide: is this genuinely tied to an action the customer already took (Utility), is it trying to sell or re-engage (Marketing), or is it strictly an OTP (Authentication)? Writing the message before choosing the category is how Utility-disguised-as-Marketing slips in by accident.
2. Write body copy that reads naturally with variables filled in. Draft the sentence with real sample values first ("Hi Priya, your order #4821 has shipped"), then swap in {{1}} and {{2}}. This guarantees the surrounding text gives every variable context, which is exactly what reviewers check for.
3. Never open or close the body with a bare variable. Start and end with real words. "{{1}}, thanks for your order" is riskier than "Hi {{1}}, thanks for your order" — the second gives the placeholder a clear frame.
4. Add the opt-out footer on every Marketing template. A line like "Reply STOP to unsubscribe" isn't optional politeness — it's one of the most commonly checked elements on promotional content, and its absence is a frequent rejection reason.
5. Keep Authentication templates minimal. Stick to the code and a short security phrase, add the copy-code button, and resist the urge to add branding, links or extra buttons — the category exists precisely because simplicity is the point.
6. Avoid spammy formatting. Excess capitalization, exclamation marks, and "FREE!!!" style phrasing read as low-quality regardless of category and can slow or sink a Marketing submission.
7. Use header media that matches the message. An image header on an order-shipped Utility template (a package photo) or a document header for an invoice reads as purposeful; generic stock imagery unrelated to the content doesn't help and can look like padding.
8. Test with sample data before submitting at scale. Preview the rendered template with a couple of real records so you catch awkward variable placement or missing fallback values before it's a live, approved template you have to resubmit to fix.
9. Build a small library ahead of need. Get your recurring Utility templates (order updates, reminders, receipts) and a rotating set of Marketing templates approved in advance, so a Friday-afternoon campaign idea doesn't stall on a pending review.

Quality rating: what happens after approval#

Approval is a starting line, not a finish line. Once a template goes live, WhatsApp tracks how real recipients react to it — blocks, reports, low engagement versus reads and replies — and rolls that into an ongoing quality rating, shown roughly as green (healthy), yellow (declining) or red (poor). This rating sits at both the template level and the phone number level, and it can move in either direction as sending continues.

A template that starts green can slide to yellow or red if it's sent to an audience that didn't expect it, if copy goes stale and stops resonating, or if it's overused past the point of relevance. When a template's rating drops far enough, it can be paused automatically, even though it was approved and performing fine last month. This is exactly why "get it approved" can't be the end of your process — you need to watch how each template performs over time the same way you'd watch any other marketing asset.

It's worth separating two related but distinct things a business ends up watching: the quality rating of an individual template, and the broader quality rating of the phone number sending it. A single weak template dragging down its own rating is a contained problem — retire or rewrite that one message. But if several templates underperform at once, or one high-volume template goes sideways, the effect can bleed into the number-level rating that governs your overall messaging tier and reach. That's the scenario worth catching early: review template-level performance regularly enough that a single bad send never has the chance to compound into a number-level problem.

The practical response to a declining template is the same discipline that keeps a broadcast healthy in general: retire or rewrite content that's underperforming, keep your audience targeting tight so the message stays relevant to whoever actually receives it, and don't lean on one aging Marketing template past the point it's still earning reads. For the deeper playbook on targeting, opt-in and campaign cadence that keeps quality ratings healthy at scale, see the guide on WhatsApp broadcast campaigns.

Common mistakes#

• Writing a Marketing message and calling it Utility. The single most frequent rejection cause. If the content is trying to sell or re-engage rather than follow up on an existing action, it's Marketing — label it that way from the start.
• Forgetting the opt-out footer on promotional content. Marketing templates without a clear "Reply STOP" or equivalent line are far more likely to get bounced, and even if approved, they erode the trust that protects your whole account.
• Over-using variables with no surrounding text. A body that's mostly bare placeholders strung together gives reviewers nothing to evaluate and often comes back for clarification.
• Ignoring quality rating after approval. Treating "approved" as permanent is how a previously-fine template gets quietly paused — check performance regularly, not just at submission time.
• Bloating Authentication templates with extras. Adding marketing language, links or unrelated buttons to an OTP template works against the category's whole purpose and can trigger rejection.
• Skipping the sample-data test. Submitting — or worse, sending at scale — without previewing rendered variables is how blank names and misaligned fields end up in front of real customers.
• Editing a live template's wording without resubmitting. Content changes need to go back through review; you can't quietly swap copy on an approved, sending template.
• Building one generic template and reusing it everywhere. A single Marketing template stretched across every offer stops feeling relevant fast — and relevance is exactly what quality rating measures.
• Treating every language the same. Submitting one English-only version of a template for a customer base that reads Hindi, Tamil or another regional language leaves engagement on the table and misses a review step you'll need to do eventually anyway — do it upfront, per language.
• Not distinguishing template-level from number-level quality. A team that only watches its overall number rating can miss that one specific template has quietly turned red and is actively dragging the average down.

Conclusion#

WhatsApp message templates exist to keep outbound business messaging structured, reviewable and consented — the trade-off for reaching customers outside a live 24-hour conversation is that Meta checks what you're sending first. Once you internalize the three categories, build templates with honest, well-labeled content, and give every variable clear context, approval stops being a mystery and becomes a routine part of shipping a campaign.

The work doesn't end at "Approved," though. Quality rating is a live, ongoing signal, and the businesses that keep reaching customers reliably are the ones that watch how templates perform after they go live, retire what's stopped working, and keep Marketing, Utility and Authentication content honestly separated. Get that discipline right once and it compounds across every future campaign.

If you're setting up templates for the first time, start with the fundamentals in the WhatsApp Business API guide, then move on to putting approved templates to work in a real send with the broadcast campaigns guide. Or explore pricing and get your first templates live on SabNode today.