WhatsApp Message Templates: Approval, Types, and Best Practices
Why templates are required
WhatsApp distinguishes between two types of messages: session messages and template messages. A session message is a free-form reply sent within 24 hours of the customer's last message — no template needed. A template message is any message you initiate outside that window, or any message sent in bulk through a campaign or automation. For template messages, every word must be pre-approved by Meta before you can send it.
This is not optional. Businesses that try to send unsolicited free-form messages — or that abuse session windows to mass-message customers — face account restrictions and number bans. The template system exists to protect users from spam and to protect businesses from losing access to their messaging channel.
The three template categories
Marketing templates are for promotional content: announcing a new product, offering a discount, sharing a newsletter. They have a higher cost-per-message from Meta and are subject to stricter delivery controls in some markets. Recipients who haven't recently engaged may receive fewer marketing messages.
Utility templates are for transactional or operational messages: order confirmations, delivery updates, invoice reminders, appointment reminders. They have a lower cost-per-message and are prioritised for delivery because the content is genuinely useful to the recipient rather than promotional.
Authentication templates are specifically for sending verification codes and one-time passwords. The format is standardised — you cannot freely edit the body — and they include a built-in copy button for the code. They go through a separate, faster approval track.
Creating a template that gets approved
Meta reviews templates for compliance with their business messaging policy. Rejections happen most often for four reasons: the template looks like spam (generic promotional language, excessive capitalisation, vague call-to-action), it contains prohibited content (gambling, weapons, misleading claims), the variable fields contain unclear placeholders, or the template is in the wrong category.
Write templates in plain, professional language. Use specific variable fields — {{customer_name}} and {{invoice_amount}} — rather than generic {{text}}. Make the call-to-action explicit. If you receive a rejection, read the reason provided: Meta typically gives a specific policy clause, which makes the required fix clear.
Managing templates in Zervixo
In Zervixo, templates are created and submitted from the Communication Hub module. Once approved, they appear in the template library and become available for selection in campaigns and automations. If a template is rejected, the rejection reason appears in the status column. Templates can be duplicated and modified — a common approach when a small wording change is needed for an existing approved template.
Variable field mapping
Template variables pull data from the matching customer or record at the time of sending. In Zervixo, you define which system field maps to each variable when setting up the template. For a utility template used in an invoice reminder automation, {{invoice_number}} maps to the invoice reference field, {{amount}} maps to the balance due, and {{due_date}} maps to the due date. The mapping is set once and applies every time the template is used — you don't re-map variables for each send.
Want to run your business more efficiently?
Try Zervixo free for 14 days — no credit card required.
Start your free trial