Why templates exist

Outside an open conversation, you cannot send a customer whatever you like. You send a template — a message format Meta approved in advance.

The reason is protection. Without it, WhatsApp becomes a marketing channel, people leave, and the platform loses its value. The rules exist to keep the channel worth being on.

The practical consequence: every proactive message you send has to be designed, submitted and approved before it can be used once.

What a template looks like

Fixed text, with variables in defined places.

Something like: Hi {{1}}, your order {{2}} has been dispatched and should arrive by {{3}}.

At send time you supply the three values. Everything else is unchangeable without resubmitting.

Optional parts:

A header. Text, an image, or a document.

A footer. Small text at the bottom.

Buttons. A link, a phone number, or quick reply options.

Buttons are worth using. A “Track order” button gets far more engagement than the same URL in the body text.

Categories

Every template is submitted in a category, and the category affects what is allowed and what you pay.

Utility. Information about something the customer already did. Order confirmations, delivery updates, appointment reminders, payment receipts.

Marketing. Promotions, offers, re-engagement, anything selling. More restricted and more expensive.

Authentication. One-time passcodes only.

Choosing wrongly is the most common rejection reason. A message that mentions a discount is marketing, however you categorise it. Meta reads the content, not your label.

Why templates get rejected

Six reasons, in rough order of frequency.

Promotional content in a utility category. The big one. Any offer, discount or upsell makes it marketing.

Unclear variables. A template that is mostly variables — “{{1}} {{2}} {{3}}” — gets rejected because Meta cannot tell what will actually be sent.

Missing context. A message that does not say who it is from or why the person is receiving it.

Policy-restricted content. Certain industries and product types have additional restrictions.

Poor formatting. Excessive capitals, too many emoji, spam-like presentation.

Placeholder text left in. Submitting with “Insert company name here” still in the body.

Read the rejection reason. Meta gives one, and it usually tells you exactly what to change.

Writing one that gets approved

Six rules.

Say who you are. “Hi Priya, this is Acme Supplies.” Not everyone saves business numbers.

State the purpose in the first line. What this message is about.

Use variables for data, not for meaning. A name, a number, a date. Not whole sentences — that reads as an attempt to send arbitrary content.

Give surrounding context. Enough fixed text that Meta can see what a real send looks like.

No promotional language in utility. No “special offer”, no “limited time”, no discount mentions.

Keep it short. This is a messaging app.

Design them to last

Editing a template means resubmitting it. So design for change.

Put anything that might vary into a variable. If your delivery window might change from “3 days” to “5 days”, make it a variable rather than fixed text.

Do not hard-code prices, dates or terms. Those change, and each change is a resubmission.

Do not create one template per product. A generic order confirmation with the product as a variable covers everything. Twenty near-identical templates is twenty things to maintain.

A useful test: if this changed slightly, would I need a new template? If yes, make that part a variable now.

How many you need

Fewer than people expect.

A typical order flow: confirmation, dispatched, out for delivery, delivered. Four templates, covering every product and customer.

Plus: appointment reminder, payment reminder, document delivery. Seven or eight total for most businesses.

If you are designing thirty, something is wrong. Look for variables you could be using instead.

The approval process

Submit through your provider’s interface.

Timing varies. Often quick — minutes to hours. Sometimes longer, particularly for marketing templates or during busy periods.

Rejections come with a reason. Read it, fix that specific thing, resubmit.

Plan for at least one rejection on your first batch. It is normal and it is not a sign of a problem.

Submit early. Do not leave templates until the week before launch — it is a common cause of delayed go-lives.

Managing them over time

Keep a written list. What each template is for, its category, when it was approved, and who owns it.

Review yearly. Some will be for processes you stopped using.

Watch performance. Templates with low read rates or high blocks are telling you something.

Delete what you do not use. Fewer templates, less to maintain.

What to do about promotional messaging

An honest position.

You can send marketing templates. They are allowed, they cost more, and they carry more risk to your quality rating.

If you do:

Only to people who opted in for marketing specifically. Not people who opted in for order updates.

Rarely. Once a month is a lot on this channel.

Genuinely relevant. Based on what they bought, not a broadcast.

With an obvious opt-out.

Many businesses are better off not doing this at all, and keeping WhatsApp as a utility channel that customers trust. The order updates work partly because they are not surrounded by promotion.

The short version

Templates are how you message customers outside an open conversation, and they need approval before first use.

Category is the main rejection cause. Promotional wording in a utility template gets rejected.

Design few templates with good variables, rather than many specific ones — every edit is a resubmission.

Submit early, expect one rejection, and keep a list of what exists and who owns it.