WhatsApp Message Templates: Why They Get Rejected and How to Pass

A WhatsApp message template is the only way to open a conversation with a customer outside the 24-hour window, so every automation that initiates contact depends on Meta's approval. Rejections are almost always caused by the same handful of mechanical rules rather than by judgement. Here is the full list, followed by the one decision that actually affects your cost.

Template structure

A template has four parts, three of them optional:

• Header - optional. One of text, image, video or document.
• Body - required. The message text, with positional variables.
• Footer - optional. Short text, no variables.
• Buttons - optional. Up to three, of type quick_reply, url or phone_number.

The mechanical rules behind most rejections

Template name

Lowercase letters, digits and underscores only - the pattern is ^[a-z0-9_]+$. A hyphen, a space or a capital letter fails the submission. The name is also immutable after creation; changing the wording means creating a new template.

Positional variables

Variables are {{1}}, {{2}}, {{3}} - positional, not named. There is no {{name}}. They must be sequential and start at 1: a template containing only {{1}} and {{3}} is rejected.

At send time the number of supplied values must match the variable count exactly, or you get error 132000.

Examples - the number one cause of rejection

Every variable must carry an example value. Meta rejects a submission without examples automatically. The example should be realistic: for a {{2}} representing a date and time, "12345" looks suspicious while "14/09/2026 at 10:30" passes. The reviewer - human or automated - reads the template with the examples substituted in, and that is what gets approved.

Sample file for a media header

If the header is media, a sample file is required at submission and is uploaded as a header_handle. The limits:

• Image - JPG or PNG, up to 5MB
• Video - MP4, up to 16MB
• Document - PDF, up to 100MB

That same file becomes the default media on real sends unless you pass a different media ID. A Meta media ID lives roughly 30 days, so a system that sends a media-header template over time needs to refresh it.

Length after substitution

The length limit applies to the text after variables are substituted. A template approved with short examples can still fail at send time with error 132005 when a long value is supplied. In Hebrew this bites sooner than you expect.

The decision that changes your cost: UTILITY vs MARKETING

Every template carries a category - UTILITY, MARKETING or AUTHENTICATION - and Meta prices them differently. You declare the category at submission, but Meta reclassifies based on the actual content.

The common case: an appointment confirmation or reminder is clearly UTILITY. Add a URL button pointing at your website and the template is reclassified as MARKETING, because a button leading to your site reads as promotion rather than as an operational update.

The practical fix: if a customer needs to reach a link from a transactional message, put it as plain text in the body instead of as a button. The customer can still tap it, and the template stays UTILITY.

The same logic applies to wording: "Your appointment is confirmed for" is an update. "Don't miss out!" or "Special offer" turns the same message into marketing.

Lifecycle - and what happens after approval

The statuses run: local draft, then pending once submitted, then approved or rejected. Only an approved template can be sent.

The part most systems miss: Meta can move a live, approved template to paused or disabled, based on a quality rating derived from recipient behaviour - blocks and reports. A paused template returns error 132015; a disabled one returns 132016.

Meta announces this only via webhook. Subscribe to the message_template_status_update and message_template_quality_update fields in your webhook configuration. Without them, the first time you learn your template was paused is when a campaign fails.

What to do differently

• Submit early. Approval takes anywhere from minutes to days and does not depend on your code being ready.
• Two languages, two templates. Same name, different language code, two separate submissions.
• Store the rejection reason. Meta returns one; without keeping it you resubmit the same mistake.
• Do not write like an ad. A transactional message that sounds transactional is approved faster, costs less, and gets blocked less.