How to write WhatsApp message templates that get approved (and convert) 

If you’re newer to WhatsApp marketing, you’ve probably heard of message templates but may not be totally sure what they are or how they work.

They’re a core part of WhatsApp marketing, and if you want to send outbound messages, you need message templates that fit Meta’s rules, fall into the right category, and pass review. That can feel confusing at first, especially if you’re used to the flexibility of email or SMS.

This guide breaks down what WhatsApp templates are and shares best practices for writing templates that are more likely to get approved and drive action.

And if you use Customer.io, you can create, edit, and submit WhatsApp templates for Meta approval directly in the platform, via our native WhatsApp offering.

A WhatsApp message template is a pre-approved message format businesses use for business-initiated messages on WhatsApp. Before you can send those messages, your template has to be submitted for review and approved by Meta.

How templates work:

• Create a template with placeholders where you’d want to personalize or add unique information like: “Hi {{1}}, your order {{2}} has shipped"
• Submit it for approval
• Once approved, use it in your WhatsApp campaigns

There are three template categories:

• Utility: Transactional or account-related updates tied to a user action, like order confirmations, shipping notifications, or appointment reminders
• Authentication: One-time passcodes, login verification, and account security messages
• Marketing: Promotional or re-engagement content, including offers, product announcements, and abandoned cart reminders

Please note, though, that as of April 1, 2025, WhatsApp marketing template messages to U.S. phone numbers are blocked.

Your message needs to fit the right category, or it is more likely to be rejected or reclassified. Learn more about general WhatsApp best practices here.

Businesses generally create and manage these templates in Meta's Facebook Business Manager, then sync them into their marketing automation platform to send. However, when using Customer.io’s native WhatsApp offering, you can manage the entire process, from creation to approval and sending, without switching out of Customer.io.

The most common reason templates are rejected is a mismatch between their content and their declared category. Before you write anything, be clear on which of the three categories applies—because they are not interchangeable.

Utility templates

These templates are for transactional updates tied to a customer action. Order confirmed. Appointment reminder. Shipping notification. The rule here is strict: no promotional language whatsoever. If Meta's reviewers spot anything that looks promotional, your Utility template becomes a Marketing template— nd if you filed it as Utility, it will likely be rejected.

Authentication templates

These templates are for security and verification only. OTPs, 2FA codes, and login verification. These are the most tightly scoped categories and rarely cause confusion.

Marketing templates

These templates are for everything promotional—sales, discount codes, abandoned cart nudges, and re-engagement. These have the most creative flexibility, but come with a constraint: as of April 2025, Marketing templates cannot be sent to US-based WhatsApp recipients.

One more nuance worth knowing: mixed-content templates are automatically classified as Marketing, even if you file them as Utility. An order update that includes a promo code? Marketing. A feedback survey with a discount incentive? Marketing. When in doubt, file as Marketing rather than risk rejection.

You cannot use a template until it has been approved. That means you should not wait until launch day to write a template. Even though many approvals happen quickly, a manual review or a rejection can still delay your send. A practical best practice is to submit templates in advance so you have time to revise and resubmit if needed.

A few realities to keep in mind:

• Some templates are approved in minutes
• Templates that require human review can take up to 48 hours
• If you edit a template’s content, you generally need to resubmit it
• A rejected template needs to go back through review after you fix it

Also, approval is not necessarily permanent. Approved templates can later be paused or disabled if they receive repeated negative feedback or run into policy issues.

WhatsApp template rules are strict, and small formatting mistakes can lead to rejection. Before you submit, make sure you’ve covered the basics.

Variables must use numbered placeholders. WhatsApp templates use numbered variables like {{1}}, {{2}}, and {{3}}. Start at {{1}} and number them consecutively. Skipping numbers can cause problems during review.

Include sample values for every variable. If your template contains placeholders, provide representative sample values when you submit it for review. This helps reviewers understand the intended message.

Template names are lowercase only. Template names use lowercase letters, numbers, and underscores. Avoid spaces, capitals, and special characters.

Use one language per template. Each WhatsApp template is created for a single language, so if you want to support multiple languages, you need separate templates.

Watch your variable placement. Some template systems automatically reject templates that begin or end with placeholders in problematic ways, so it is best to keep variables grounded in clear surrounding text.

Proofread before submitting. Clear, polished copy improves your chances of approval and makes the final message feel more trustworthy.

WhatsApp templates are not just one block of text. They can include distinct components that help you add structure and make the message easier to act on.

Header (optional): A header appears above the body and can help set context quickly. Depending on the template type, headers can include text and, in some flows, richer media options.

Body (required): This is the main message and the only required content area.

Footer (optional): A short piece of supporting text that appears below the body.

Buttons (optional): WhatsApp supports two main button types:

• Call-to-action buttons, such as opening a URL or placing a phone call
• Quick reply buttons, which let recipients tap a preset response instead of typing one.

