WhatsApp Message Templates: Rules and Examples

Message templates are one of the most important concepts to understand on the WhatsApp Business Platform, and also one of the most frequently misunderstood. They are the mechanism that lets a business reach out to a customer first, outside the back-and-forth of a live conversation, and because of that they sit under a specific set of rules designed to protect people from spam. If you have ever wondered why you cannot simply type a free-form message and blast it to your contacts, templates are the answer to that question.

This guide explains what templates are, when they are required, the rules they must follow to be approved, how Meta categorises them, and what well-written templates actually look like. The examples are written to be adapted rather than copied verbatim, so you can see the structure and reasoning behind a message that gets approved and performs well once it is live.

What a message template is and why it exists

A message template is a pre-approved message format that a business submits to Meta for review before it can be sent. Once approved, it can be used to start conversations or to send certain notifications to customers. The reason for the review is straightforward. WhatsApp is a personal space for most people, and the platform protects that by not letting businesses send unsolicited free-form messages whenever they like. Templates create a controlled path: the business says in advance exactly what kind of message it wants to send, Meta checks it against policy, and only then is it allowed out.

This is the key distinction that confuses newcomers. When a customer messages you first, a window opens during which you can reply freely with normal, unstructured messages. But if you want to reach out proactively, or if that window has closed, you generally need an approved template. Understanding this difference is the foundation for everything else, because it determines when you are free to write naturally and when you must work within an approved format.

The deeper logic is worth appreciating, because it changes how you feel about the rules. Templates are not an arbitrary hurdle invented to slow businesses down. They exist because the platform is fiercely protective of the customer experience, and a flood of unsolicited promotional messages would quickly drive people away from using WhatsApp to talk to businesses at all. By insisting that proactive outreach be pre-approved, the platform keeps the channel valuable for everyone, which ultimately benefits the businesses that use it responsibly. Seen that way, templates are a shared agreement to keep the space worth being in.

When templates are required

Templates come into play in two broad situations. The first is business-initiated contact, where you want to reach a customer who has not just messaged you. Order updates, appointment reminders, shipping notifications, and similar proactive outreach all fall here. The second is when a customer-initiated conversation window has closed and you need to re-engage. In both cases, free-form messaging is not available, so an approved template carries the message.

Inside an active customer-initiated conversation, by contrast, you usually do not need a template at all. The customer has reached out, a window is open, and you can respond conversationally. This is why a well-designed support flow often mixes both: templates to begin or re-open contact, and free-form replies during the live exchange. If you are designing automated journeys, our WhatsApp AI chatbot guide shows how these two modes fit together in a single experience.

Getting this distinction right in practice is one of the most valuable habits you can build. Many businesses waste effort trying to force template-style messaging into moments where a normal reply would do, or conversely attempt free-form outreach in situations that genuinely require a template and then wonder why their messages do not go through. A simple mental rule helps: if the customer just spoke to you and the window is open, write naturally; if you are reaching out first or re-opening a dormant thread, reach for an approved template. Internalising that rule removes most of the confusion that surrounds the whole topic.

The rules a template must follow

Templates are reviewed against WhatsApp's policies, and the review is real, not a formality. A template that reads like spam, makes misleading claims, or tries to circumvent the platform's intent will be rejected. The strongest templates share a few qualities. They are clear about who is sending and why. They deliver genuine value to the recipient rather than pushing unwanted promotion into a private space. They use variables, the placeholders that get filled in per recipient, in a way that is meaningful rather than as a trick to disguise generic blasts.

Formatting matters too. Templates can include a header, a body, a footer, and interactive buttons, and each part has its own expectations. Variables should be used responsibly, with content that genuinely changes per message such as a name, an order reference, or a date. Overloading a template with too many variables, or using them to smuggle in arbitrary marketing copy, raises flags. Grammar, spelling, and clarity all influence approval, because a sloppy template signals low effort and a higher spam risk.

Common reasons templates get rejected

Most rejections trace back to a small set of issues. Overly promotional content in a category meant for something else, vague or placeholder text left in by mistake, misuse of variables, and language that feels manipulative are frequent culprits. Templates that try to recreate a free-form marketing blast under the guise of a notification are particularly likely to be turned down. The fix is almost always to make the message more honest about its purpose, cleaner in its wording, and more clearly valuable to the person receiving it.

How templates are categorised

