
WhatsApp Template Categories and Approval, Explained
Marketing, Utility and Authentication templates explained: what each is for, how Meta reviews them, common rejection reasons and a checklist before you submit.
- Social Agent team
- 7 min read

In this article
If you use the WhatsApp Business API, message templates are unavoidable. Any message your business starts, and any message you send after a customer has gone quiet for more than 24 hours, has to use a template that Meta has reviewed and approved. The category you choose affects what you may say, how Meta reviews it and what you pay. This guide explains the three template categories, how the customer service window works, how to build templates that pass review first time and what to check before you submit.
Meta updates its template rules and pricing regularly. Everything below reflects the position at the time of writing, and Meta's WhatsApp Business Platform documentation is the authoritative source.
Templates and the 24-hour customer service window
Two kinds of messages exist on the WhatsApp Business Platform:
- Free-form messages: any text, media or interactive message you like. You can only send these while a customer service window is open.
- Template messages: pre-approved message formats with placeholders for personal details. You can send these at any time, provided the recipient has opted in.
A customer service window opens when a customer messages you and stays open for 24 hours from their most recent message. Every new message from the customer restarts the clock. Inside that window your team, or your automation, can reply freely. Once it closes, you need a template to restart the conversation.
This is why templates matter to support and operations teams, not only marketers: a next-day order update or an appointment reminder will usually fall outside the window.
The three template categories
At the time of writing, Meta offers three categories: Marketing, Utility and Authentication.
| Category | Purpose | Typical examples | Key restrictions |
|---|---|---|---|
| Marketing | Promotion, awareness, re-engagement and anything that does not fit the other two | Sales, new products, event invitations, abandoned cart nudges, newsletters | Recipient must opt in; subject to per-user marketing limits |
| Utility | A specific, agreed transaction or account matter the customer triggered or requested | Order confirmations, delivery updates, payment receipts, appointment reminders, account alerts | Must be non-promotional and relate to an existing transaction or account |
| Authentication | One-time passcodes for verifying identity | Login codes, account recovery, transaction verification | Fixed preset wording from Meta, code delivery buttons, no URLs, media or emojis |
Marketing
Marketing is the catch-all: promotion, offers and re-engagement all belong here. Meta also treats mixed content as marketing: an order confirmation that ends with "Use code SAVE10 on your next purchase" becomes a Marketing template.
Utility
Utility templates must relate to a specific transaction or account event the customer triggered or agreed to. "Your order 4521 has shipped" passes. "We noticed you have not ordered in a while" does not, however neutral the wording.
Authentication
Authentication templates deliver one-time passcodes. Meta supplies the body text, so you do not write it yourself. You choose options such as a security disclaimer and code expiry note, and add a button for the code: copy code, one-tap autofill or, on Android, zero-tap. You cannot add promotional content, links or media.
How Meta categorises and can re-categorise
When you submit a template you choose a category, but Meta makes the final decision. At the time of writing, Meta reviews templates against its category guidelines and may assign a different category if the content does not match your choice. Meta can also review templates after approval and change their category if it finds they are being used in a way that does not match, notifying you when this happens.
Two practical consequences follow:
- Write for the category you want. Keep Utility templates strictly transactional.
- Watch for category changes. A template that moves from Utility to Marketing will be charged at the Marketing rate and becomes subject to marketing delivery limits. Monitor notifications in WhatsApp Manager or through webhooks.
Pricing basics
Meta moved the WhatsApp Business Platform to per-message pricing in July 2025. At the time of writing, you are charged for each delivered template message, with the rate depending on the template category and the recipient's country. Some combinations are not charged, for example Utility templates sent while a customer service window is already open, and free-form replies inside the window are not charged either.
Rates differ by market and change periodically, so we will not quote numbers here. Check Meta's current rate card on the WhatsApp Business Platform pricing pages, and if you use a Business Solution Provider, confirm whether they add a markup. Our guide to choosing a WhatsApp Business API provider covers the different cost models.
Building a template: components, variables and samples
A template is made up of up to four parts.
Header (optional)
- Text: a short title, which can include one variable.
- Media: an image, video or document. Media headers are powerful for marketing and for sending documents such as invoices. You provide a sample file at submission and the actual file at send time.
- Location: for sharing a place, such as a store or collection point.
Body (required)
The main message, with a character limit set by Meta (currently 1,024 characters). This is where most variables live.
Footer (optional)
A short line of plain text without variables. It is a good place for an opt-out line such as "Reply STOP to unsubscribe".
Buttons (optional)
- Quick reply: tappable replies such as "Confirm", "Reschedule" or "Stop promotions". A tap opens a customer service window.
- Call to action: a URL button (static or with a variable suffix) or a phone number button.
- Copy code: for coupon codes in Marketing templates.
- Flows: launch a WhatsApp Flow, such as a short form.
Meta limits the number and mix of buttons per template, so check current limits first.
Variables and samples
Variables are placeholders such as {{1}} or named parameters such as {{first_name}}. For every variable you must supply a realistic sample value when you submit. Reviewers use the samples to understand what the final message will look like, so "John" and "Order 4521" are far better than "test" or "xxx".
Rules that catch people out:
- A body should not start or end with a variable.
- Avoid placing variables directly next to each other with nothing between them.
- Do not write a template that is mostly variables. Reviewers need enough fixed text to judge the purpose.
- Number positional variables in sequence without gaps.
Common rejection reasons
Most rejections come down to a handful of issues:
- Wrong category: promotional wording in a Utility template, or anything other than a passcode in Authentication.
- Variable formatting: variables at the start or end, adjacent variables, missing or unrealistic samples, or incorrect numbering.
- Unclear purpose: a body so generic ("Hi {{1}}, {{2}}") that the reviewer cannot tell what will be sent.
- Policy violations: content that breaches Meta's Commerce Policy or Business Messaging Policy, such as restricted goods or services.
- Requests for sensitive information: asking customers to send full card numbers, identity numbers or passwords in the chat.
- Threatening or abusive tone: aggressive debt collection wording is a frequent problem.
- Suspicious links: URLs that obscure the destination, or links that do not match your business.
- Duplicates: a template with the same wording as one you already have.
If you believe a rejection is wrong, you can request a review through WhatsApp Manager, though fixing the wording and resubmitting is often faster. Approved templates can also be paused or disabled if recipients block or report them heavily, so monitor each template's quality rating.
Managing templates at scale
Once you have dozens of templates across several languages, management becomes the real challenge. Use a naming convention (lowercase with underscores, such as order_shipped_v2), give every template an owner, add an internal review before Meta sees it, create a new template for significant changes rather than editing one that automations depend on, and prune templates you no longer use.
In Social Agent, templates are drafted, reviewed internally and submitted to Meta from one place, with status changes and category updates tracked in the audit trail. The same templates are then available to broadcasts and to drag-and-drop workflows, so an order update or reminder uses exactly the approved wording.
Pre-submission checklist
- The category matches the content, with no promotional wording in Utility.
- The template name is descriptive, lowercase and uses underscores.
- The language is set correctly, with separate templates for each language.
- The body neither starts nor ends with a variable, and no variables are adjacent.
- Every variable has a realistic sample value.
- Media headers have a representative sample file.
- Button text is short and clear, and URLs point to your own domain.
- Marketing templates include an opt-out option.
- The message does not ask for passwords, full card numbers or identity numbers.
- A colleague has reviewed the wording before submission.
- You have checked the current rules in Meta's WhatsApp Business Platform documentation.
Key takeaways
- Templates are required for any business-initiated message and for anything sent after the 24-hour customer service window closes.
- Marketing covers promotion and re-engagement, Utility covers specific transactions and account events, Authentication covers one-time passcodes only.
- Meta decides the final category and can re-categorise templates, which changes cost and delivery.
- Pricing is per delivered template message by category and country at the time of writing; always check Meta's current rate card.
- Realistic samples, correct variables and an internal review prevent most rejections.