Not every template needs every component. A simple appointment reminder may only need body copy and one clear CTA. A promotional template may benefit from a stronger visual hierarchy and a more obvious next step.

WhatsApp sits next to messages from friends, family, and close contacts. That context should shape how you write.

Be brief. Mobile messages work best when they get to the point quickly.

Be specific. “Your order has shipped” feels much more relevant than “We have an update for you.”

Use personalization where it adds clarity. A name, appointment time, or order number can make the message more useful without making it feel forced.

Include a clear next step. The reader should know exactly what to do next: track the package, confirm the appointment, redeem the offer, or reply.

Treat opt-out handling seriously for marketing messages. Even when the exact wording and implementation depend on your provider setup, giving recipients a clear path to stop marketing messages is good practice for trust, compliance, and long-term list health.

Appointment reminder (Utility template)

Template title: appointment_reminder_pet

Company name: Pamper Palace

Hello {{1}},

Just a friendly reminder that {{2}}’s {{3}} appointment is scheduled for tomorrow at {{4}}. We’re excited to pamper your pet at {{5}}! If you need to reschedule or update your appointment, please give us a call at (123)-456-7890 (tel:1234567890). See you soon!

Pamper Palace

Variables

• {{1}} = Customer name
• {{2}} = Pet's name
• {{3}} = Service
• {{4}} = Appointment time
• {{5}} = Company name

Why it works: it is specific, transactional, and tied to a known customer action, which fits Utility use cases well.

Seasonal offer (Marketing template)

Company name: Green Haircare

Template title: green_haircare_marketing_promo

Hello {{1}},

Enjoy {{2}}% off on all haircare products for a limited time! Use code {{3}} at checkout to save on your favorites. Offer valid until {{4}}, don’t miss out! Reply STOP to opt out.

Variables

• {{1}} = Customer name
• {{2}} = Discount percentage
• {{3}} = Discount code
• {{4}} = Expiration date

Why it works: the purpose is obvious, the CTA is clear, and the promotional nature makes it a good fit for Marketing. Just remember that marketing template messages cannot be sent to U.S. phone numbers.

Rejections happen. A rejection does not mean WhatsApp is not a fit for your program. It usually means the template needs a clearer category, cleaner formatting, or more context.

Common reasons templates get rejected include:

• Category mismatch
• Promotional content inside a Utility template
• Variable formatting problems
• Unclear or overly vague message purpose
• Policy or quality issues detected during review

When a template is rejected:

1. Read the rejection reason carefully.
2. Fix the specific issue instead of rewriting blindly.
3. Resubmit the template.
4. Expect the review process to start again.

Here’s something that surprises many new WhatsApp marketers: you don’t always need a template.

When a customer messages your business first, a user-initiated conversation opens. During that session, businesses can send different kinds of replies than they can in a business-initiated conversation.

In practice, that means:

1. If your business is starting the conversation, you usually need an approved template.
2. If the customer starts the conversation, your reply options are broader during that active conversation window.

One Customer.io-specific note: We do not currently support sending free-form messages or two-way conversations at this time.

Learn more about the 24-hour rule here.

Historically, creating a WhatsApp message often meant jumping between tools to build it, submit it, and then use it in a campaign.

But, not anymore! If you are using our native WhatsApp offering, Customer.io lets you build, edit, and submit WhatsApp message templates for Meta approval directly inside the platform—in the same place where you build all of your other campaigns, manage your segments, and track performance. Approval status is visible in-product, so you always know where your WhatsApp message templates stand.

This means marketers can spend less time managing handoffs and more time focusing on message quality, timing, and performance.

Ready to see it in action? Book a demo →

What is a WhatsApp message template?

A WhatsApp message template is a pre-approved message format businesses use for business-initiated messages on WhatsApp.

When do you need a WhatsApp message template?

You typically need one when your business is initiating contact or sending outside an active user-initiated conversation flow.

What are the three WhatsApp template categories?

Utility, Authentication, and Marketing.

Why do WhatsApp templates get rejected?

Common reasons include category mismatch, unclear purpose, bad variable formatting, and policy or quality issues found during review.

How long does WhatsApp template approval take?

Many templates are approved within minutes, but templates that require human review can take up to 48 hours.

How do variables work in WhatsApp templates?

Templates use numbered placeholders like {{1}}, {{2}}, and {{3}}, and sample values should be included for review when variables are present.

Can you edit an approved WhatsApp template?

If you change the content, you generally need to resubmit it for approval.

Can you send marketing messages on WhatsApp?

Yes, through approved Marketing templates, but WhatsApp marketing template messages to U.S. phone numbers have been blocked since April 1, 2025.

What makes a good WhatsApp template?

A good template is clear, brief, category-appropriate, easy to understand, and focused on one obvious next step.

Can you create WhatsApp templates inside Customer.io?

Yes. Customer.io supports creating and submitting WhatsApp templates in-platform if sending natively.