A WhatsApp template strategy that survives contact with production

Every WhatsApp programme eventually hits the same 2am problem: something has gone wrong, you need to tell customers, and the message you want to send does not exist as an approved template. On the WhatsApp Business Platform, a business can only start a conversation — or write to someone more than 24 hours after their last message — with a pre-approved template. So the template set is not copywriting; it is the list of things you will ever be able to say first. Design it like that.

Templates are submitted to Meta, reviewed (often within minutes, sometimes longer) and filed under a category: marketing, utility or authentication. The category decides the price and how strictly the template is reviewed. Since 1 July 2025 the platform bills per message rather than per conversation, and Meta has changed what is free inside the 24-hour customer-service window more than once since then. The latest change took effect on 1 October 2026: free-form replies inside the window (service messages) are charged after 1,000 free per business phone number each month, with no rollover, and utility templates sent inside an open window, free since July 2025, are charged too. Messages in the 72-hour free entry point window after a click-to-WhatsApp ad or a Page button still carry no delivery charge. Treat the pricing page as the source of truth and re-read it each quarter; WhatsApp 101 summarises the rules as of October 2026. Meta also limits how many marketing templates one person receives from businesses overall, so a marketing send can fail even when everything on your side is approved.

Think of templates as a small API you are publishing to your future self. The question is not "what do I want to say today" but "what kinds of thing will I ever need to say first".

A workable starting set:

Each with enough variables to be reusable. Five well-parameterised templates beat forty specific ones and are far easier to keep approved.

Do not file marketing as utility. Reviews are content-based; Meta can move a template to the category it thinks fits and will notify you when it does. Repeated mis-filing damages the account's standing. The saving is small and the downside is the channel.

Model cost per outcome, not per message. A utility template that produces a resolved query is cheaper than a marketing template that produces nothing, whatever the unit prices say.

The single highest-value practice: keep an approved, generically worded incident template that you hope never to use.

Word it so it can carry any incident — what happened, what you are doing, where to look for updates — with variables for the specifics and a link. Approval is usually quick, but on the day you need it a rejection, a pause or a backlog is the difference between telling customers and not. The temptation is to write it specifically. Resist; a specific template has to be approved again for the next incident.

Templates drift. Someone edits copy, resubmits, and production now references a template whose meaning has changed.

Keep template definitions in version control next to the code that sends them, and treat an approval as a deployment. When a template changes, that is a new version, not an update — the old one sent real messages and you need a record of what they said.

The discipline is in the count rather than the craft. A programme with forty templates usually has a dozen that carry the traffic and many that nobody has retired.

Rejection is rarely about the words. It is about the gap between the category claimed and the message written.

• Marketing filed as utility — the most common cause.
• Variables that carry the whole message. A template whose only fixed text is "Hello {{1}}" is a way of avoiding review and is treated as one.
• No exit. A re-engagement template without a way to stop receiving them.
• Vague or misleading content, such as an unexplained link or a sender that does not match the business.

And one to avoid on your own account: a template that invites a reply you have no capacity to answer. If it asks a question, someone — or something — has to be ready.

A regional internet provider sets up WhatsApp for billing and support.

• Five templates in English and Arabic (ten records): payment received, plan changed, payment due in three days, service disruption (break-glass), and a quarterly upgrade offer (marketing).
• The disruption template reads, in effect: "We are aware of a problem affecting {{1}}. Our team is working on it. Updates: {{2}}." It was approved in week one and not used until a fibre cut in month five, when it went to affected customers within minutes.
• The upgrade offer was first submitted as utility, re-categorised to marketing by Meta, and kept there. Its cost was then compared with upgrades it produced, not with the utility price.

• Can I manage templates through your API and export them, with category, status and version history?
• Do you pass through Meta's category-change and quality notifications to me as webhooks?
• Do you add a margin to Meta's per-message prices, and is it per message or per conversation?
• How do you show a template send that failed because of Meta's per-user marketing limits?

Templates exist because of the 24-hour window. Next in this track: what RCS changed. For why the official platform matters, read the cost of an unofficial transport.