How to Write WhatsApp Business Message Templates That Get Approved (and Actually Convert)
Write WhatsApp Business message templates that pass review and drive replies. Practical guide to categories, variables, rejection reasons, and handling responses.
Most teams discover WhatsApp message templates the hard way: they try to send a broadcast, hit a wall, submit a template in a hurry, watch it get rejected, and then scramble to figure out why.
This guide skips the scramble. It covers what templates actually are, how categories work, what gets copy rejected, how to write variables cleanly, and — the part that determines whether a template actually converts — what you do when someone replies.
What Templates Are and When You Need Them
WhatsApp Business Platform has two distinct messaging modes.
Session messaging is free-form. Once a customer sends your business a message, you have a 24-hour window to reply however you like — conversational text, media, links, follow-up questions. No template required.
Template messaging (also called HSMs, Highly Structured Messages) is required any time you initiate contact with someone outside an active 24-hour session. This covers:
- Broadcast campaigns to opted-in lists
- Re-engagement after a conversation has gone quiet
- Transactional notifications (order updates, appointment reminders, OTP)
- Proactive outreach for any reason
Templates must be submitted to WhatsApp and approved before you can use them. Approval happens per template, not per sending number. Once approved, you can reuse a template for any number of recipients — but you cannot change its content without resubmitting.
The category you assign and the copy you write determine whether it gets through.
The Three Template Categories
WhatsApp organises templates into three categories. Getting the category wrong is one of the most common submission mistakes.
Marketing — Any message whose primary purpose is promoting a product, service, or offer. Discounts, new launches, event invitations, re-engagement nudges, and anything that drives a purchase intent. If the core point of the message is "here is something you should buy or look at," it is marketing.
Utility — Messages tied to an existing transaction or relationship. Order confirmations, shipping updates, appointment reminders, account alerts, service status notifications. The defining quality: the recipient is expecting this information because they already did something.
Authentication — One-time passwords and verification codes only. WhatsApp has a specific template structure for these and they are reviewed separately.
Misclassifying is a direct path to rejection. A discount announcement submitted as Utility will be rejected. An OTP submitted as Marketing will be rejected. WhatsApp reviewers check whether your content matches the declared category.
Billing also differs by category, so correct classification matters beyond just approval.
Why Templates Get Rejected
WhatsApp's review looks at both policy compliance and category accuracy. Common rejection reasons:
Content that resembles spam or feels coercive. Phrases like "Act now before it's too late," excessive capitalisation, multiple exclamation points, and countdown urgency language are patterns associated with low-quality bulk messaging. Reviewers flag them.
Vague or generic copy. A template like "Hi {{1}}, we have an exciting offer for you. Click here!" does not pass review because it is too ambiguous to evaluate. WhatsApp requires the message to be clear about what the business is offering and why the recipient is receiving it.
Misleading or inflated claims. Any absolute claim — "guaranteed," "100% results," "best price in India" — that cannot be substantiated tends to get flagged. Superlatives in marketing copy are a common sticking point.
Missing opt-out signal for marketing templates. For marketing messages, your flow should give recipients a way to stop receiving messages. This does not need to be in every template line, but your end-to-end opt-out mechanism matters to the overall policy review.
Wrong category. Already covered, but worth repeating: reviewers check this explicitly.
Prohibited content categories. WhatsApp's commerce policy prohibits certain content types outright — content that violates local laws, certain financial products depending on region, adult content, weapons, and others. These result in immediate rejection regardless of how the copy is written.
Writing Variables That Actually Work
Template variables are placeholders —
{{1}}{{2}}Every variable needs to be fully parseable from context. If a reviewer sees
{{1}}Do not use variables to smuggle in content that would fail on its own. Some teams try to put the entire promotional claim inside a variable so the template looks clean on review but delivers spam at send time. WhatsApp reviewers are aware of this pattern.
Limit variable count to what you actually need. A template with eight variables is harder to review and harder to fill correctly at send time. If your template needs that many placeholders, it is usually a sign the message is trying to do too much.
Headers and footers have their own variable limits. A template can have a header (text, image, video, or document), a body, a footer, and buttons. Variables are allowed in the body and header text, not the footer.
Writing Copy That Converts Inside the Rules
Approval is necessary but not sufficient. A template that passes review and generates no replies is not useful.
The best-performing WhatsApp marketing templates share a few characteristics:
They are specific about why the recipient is receiving the message. "Hi {{1}}, you visited our store last month" lands better than "Hi {{1}}, we thought you'd like this." Specificity signals relevance, and relevance drives replies.
They have one clear action. Whether it is "reply YES to confirm," "tap the button to view your booking," or "let us know your preferred time" — one ask, not three. Templates that end with multiple options get lower engagement.
They sound like a person wrote them. The WhatsApp channel is intimate. Copy that reads like a bulk email subject line is jarring. First person ("We noticed..."), conversational contractions, and a specific sender identity help.
Buttons are worth using when they fit. WhatsApp supports call-to-action buttons (visit URL, call number) and quick reply buttons in templates. A well-labelled quick reply ("Yes, confirm" / "Not now") can double reply rates compared to asking people to type a response. Keep button labels short and unambiguous.
What Happens When the Template Lands
This is where most template guides stop, and it is exactly where execution falls apart.
A good template generates replies. Those replies open 24-hour session windows with individual recipients. Inside those windows you can have real, free-form conversations — answer questions, close sales, handle objections, book appointments.
If those replies go unread, or pile up in a single WhatsApp number that one person checks manually, the campaign's conversion potential is wasted. Recipients who replied and heard nothing back are likely to block the number, which damages your sending quality rating.
Managing template replies at any real scale — multiple campaigns, different intents, different teams — requires a shared inbox that routes incoming messages by context. Bow Chat is built for exactly this: when a broadcast template goes out, replies come into a shared queue where they can be assigned to the right agent before they stack up.
You can also set up automated responses for the first few seconds after a reply arrives — acknowledging receipt, asking a clarifying question, or routing to the right team based on keyword — so no one sits waiting for a human to notice they replied.
The template is the door. What you do with the people who walk through it determines whether the campaign was worth running. Bow Chat handles both sides: helping teams manage their approved templates and owning the conversations those templates start.
A Practical Template Submission Checklist
Before writing
- I know which category this belongs in: Marketing, Utility, or Authentication
- The content is permitted under WhatsApp's commerce policy
- I have sample values ready for every variable
Copy
- The message is specific about who is receiving it and why
- There is one clear action or ask
- No superlatives, countdown urgency, or all-caps emphasis
- Variables make sense in context and are not hiding content that would fail review
Category check
- If Utility: there is a clear prior transaction this message relates to
- If Marketing: opt-out path exists in our broader flow
Operations
- We have a plan for routing replies before the template is approved and sent
- Someone is assigned to reply ownership, not just send ownership
The Short Version
Template approval is about accuracy: accurate category, clear copy, honest variables, no policy violations. Conversion is about specificity and follow-through: a message that gives the recipient a real reason to reply, and a team that is ready when they do.
Neither is complicated. Both require a bit more discipline than most teams apply to their first submission.
Get the template right, then get the reply right. That is the whole playbook.