WhatsApp template rejected for having a variable at the start of the message

If Meta rejected a WhatsApp template because the message starts with a variable, it's not serious and you can fix it yourself without touching a single line of code. The rejection means that the text you uploaded starts directly with a placeholder (for example "{{1}}, your order is ready") instead of starting with fixed words. Meta requires that every template has a real text header before the first variable, so that the message makes sense even if the data that gets filled in comes in empty or odd. It's fixed by rewriting the beginning of the text and resubmitting the template for review.

Before we continue, an important clarification: this is a template content issue, not an error with the API or your account. There is no error code to look up, nothing broke and you didn't lose your number. It's an editorial rejection from Meta about how the message is written.

What the rejection exactly means

When you upload a template in WhatsApp Manager, the text is divided into two parts: what you write as fixed text and the placeholders that get filled in with contact data (the variables, which look like {{1}}, {{2}}, etc.). Meta reviews that text before approving it, and one of the things it checks is that the first part of the message is fixed text, not a variable.

Simply put: the message can't start with a gap. It has to start with something that is already written. If it starts with the variable, the rejection is automatic and doesn't depend on whether the rest of the text is fine.

• Rejected: "{{1}}, your appointment is tomorrow at 15:00."
• Accepted: "Hi {{1}}, your appointment is tomorrow at 15:00."
• Rejected: "{{1}} {{2}}, we confirm your order."
• Accepted: "We confirm your order, {{1}}. It arrives on {{2}}."

Why Meta requires that the message doesn't start with a variable

The underlying reason is that a template has to be readable and understandable on its own, without depending on the data that gets filled in arriving correctly. Meta does not publish the fine details of how it validates each case, so what follows is the practical explanation of why this rule exists, not a verbatim quote from their documentation.

• If the data arrives empty or badly filled in, a message that starts with a variable is left without context: the contact receives ", your turn is tomorrow" and understands nothing.
• A message that starts with fixed text can be classified and moderated better: it's clear what it's about before looking at the data.
• Starting with a variable is a typical pattern of messages assembled in bulk, and Meta looks at it more warily because it resembles a mass send without its own content.
• Fixed text at the start makes the template work for all contacts, even if the name or number that gets filled in changes.

It's not an arbitrary rule: it's the same logic that makes an email start with "Hello" and not with the bare name. If you want the official details, they're in Meta's documentation on message templates; the other format rules that are reviewed in the same pass are also listed there.

How to fix it step by step

All of this is done from the dashboard, without programming. You don't need a token, webhook or technical help.

1. 1Go to WhatsApp Manager with the account that administers your WhatsApp Business number.
2. 2Find the rejected template in the template list and open it. There you'll see the text as you entered it and the reason for the rejection.
3. 3Look at the first word of the message body: if it's a variable ({{1}}, {{2}} or similar), that's the problem.
4. 4Write a short, natural fixed text at the front: "Hello", "Good morning", "We're writing to you from [business name]", "We confirm your order". Anything, but make it words, not a gap.
5. 5Check that the variables you already had are still in the same order and that the number of placeholders to fill in hasn't changed. If you add or remove one, you also have to update the system that sends the message.
6. 6Save the changes and resubmit the template for review.
7. 7Wait for the response. The only deadline Meta recognizes for template approval is up to 48 hours; it may come sooner, but there is no guaranteed shorter time.
8. 8While you wait, don't duplicate the template under another name: two nearly identical versions compete with each other and one can be rejected for resembling the other.

Examples of how to rewrite the opening

The fix is almost always adding two or three words at the beginning. These are typical cases by industry.

• Food service: "{{1}}, your order is out" becomes "Hi {{1}}, your order is out."
• Appointments and beauty: "{{1}}, we'll see you tomorrow" becomes "We're reminding you about your appointment, {{1}}: tomorrow."
• E-commerce: "{{1}}, your purchase was confirmed" becomes "We've confirmed your purchase, {{1}}."
• Real estate: "{{1}}, there's a new property" becomes "There's a new property for you, {{1}}."
• Collections: "{{1}}, you have a pending payment" becomes "We're reminding you about a pending payment, {{1}}."

Notice that in every case the name stays just as personalized, only the order changes. You don't lose any closeness by moving the variable two words to the right.

How to keep it from happening again

Rejection for a variable at the beginning happens a lot when several people on the team build templates at the same time without a written rule. These are the habits that prevent it.

• Set a fixed rule: every template starts with text, never with a blank to fill in.
• Before sending, read the message out loud as if you were the one receiving it. If the first word doesn't exist until the data is filled in, it's wrong.
• Test the template with an empty data field. If the message makes no sense, the opening needs more fixed text.
• Leave one person in charge of uploading templates, or at least one who reviews before sending. Rejections usually come from rushed sends.
• Save approved templates as a model for the next ones: copying one that already passed review is faster than writing from scratch.
• Don't mix a format fix with a big content change in the same send. If Meta rejects it, you won't know which of the two it was.

When the real problem is something else and this rejection is only the symptom

Sometimes the rejection says one thing, but the underlying reason is different. If you fix the opening and get rejected again, check these points before sending it a third time.

• The template content promises something the category doesn't allow: an aggressive promotion uploaded as a service message, for example.
• The template has too many variables together, or variables that add nothing, and Meta reads it as a mass-produced message.
• The template name or text looks too similar to another one you already have approved.
• The chosen category doesn't match what the message says (marketing, utility, or authentication).
• The text has formatting errors, strange characters, or extra spaces that sneak in when you copy and paste.
• The account has some pending verification or quality issue, and that affects the review of everything you send.

If the rejection continues after you fix the opening, the reason is no longer this one. In that case, it's worth reading Meta's full rejection message carefully and, if it's still unclear, writing to support from the WhatsApp Business panel itself. How long it takes to resolve varies by case, and there's no timeframe that can be promised in advance.

What to check while you wait for approval

The template is under review and you can't use it yet. In the meantime, there are things you can get ready so you don't lose time.

• Confirm that the system or tool sending the message has the correct number of variables loaded.
• Check whether that template is used in any scheduled campaign and let the team know if it needs to be postponed.
• Take the opportunity to review the other active templates and see if any of them start with a variable: better to fix them before they get rejected.
• If you use a tool with an inbox and templates, like Wando, you can see each template's status from the panel and which ones are approved to send.

Frequently asked questions

These are the questions that always come up when someone gets this rejection.

• Can I put the contact's name at the end instead of the beginning? Yes, and it's usually the simplest fix: "Hi, {{1}}, ..." or "..., {{1}}".
• Do I lose my history or the conversation because of this rejection? No. It's feedback about the template text; it doesn't affect your chats or your number.
• How long does the new review take? The only timeframe Meta recognizes is up to 48 hours. It may come through sooner, but there's no guarantee of a shorter time.
• Can I use the template while it's under review? No. Until it's approved, it can't be sent.
• Am I charged anything for this rejection? Rejected templates aren't sent, so they don't generate a conversation. Meta's conversation prices vary by country and are in its official documentation.
• Can I have two similar templates in case one fails? It's not a good idea: two nearly identical templates compete with each other and one can be rejected for resembling the other.
• Can this make me lose my account? No. A template rejection for formatting isn't an account penalty; it's a content correction.