Meta groups templates into categories that reflect their purpose, and this categorisation matters because it ties directly into how conversations are priced and reviewed. At a high level, the platform distinguishes between utility-style messages that relate to a specific transaction or account, marketing messages that promote or re-engage, and authentication messages used for verification codes. Choosing the correct category for a template is important, because submitting a promotional message under a non-promotional category is a common reason for rejection or re-categorisation.

Because category influences pricing as well as approval, it is worth getting right from the start. Our companion article on WhatsApp pricing explains how conversation categories map to charges, which gives useful context for why you should not simply label everything as one type to save effort.

A practical consequence of categorisation is that you should design templates with their category in mind from the very first draft, rather than writing the message and choosing a category afterwards. If a message is fundamentally promotional, accept that it belongs in the marketing category and write it honestly as such. Trying to disguise promotion as a utility notification to gain some perceived advantage almost always backfires, either at review or through re-categorisation, and it erodes trust with the platform. Aligning intent and category from the outset keeps everything clean and predictable.

Examples you can adapt

The best way to internalise the rules is to look at the shape of a good template. Consider an order update. A clean version greets the customer by name, states the order reference, and tells them clearly what has changed, perhaps that the order has shipped, along with any relevant next step. The variables are the name and the order reference, both of which genuinely differ per recipient. There is no unrelated promotion, no vague filler, and no attempt to disguise the message as something it is not.

An appointment reminder follows the same logic. It identifies the customer, names the appointment and its time, and offers a clear way to confirm or reschedule. Again the variables are meaningful, the purpose is unambiguous, and the value to the recipient is obvious. A re-engagement marketing template is allowed too, but it must live honestly in the marketing category, be transparent that it is promotional, and respect that the recipient may not want it. The honesty is what keeps it compliant.

Writing variables well

Variables are where many templates go wrong. The principle is simple: a variable should hold information that genuinely changes from one recipient to the next and that the recipient would expect to see personalised. A first name, an order number, a delivery date, or an appointment time are all good uses. Stuffing a long block of marketing copy into a variable, or using variables to make one template act like many unrelated ones, defeats the review process and tends to be caught. Keep variables tight, purposeful, and predictable.

One more habit improves your templates immediately: read each finished template aloud as if you were the customer receiving it cold, with no context beyond the message itself. Does it make sense on its own? Is it obvious who sent it and why? Does the variable content slot in naturally, or does it read like an obvious mail-merge? Templates that survive being read aloud from the recipient's point of view tend to be the ones that both pass review and actually perform once they are live, because clarity for the reader and clarity for the reviewer are usually the same thing.

Building templates into a real workflow

Templates rarely live in isolation. In practice they are the entry points to broader customer journeys: a shipping notification that invites a reply, a reminder that lets someone reschedule, a promotional message that opens into a conversation. Designing these flows well means thinking about what happens after the template is delivered, because that is where the live, free-form portion of the conversation begins. If you run broadcasts, our guide to the WhatsApp broadcast process covers how to reach many people responsibly using approved templates.

It also helps to connect templates to your wider commerce setup. Order and shipping templates are far more useful when they are wired into your actual operations, and a thoughtful approach to conversational commerce turns those notifications into genuine touchpoints rather than one-way announcements. The goal is always the same: use the template to start a valuable interaction, then let the conversation carry it forward.

If you are still standing up your account, getting the underlying connection right comes first. Our walkthrough of WhatsApp Business API setup covers the prerequisites that make template submission possible, and from there the practice of writing and refining templates becomes a steady, learnable craft rather than a guessing game.

A practical mindset for templates

The most reliable way to get templates approved and to keep them performing is to write every one as if you were the person receiving it. Would this message feel useful or intrusive? Is it obvious who sent it and why? Does every variable earn its place? Templates that pass this internal test tend to pass Meta's review as well, because the policies are ultimately trying to protect the same experience you would want as a customer. Treating the rules as a guide to good messaging, rather than an obstacle, is what turns templates from a chore into an advantage.

Over time you will build a small library of dependable templates for the situations that recur in your business. Maintain them, keep their wording clean, and revisit their categories if your usage changes. A well-kept set of templates becomes part of the operational backbone of your messaging, quietly handling the proactive contact that keeps customers informed and engaged without ever crossing into spam.

Frequently asked questions

References

1. WhatsApp Business Platform, business.whatsapp.com
2. Meta for Developers, developers.facebook.com

Want help designing templates and flows that get approved and perform? Explore our WhatsApp AI chatbot or get in touch.