Rejected WhatsApp Templates: Causes, Tips and How to Fix Them

Why WhatsApp Templates Get Rejected by Meta

When you submit a WhatsApp Business API template for review, Meta examines it against a strict set of policies before granting approval. The process is largely automated and, in some cases, involves manual review as well. A rejection does not necessarily mean your content is inappropriate: it often comes down to small formal details or word choices that do not comply with the guidelines.

The most common causes of rejection involve overly aggressive promotional content in non-permitted contexts, incorrect use of variable parameters, ambiguous or misleading messages, and violations of industry-specific rules. Meta periodically updates its policies, so a template that was approved in the past may not pass review if resubmitted with minor changes.

Understanding why a template was rejected is the essential first step. The Meta Business Manager panel provides a rejection reason code, but it is often generic. This is why having a thorough understanding of the policies and applying the right practices from the creation stage is far more effective than trying to fix issues after the fact.

Meta Policies You Must Know Before Writing a Template

Meta draws a clear distinction between utility messages, authentication messages, and marketing messages. Each category has different rules regarding permitted content, frequency, and use cases. Sending a message with a promotional purpose inside a template classified as 'utility' is one of the most frequent causes of rejection, because Meta considers this practice misleading to the end user.

There are also specific industry restrictions to be aware of: financial products, pharmaceuticals, alcohol, gambling, adult products, and legal services require particular attention. In some cases you may need to provide additional documentation or comply with precise geographic restrictions. Before creating templates in these areas, it is essential to read Meta's updated Business Policies.

An often overlooked aspect concerns the tone of messages. Phrases with excessive urgency such as 'Act now or lose everything', unverifiable claims, or promises of easy earnings are interpreted as signals of spam or misleading content. Even the presence of links to unknown URLs or domains not associated with your verified business domain can cause immediate rejections.

• Always identify the correct category: utility, authentication, or marketing
• Avoid sensitive industries without adequate documentation
• Do not use artificial urgency or unverifiable claims
• Only use URLs from verified domains in your Meta account

Technical Errors in Templates: Variables and Formatting

WhatsApp templates support dynamic variables indicated with the syntax {{1}}, {{2}}, and so on. A very common mistake is creating templates with too many variables or with consecutive variables without any fixed text in between. Meta requires that each variable be preceded and followed by at least a few words of context: a template made up almost entirely of placeholders is rejected because it is impossible to assess the legitimacy of its content.

Text formatting is another critical point. Excessive use of asterisks for bold, capitalising every word, or using special characters and excessive emoji in the body text to grab attention can trigger automatic filters. The template must look like a professional business communication, not a flyer-style advertising message.

The structure of CTA buttons also requires attention. Buttons of type 'URL' must point to valid HTTPS addresses and the domain must be registered in the Meta account. 'Quick Reply' buttons must have clear, concise, and non-promotional labels. A button labelled 'CLICK NOW TO WIN' will almost certainly be rejected.

• Each variable must have textual context before and after it
• Limit the use of capitals, symbols, and emoji in the body text
• Links in buttons must be HTTPS and on verified domains
• Button labels must be clear and non-promotional

How to Rewrite a Rejected Template: Practical Tips

The first thing to do when you receive a rejection is to carefully analyse the reason code provided by Meta. Rejection categories include content issues, formatting issues, and specific policy violations. Once you have identified the cause, proceed with a targeted revision, avoiding changing the entire template: excessive changes can introduce new problems and make it harder to understand what worked.

If the issue concerns promotional content, rephrase the sentences from an informational perspective. Instead of 'Take advantage of our exclusive 50% discount today only!', try 'We have updated the terms of your offer. Check the details in your account.' The meaning can remain similar, but the tone changes dramatically and aligns much better with Meta's criteria for utility or notification templates.

For marketing templates, promotion is permitted but must still respect the boundaries. Avoid unsubstantiated superlatives, unrealistic promises, and aggressive time pressure. Focus on the concrete value for the user: what they get, how it works, what the next steps are. A clear, direct, and respectful message is far more likely to get approved and, equally important, to achieve a good response rate.

Ecommerce Templates: The Most Delicate Situations

