WhatsApp message templates: approval, categories, and best practices

WhatsApp message templates are pre-approved messages that businesses use to start a conversation or message a customer outside the 24-hour window. Because WhatsApp does not let businesses send free-form messages to people who have not recently messaged them, templates are the approved way to reach out first.

If you have ever received an order confirmation or an appointment reminder on WhatsApp, you have seen a template in action. The business did not type that message by hand to each customer. They created a WhatsApp message template, got it approved once, and now send it with the customer's details filled into the variable slots.

Templates matter because they sit at the center of WhatsApp's rules. Inside an open conversation you can reply freely. To open a conversation, or to follow up after the window closes, you need an approved template. Understanding that split is the whole game.

WhatsApp sorts message templates into three categories, and the category you pick shapes both approval and cost. The three are utility, marketing, and authentication.

Utility templates relate to a specific transaction or request the customer already made: order updates, delivery notifications, appointment reminders, payment confirmations. They are expected and low-friction because the customer is waiting for them.

Marketing templates promote something: a new product, an offer, a re-engagement nudge, a seasonal campaign. They face the strictest review because they are the most likely to feel like spam. They also require the customer to have opted in.

Authentication templates deliver one-time passcodes and login verification. They are tightly scoped to that single purpose and should not carry any marketing content. Picking the honest category for your message is the first step toward a clean approval.

Template approval works by sending each template to Meta for review, where it is usually approved or rejected within minutes to a day. You submit the template text, its category, and any variables, and you cannot send it to customers until it clears.

Review checks a few things: that the category matches the content, that the message is not misleading, and that variables are used properly rather than as a way to smuggle in free-form spam. Approval is per template, so a small wording change can mean resubmitting.

Once approved, a template stays usable until you edit it or until Meta flags a quality problem from how customers respond. Templates that get blocked or reported a lot can be paused, so the goal is not just to pass review, it is to write messages people are glad to receive.

WhatsApp templates get rejected most often for vague content, a mismatched category, or placeholder abuse. The good news is that almost every rejection reason is fixable on the second try.

The frequent culprits are templates that are too generic to tell what they do ("Hi {{1}}, check this out"), marketing dressed up as utility to dodge the stricter review, and variables stacked so heavily that the approved text could mean anything once filled in. Broken formatting, like mismatched variable numbers, also trips review.

To fix a rejection, make the purpose obvious in the static text, label the category honestly, and keep variables to the specific data they hold (a name, an order number, a date). A template a human reviewer can read and immediately understand is a template that gets approved.

The best practice for WhatsApp message templates is to write each one as if a real customer and a strict reviewer will both read it, because both will. Clear purpose, honest category, and minimal variables carry you most of the way.

A few rules that hold up well in practice:

Keep the static text specific enough to stand on its own, so the message reads cleanly even before the variables are filled in. Match the category to the actual intent rather than the category with the loosest rules. Use variables only for true per-customer data, not to hide changing promotional copy. Give marketing templates a clear opt-out path, and only send them to contacts who opted in.

Write for the person, not the algorithm. Templates that read like a helpful note from a business the customer chose to hear from are the ones that keep your quality rating healthy over time.

You need a template whenever you are starting the conversation, or replying after the 24-hour window has closed. Inside that window, after the customer messages you, you can reply with normal free-form text and no template at all.

The window is the dividing line. When a customer sends you a message, a 24-hour service window opens, and during it your team can answer naturally. Once 24 hours pass with no new customer message, the window closes, and reaching them again requires an approved template.

This is why templates and your inbox work together. Day-to-day support happens in free-form replies inside open windows. Proactive outreach, reminders, and re-engagement happen through templates. A team that understands which mode it is in avoids both broken sends and accidental rule violations.

In a team setting, templates work best when they live in one shared place instead of scattered across individual phones. If every agent keeps their own copy, you get drift: slightly different wording, untracked edits, and no single source of truth.

This is part of what a shared workspace solves. In Clapvo, message templates sit alongside the shared inbox and the campaigns feature, so the whole team draws from the same approved set. An agent picking a template for a reply is using the same vetted message a manager approved, not a personal variant.

That shared library also speeds up campaigns. When you send a scheduled or bulk message, you are sending an approved template to an opted-in list, with the customer details filled in per recipient. Keeping templates, contacts, and the inbox in one surface is what turns template rules from a chore into a routine.