WhatsApp coexistence templates: when you need them and why they fail

A WhatsApp template (Meta calls it a message template) is a pre-approved message format your business uses to start a conversation through the Cloud API outside the 24 hour window. With WhatsApp coexistence, you need one in exactly one situation: when the API has to reach a customer who has not written in the last 24 hours. Your team replying from the phone never uses templates, and inside the window the API can reply with free-form text. Every template has a category (marketing, utility or authentication), goes through Meta's review, and is billed according to Meta's public rate card.

Below: when to use them, how to build one that clears review on the first try, and what usually gets rejected.

When a template is required, and when it is not

Coexistence puts the same number in two places: the WhatsApp Business app on the phone and the Cloud API. Each side follows its own rules.

The 24 hour window opens and restarts only when the customer messages you. Business replies do not count, whether they come from the API or the phone. For the full rule with an hour-by-hour example, read the WhatsApp 24 hour window with coexistence.

In practice, almost any automation that fires after a delay has to be a template: day-before appointment reminders, "your order shipped" notices, a satisfaction survey a few days later, a nudge on a quote that went cold. By the time those fire, the window has usually closed.

The three categories, in plain terms

Meta sorts templates by what the message is for. Broadly:

Marketing. Anything that promotes: sales, launches, invitations, coupons, win-back messages, "we have something new for you." If the message is trying to sell or spark interest, treat it as marketing.

Utility. Messages tied to something the customer did or asked for: order confirmations, delivery updates, a reminder for an appointment they booked, a heads-up about a change to their account. Utility informs about an existing transaction or request; it does not push a new product.

Authentication. One-time passcodes and login codes. Fixed format, single purpose.

The category is not paperwork. It sets the price of the message and affects approval. Meta charges per message using a public rate card that varies by country and by category, and the rates change from time to time, so check Meta's current rate card before you build a budget. For the full cost picture, see WhatsApp coexistence pricing.

Anatomy of a template

Every template has the same parts:

• an internal name only you see
• a language, which must match the copy
• a category, one of the three above
• a body, the message text, with numbered variables where each customer's details go (first name, date, order number)
• header, footer and buttons, all optional

Variables are what make a template reusable: one reminder template serves every customer by swapping in name, date and time. When you submit it for review, you provide a sample value for each variable, and that sample is how the reviewer understands what the message will actually say.

Getting it approved

Once submitted, the template goes into Meta's review and comes back approved or rejected. Turnaround varies, so do not plan a send for the same hour you create the template. Build templates ahead of time and schedule sends only once the status says approved.

A rejection is not a penalty. You adjust the copy and resubmit. What hurts is finding out about a rejection on the morning the automation was supposed to run.

A working order that avoids surprises:

1. List every message your automation will send outside the window.
2. Write each one as a template with the right category.
3. Submit them all together, days before you need them.
4. Turn on the automation only after every template it uses is approved.
5. Keep an alternate version of the copy ready for anything rejected, and resubmit the same day.

What gets templates rejected

Wrong category. A promotion filed as utility is the textbook case. "Your order has shipped. Take 15% off your next purchase!" mixes both. Split it into two templates, or accept that it is marketing.

Variables with no sample or no context. A body that is mostly variables, or a variable dangling at the very start or end of the message, leaves the reviewer guessing. Write the full sentence and place variables inside copy that makes sense on its own.

Vague copy. "Hi, we have an update for you" says nothing about who is sending or why. A good template says who the business is, what it is about and what the person can do next.

Language mismatch. A template declared as English with chunks of Spanish is a common reason for rejection. One language per template; if you serve customers in both, create one version for each.

Content outside Meta's policies. Products and offers that Meta's commerce policies do not allow will not get through, no matter how well written.

Pre-submission checklist

• The category describes what the message is really for, not what looks cheapest
• The copy says who is sending and why, even with variables left blank
• Every variable has a realistic sample value
• No variable sits alone at the start or end of the message
• One language only, matching the one declared
• There is a real reason the customer would want this message
• The template was created days ahead, not on send day

Templates and number quality

With coexistence, your number has a single quality rating. Blocks and reports against a template sent through the API weigh on the same number your team uses on the phone. An approved template is not a safe template: approval means the copy follows the rules; the people receiving it decide whether it hurts your number.

The pattern that tanks quality is messaging people who did not ask to hear from you: purchased lists, old databases with no recent contact, customers who never opted in. And there is a temptation specific to coexistence: using the phone to dodge templates by manually pasting the same message to dozens of contacts. Replacing broadcasts with manual mass sending is precisely what Meta penalizes, and the consequences hit the whole number. The post on WhatsApp number quality covers the early warning signs.

One upside people miss: a template sent through the API also shows up in the conversation on the phone. Your rep sees exactly what the automation sent and can take it from there when the customer replies. And that reply reopens the 24 hour window, so the API can continue with free-form text.

Where to start

Start with two or three utility templates for things customers already expect: a booking confirmation, a reminder, a status update. They are the easiest to get approved and the least risky for your number. Marketing templates come later, for an audience that asked to hear from you.

If your number is not connected yet, check the WhatsApp coexistence requirements and the module page at WhatsApp Coexistence. A Vazante account starts with 7 days for US$2.99 at sign up.