Ecommerce businesses are among the heaviest users of WhatsApp Business API and also among those who most frequently encounter the problem of rejected templates. Typical online store communications such as order confirmations, shipping updates, and review requests generally fall into the utility category and have a high approval rate when built correctly.

The problem arises when promotional elements are inserted inside transactional messages. For example, adding a paragraph to an order confirmation that promotes a related product with a dedicated discount effectively turns a utility message into a marketing message, without having declared it as such. Meta detects this and rejects the template. The solution is to keep communications clearly separate: one template for the confirmation, a separate template for the promotion.

Another sensitive area for ecommerce concerns abandoned cart recovery templates. These messages are only permitted if the user has given explicit consent to receive marketing communications via WhatsApp (documented opt-in). The template itself must comply with marketing policies, so no excessive urgency and no unverifiable promises. Structure them as a helpful reminder, not as a spam email.

• Always separate transactional templates from marketing templates
• Do not add promotions inside order confirmation messages
• Document user opt-in for marketing messages
• Structure cart recovery as a reminder, not as pressure

The Role of Examples and Sample Content in Approval

When you submit a template for approval, Meta asks you to provide concrete examples for each variable in the message. This step is often overlooked or filled in with generic data such as '{{1}} = test' or '{{1}} = name'. This is a significant mistake: the examples are there to help Meta evaluate the actual content of the template in a plausible use context.

Providing realistic and relevant examples noticeably increases the likelihood of approval. If your template contains the variable {{1}} for the product name, insert an example such as 'Nike Air Max 270 Running Shoes'. If {{2}} represents a tracking link, use a real URL from your domain. The more the template filled in with examples resembles an authentic communication, the more Meta's automated reviewer considers it trustworthy.

The same principle applies to images or videos attached to templates with a media header. Use real images of your products or brand, not placeholder images or irrelevant generic stock photos. A visual header that is coherent with the message text conveys professionalism and reduces the risk of being flagged by Meta's automated systems.

How Many Times Can You Retry and How to Handle Repeated Blocks

Meta does not impose a strict limit on the number of attempts to get a template approved, but it does apply throttling mechanisms in cases of multiple consecutive rejections. If a template is rejected several times without significant changes, the review process may slow down or the template may be temporarily blocked. This is why it is essential to make substantial modifications to the template before each new submission.

If you have exhausted the obvious changes and the template continues to be rejected, consider contacting Meta Business support directly through the Business Help Center. In some cases, especially for businesses with verified accounts and a good track record, it is possible to request a manual review of the rejection. This option is not always available, but it is worth exploring before completely rewriting the template.

An important strategic tip: keep an internal log of all submitted templates, including the date, text, category, outcome, and rejection reason. This archive allows you to identify recurring patterns in rejections, adapt your writing process over time, and train team members responsible for managing WhatsApp communications. Historical memory is a valuable asset in this area.

• Do not resubmit identical templates without substantial changes
• Request manual review through the Business Help Center if necessary
• Keep an internal log of all templates and their outcomes
• Analyse rejection patterns to improve the creative process

Preventing Rejections: An Effective Internal Review Process

The best way to minimise rejected templates is to build an internal review process before submitting to Meta at all. This means creating a checklist based on the most recent Meta policies and using it systematically for anyone who drafts templates in your organisation. The checklist must include verifying the correct category, checking variables, reviewing the tone, and validating any URLs present.

Tools like Kuba Labs allow you to manage WhatsApp Business API templates in a structured way, with visibility into approval status and revision history. Having a centralised platform reduces errors caused by fragmented processes and allows you to iterate quickly on corrections. When the marketing team, the technical team, and customer service collaborate on the same platform, the quality of templates improves significantly.

Investing time in training is equally important. Meta's policies evolve and what was approved six months ago may not be approved today. Schedule regular update sessions for your team, monitor the official Meta for Developers changelogs, and consider working with a certified WhatsApp Business Solution Provider to get direct support in optimising templates and managing the approval process.

• Create an internal checklist based on updated Meta policies
• Use centralised platforms to manage templates and reviews
• Regularly train your team on Meta policy updates
• Consider support from a WhatsApp Business Solution Provider