We did not find any results

Why Meta Rejects WhatsApp Templates and How to Resolve Delivery Errors

A template rejection and a message delivery failure are different events. Check the exact status, reason and error code before changing a template or retrying a campaign.

Common reasons for template rejection

  1. Promotional content used in the wrong context. Marketing templates may contain offers and sales messages when they comply with policy and recipients have opted in. Sales wording alone is not a universal reason for rejection. Do not present a promotion as a purely transactional utility message.
  2. Policy or intellectual property violations. Avoid misleading claims, scams, spam, impersonation and content that infringes another party’s rights.
  3. Prohibited or restricted content. Meta restricts certain products, services and uses, including weapons, drugs, adult content and some regulated sectors. Restrictions and any exceptions depend on the current policy, country and business activity. Check the applicable policy rather than assuming that regulatory approval alone makes a campaign eligible.
  4. Abusive or threatening language. Do not threaten, harass or shame recipients.
  5. Unclear content or variables. Reviewers must understand the message and what each variable will contain. Add meaningful fixed text and realistic sample values.
  6. Phishing or requests for sensitive identifiers. Do not ask recipients to disclose passwords, full payment card numbers, full financial account numbers or other sensitive identifiers in a message.
  7. Language and formatting problems. Match the selected template language, write clearly and follow the limits for the specific template format. Check spelling, punctuation and variable syntax.
  8. Incorrect category. Choose Marketing, Utility or Authentication according to the real purpose. Promotional content does not belong in Utility, and Authentication templates are for supported authentication use cases.

Formatting checks and examples

1. Spacing and text structure

Use readable, concise paragraphs. Avoid unnecessary blank lines, excessive spaces or text that is difficult to understand. A suggested number of lines is an editorial preference, not a universal approval rule.

Hello {{1}},
Your appointment is tomorrow at 10:00.
We look forward to seeing you.

2. Variables and placeholders

For positional variables, use matching braces and sequential numbers such as {{1}}, {{2}} and {{3}}. Do not leave gaps, use unsupported characters in parameter names or submit a message consisting only of variables. Do not start or end the body with a variable, and include sample values during submission.

Hello {{1}}, your order {{2}} is ready for collection at {{3}}. Thank you.

A body such as {{1}} {{2}} {{3}} does not provide enough fixed context. Likewise, avoid having too many variables relative to the amount of meaningful text.

3. Message length

Provide enough information to explain the purpose, without unnecessary repetition. A one-word message may lack context, but there is no general requirement to write exactly two to six lines. Stay within the character limit for each component and template type.

4. Symbols and emojis

Use punctuation and emojis sparingly and meaningfully. Repeated exclamation marks or long emoji sequences can make a message unclear. Follow any format-specific emoji limits; ordinary Unicode characters are not automatically prohibited.

5. Links

Use complete, working HTTPS links that clearly relate to your business and the message. Check braces and sample values in dynamic links. For example: https://example.com/order/{{1}} where the component supports a dynamic suffix. The example domain is a placeholder; replace it with your actual site.

6. Headers, footers and buttons

Use a descriptive header when useful, a relevant footer and clear button labels such as “View order”. Headers and footers are optional in standard templates; omitting an optional component is not itself a rejection reason. Button types, counts and labels must match the chosen format, and an offer button should not be disguised as a service update.

7. Language

Select the language used by the template, proofread it and avoid unrelated language fragments. Brand names and necessary product terms can remain as appropriate.

8. Category and duplication

Match the category to the content and check whether an equivalent template already exists. Meta may reject duplicate wording in an existing template’s body and footer; use or revise the appropriate existing template instead of creating unnecessary copies.

Original Hebrew reference screenshots

These historical screenshots illustrate the original guide. The current explanations above take precedence: optional headers and footers are not mandatory, and editorial suggestions are not universal Meta rejection rules.

Original Hebrew template example 1

Original Hebrew template example 2

Original Hebrew template example 3

Original Hebrew template example 4

Original Hebrew template example 5

Original Hebrew template example 6

Original Hebrew template example 7

Common delivery errors

Healthy ecosystem engagement — error 131049

This usually relates to Meta’s limits on marketing messages a recipient can receive. There is no fixed rule that a seventh message is always blocked. If you suspect this limit, Meta advises waiting at least 24 hours before retrying. Repeated immediate attempts do not remove the limit. Respect any opt-out and do not keep retrying messages to someone who has stopped marketing delivery.

Payment method error — 131042

Check that billing is set up correctly for the relevant WhatsApp Business account. Possible issues include a missing or inactive payment account, a credit limit, account suspension, or missing currency/timezone settings. Review Meta billing settings and contact the account administrator or Pulseem support if needed.

Unable to deliver the message — 131026

A recipient number that is not registered with WhatsApp is one possible cause. Other causes include an outdated WhatsApp app or unaccepted updated terms. Through an appropriate alternative channel, ask the recipient to confirm the number, update the app and check whether they can send your business a message. Do not assume every delivery failure means the number is invalid.

Message was not sent as part of an experiment — 130472

Meta may restrict delivery to recipients included in a messaging experiment. This does not necessarily indicate a template defect. Check the current experiment guidance and the exact error. If appropriate and permitted, offer another contact channel or invite the customer to initiate a WhatsApp conversation. Do not promise that an incoming message will remove every experiment or marketing restriction, and do not relabel marketing as Utility to evade it.

Business account restricted or disabled

Meta may restrict sending or disable a WhatsApp Business account after detecting a policy violation. Open WhatsApp Manager or Business Support Home, read the reason and address the issue. If you believe the decision is wrong, use Request Review where available and provide the information Meta requests through its official process. Review times and restoration are not guaranteed; do not rely on a universal 48-hour recovery promise.

Cannot display this message

The received message may contain a file or message type that the interface does not support. Ask the recipient to resend it in a supported format, such as an appropriate JPEG, PNG, MP3 or MP4 file, and check the current size and format requirements. If the media cannot be downloaded, arrange an appropriate alternative channel.

Original Hebrew interface example of a message that cannot be displayed

What to do after a template rejection

  1. Open the rejection notice in WhatsApp Manager or Business Support Home and read the specific reason.
  2. Correct the content, category or formatting and add realistic samples for variables and media.
  3. Resubmit the template, or appeal if the decision appears incorrect.
  4. Wait for the new status before using the template in campaigns.

Reference information checked on 15 October 2026: Meta template review, WhatsApp error codes and WhatsApp Business Messaging Policy.