Template Rejected by Meta: Why It Happens and How to Fix It Without Burning Your Number

How to fix and resubmit for review

Rejection rarely comes with a detailed explanation, so the method is elimination, in the following order.

First, review the category. Read the text and ask: is there anything here that offers, invites, or promotes? If yes, it’s marketing. If the goal is utility, remove the offer instead of changing the category — a clean utility template is cheaper and approved faster.

Second, add context. Identify the company, mention the reason for contact and the existing relationship. "This is [Company]. Regarding budget no. {{1}} we sent on {{2}}..." passes; "Hi {{1}}, how are you?" does not.

Third, adjust variables. Never at the beginning or end, never stuck together, and always with a realistic example filled in the sample field — this detail solves a significant portion of rejections.

Fourth, simplify. Short, direct text, no slang, no excess emojis, no shouting uppercase letters.

Fifth, use buttons instead of instructions. Quick reply buttons communicate better than "reply YES to confirm" and improve both approval and response rates simultaneously.

Resubmit with the corrected text and, if possible, a new name. Resubmitting exactly the same content expecting a different result doesn’t work — and repeated resubmissions of the same rejected template draw negative attention to the account.

Errors that only appear during sending

An approved template and a message that doesn’t arrive is another matter. The most frequent reasons:

Outside the service window with free text. Attempting to send free text to someone who hasn’t written in the last 24 hours. The solution is to use a template — the topic is detailed in the 24-hour window.

Incompatible parameters. The template expects three variables and the sending provides two, or sends a value with a line break where it’s not allowed. Technical error, simple fix, and usually takes down the entire campaign at once.

Template not available in the requested language. Registered in Portuguese and sent with another language code.

Invalid number or no WhatsApp. Dirty list is the most common cause of mass failure — and the most dangerous, because a high volume of invalid recipients affects the number’s reputation.

Number limit reached. Each number has a daily cap of unique contacts initiated by the company, which evolves according to history.

Platform decision about that message. There is a control on how many marketing messages the same user receives in a given period. When the limit is reached, the message simply isn’t delivered — it’s not your fault, and resending won’t help.

The returned error codes help distinguish these cases and change over time, so it’s worth consulting the current documentation. What doesn’t change is the interpretation: sending error is almost never a server problem. It’s list, parameter, window, or limit.

Template paused due to quality

There is a third, less known and more serious situation: the template was approved, worked for weeks, and suddenly stops being delivered. This happens when its performance worsens — many blocks, many reports, little response.

Templates with poor quality are temporarily paused and, if the problem persists, disabled. The warning precedes a bigger problem: poor template quality drags down the quality of the entire number, which determines sending limits and risk of restriction.

The fix is not technical, but content and list-related. Reduce frequency, review who you’re sending to, increase relevance, and check if there is recorded permission from all recipients. A paused template is a cheap warning of a problem that becomes expensive.

What never to do after a failure

Mass resending what was blocked. This is the most destructive mistake. If the platform refused delivery, insisting increases failure rates, signals anomalous behavior, and accelerates restrictions on the number.

Switching numbers to continue sending. A new number has a low limit and zero reputation, and the behavior change draws attention. Also, the approved template is linked to the account, not your preference.

Running the same template on multiple numbers simultaneously. Typical pattern of improper mass sending and one of the fastest ways to lose all numbers at once.

Treating it as an infrastructure problem. Restarting the server doesn’t change anything when the refusal is from the platform — and the time spent delays the real fix.

How to interpret sending results

After a campaign, the report usually shows numbers that seem contradictory. It’s worth knowing what each means, because misinterpretation leads to wrong decisions in the next campaign.

Sent. How many messages the platform accepted. It doesn’t mean they arrived — only that they passed initial validation.

Delivered. How many actually reached the device. The difference between sent and delivered is made up of invalid numbers, devices off for a long time, and platform refusals. A delivery rate below 90% almost always indicates a list problem.

Read. Depends on each recipient’s privacy settings, so underestimates actual reach. Useful for comparing campaigns, not as an absolute number.

Replies. The only indicator that really matters in a commercial campaign. Below 5% on a list with prior relationship, the problem is the text, not the platform.

Blocks and reports. The most important number for operation health, and the one no one opens. A campaign with a block rate above normal must stop the pattern immediately — not next time, now.

Combined interpretation guides correction. Low delivery and reasonable response: list problem. High delivery and low response: text or audience problem. High delivery, low response, and high block: the message is perceived as invasive, and insisting costs the number.

How to reduce rejection to almost zero

Companies that operate well follow four simple practices.

Pre-approved library. Six to ten templates covering recurring situations, approved before urgency exists.

Preference for utility. Whenever there is a concrete fact — order, appointment, due date, budget — use utility: easier approval, lower cost, and better reception.

Clean and permissioned list. Number validation, removal of those who opted out, respect for frequency. List is the variable that most influences delivery and quality.

Test with small volume first. Fifty sends before five thousand reveal parameter, text, and reception problems when they are still cheap to fix.

Rejected template is a nuisance; insisting on sending after being blocked is damage. The difference between an operation that grows on the channel and one that loses numbers is often exactly in this interpretation — understanding what the platform is saying, fixing it, and moving on, instead of trying harder again.