Outside an open conversation, you cannot send a customer whatever you like. You send a template<\/strong> \u2014 a message format Meta approved in advance.<\/p>\n The reason is protection.<\/strong> 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.<\/p>\n The practical consequence:<\/strong> every proactive message you send has to be designed, submitted and approved before it can be used once.<\/p>\n Fixed text<\/strong>, with variables<\/strong> in defined places.<\/p>\n Something like: Hi {{1}}, your order {{2}} has been dispatched and should arrive by {{3}}.<\/em><\/p>\n At send time you supply the three values. Everything else is unchangeable<\/strong> without resubmitting.<\/p>\n Optional parts:<\/strong><\/p>\n A header.<\/strong> Text, an image, or a document.<\/p>\n A footer.<\/strong> Small text at the bottom.<\/p>\n Buttons.<\/strong> A link, a phone number, or quick reply options.<\/p>\n Buttons are worth using.<\/strong> A “Track order” button gets far more engagement than the same URL in the body text.<\/p>\n Every template is submitted in a category, and the category affects what is allowed and what you pay.<\/p>\n Utility.<\/strong> Information about something the customer already did. Order confirmations, delivery updates, appointment reminders, payment receipts.<\/p>\n Marketing.<\/strong> Promotions, offers, re-engagement, anything selling. More restricted and more expensive.<\/p>\n Authentication.<\/strong> One-time passcodes only.<\/p>\n Choosing wrongly is the most common rejection reason.<\/strong> A message that mentions a discount is marketing, however you categorise it. Meta reads the content, not your label.<\/p>\n FIGURE 1: THE THREE CATEGORIES<\/p>\n Utility<\/p>\n Marketing<\/p>\n Authentication<\/p>\n Six reasons, in rough order of frequency.<\/p>\n Promotional content in a utility category.<\/strong> The big one. Any offer, discount or upsell makes it marketing.<\/p>\n Unclear variables.<\/strong> A template that is mostly variables \u2014 “{{1}} {{2}} {{3}}”<\/em> \u2014 gets rejected because Meta cannot tell what will actually be sent.<\/p>\n Missing context.<\/strong> A message that does not say who it is from or why the person is receiving it.<\/p>\n Policy-restricted content.<\/strong> Certain industries and product types have additional restrictions.<\/p>\n Poor formatting.<\/strong> Excessive capitals, too many emoji, spam-like presentation.<\/p>\n Placeholder text left in.<\/strong> Submitting with “Insert company name here” still in the body.<\/p>\n Read the rejection reason.<\/strong> Meta gives one, and it usually tells you exactly what to change.<\/p>\n Six rules.<\/p>\n Say who you are.<\/strong> “Hi Priya, this is Acme Supplies.” Not everyone saves business numbers.<\/p>\n State the purpose in the first line.<\/strong> What this message is about.<\/p>\n Use variables for data, not for meaning.<\/strong> A name, a number, a date. Not whole sentences \u2014 that reads as an attempt to send arbitrary content.<\/p>\n Give surrounding context.<\/strong> Enough fixed text that Meta can see what a real send looks like.<\/p>\n No promotional language in utility.<\/strong> No “special offer”, no “limited time”, no discount mentions.<\/p>\n Keep it short.<\/strong> This is a messaging app.<\/p>\n FIGURE 2: WHAT GETS APPROVED AND WHAT DOES NOT<\/p>\n Approved<\/p>\n Rejected<\/p>\n Editing a template means resubmitting it.<\/strong> So design for change.<\/p>\n Put anything that might vary into a variable.<\/strong> If your delivery window might change from “3 days” to “5 days”, make it a variable rather than fixed text.<\/p>\n Do not hard-code prices, dates or terms.<\/strong> Those change, and each change is a resubmission.<\/p>\n Do not create one template per product.<\/strong> A generic order confirmation with the product as a variable covers everything. Twenty near-identical templates is twenty things to maintain.<\/p>\n A useful test:<\/strong> if this changed slightly, would I need a new template? If yes, make that part a variable now.<\/p>\n Fewer than people expect.<\/p>\n A typical order flow:<\/strong> confirmation, dispatched, out for delivery, delivered. Four templates, covering every product and customer.<\/p>\n Plus:<\/strong> appointment reminder, payment reminder, document delivery. Seven or eight total for most businesses.<\/p>\n If you are designing thirty<\/strong>, something is wrong. Look for variables you could be using instead.<\/p>\n Submit through your provider’s interface.<\/strong><\/p>\n Timing varies.<\/strong> Often quick \u2014 minutes to hours. Sometimes longer, particularly for marketing templates or during busy periods.<\/p>\n Rejections come with a reason.<\/strong> Read it, fix that specific thing, resubmit.<\/p>\n Plan for at least one rejection<\/strong> on your first batch. It is normal and it is not a sign of a problem.<\/p>\n Submit early.<\/strong> Do not leave templates until the week before launch \u2014 it is a common cause of delayed go-lives.<\/p>\n FIGURE 3: A SENSIBLE TEMPLATE PROCESS<\/p>\n Design few, with variables<\/p>\n Submit early<\/p>\n Read the rejection reason<\/p>\n Keep a list of what exists<\/p>\n Keep a written list.<\/strong> What each template is for, its category, when it was approved, and who owns it.<\/p>\n Review yearly.<\/strong> Some will be for processes you stopped using.<\/p>\n Watch performance.<\/strong> Templates with low read rates or high blocks are telling you something.<\/p>\n Delete what you do not use.<\/strong> Fewer templates, less to maintain.<\/p>\n An honest position.<\/p>\n You can send marketing templates.<\/strong> They are allowed, they cost more, and they carry more risk to your quality rating.<\/p>\n If you do:<\/strong><\/p>\n Only to people who opted in for marketing specifically.<\/strong> Not people who opted in for order updates.<\/p>\n Rarely.<\/strong> Once a month is a lot on this channel.<\/p>\n Genuinely relevant.<\/strong> Based on what they bought, not a broadcast.<\/p>\n With an obvious opt-out.<\/strong><\/p>\n Many businesses are better off not doing this at all<\/strong>, and keeping WhatsApp as a utility channel that customers trust. The order updates work partly because they are not surrounded by promotion.<\/p>\n Templates are how you message customers outside an open conversation, and they need approval before first use.<\/p>\n Category is the main rejection cause.<\/strong> Promotional wording in a utility template gets rejected.<\/p>\n Design few templates with good variables<\/strong>, rather than many specific ones \u2014 every edit is a resubmission.<\/p>\n Submit early, expect one rejection, and keep a list of what exists and who owns it.<\/p>\n Templates getting rejected or taking too long?<\/p>\n Get in touch. Most rejections come down to category and variable structure, and both are fixable in one pass.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" Why templates exist Outside an open conversation, you cannot send a customer whatever you like. You send a template \u2014 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 […]<\/p>\n","protected":false},"author":3,"featured_media":9396,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"class_list":["post-9395","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automation"],"yoast_head":"\nWhat a template looks like<\/h2>\n
Categories<\/h2>\n
\n
\n
\n
Why templates get rejected<\/h2>\n
Writing one that gets approved<\/h2>\n
\n
\n
Design them to last<\/h2>\n
How many you need<\/h2>\n
The approval process<\/h2>\n
\n
\n
\n
\n
Managing them over time<\/h2>\n
What to do about promotional messaging<\/h2>\n
The short version<\/h2>\n