Back to blog
  • whatsapp-templates
  • compliance
  • ecommerce

WhatsApp Message Templates: Examples That Get Approved

Composing a WhatsApp business message template on a smartphone

If you want to send proactive messages on the WhatsApp Business API — order updates, offers, reminders — you can't just type and hit send. You send a pre-approved message template. The fastest way to learn the rules is to study WhatsApp message template examples that actually pass review, then copy the structure. This guide gives you exactly that: how templates and categories work, why templates get rejected, and seven ready-to-use examples for Indian D2C brands.

Everything here reflects how Meta's template system works as of 2026 — Meta updates its policies regularly, so always verify the current rules before you launch.

What a WhatsApp message template actually is

A template is a reusable message format you submit to Meta for approval. Once approved, you can send it to opted-in customers — even outside the 24-hour conversation window — with personalised details filled into placeholders.

  • Placeholders look like {{1}}, {{2}} and get replaced at send time with a name, order number, amount, and so on.
  • Components can include a header (text or image), a body, a footer, and buttons (quick replies or a link).
  • Approval usually lands within minutes to a few hours, though it can take longer.

Templates are how you stay both proactive and compliant — the customer agreed to hear from you, and Meta vetted the message.

Categories — and why the category matters

Every template is submitted under a category, and the category affects both approval and cost:

  • Marketing — promotions, launches, offers, re-engagement. The most scrutinised and the most expensive to send.
  • Utility — transactional updates tied to an action the customer took: order confirmations, shipping, payment reminders.
  • Authentication — one-time passwords and login codes only.

Picking the wrong category is a top rejection reason. A discount dressed up as a "utility" order update will get bounced. Because categories also drive your per-conversation cost, getting them right protects your budget too — our guide to WhatsApp Business API pricing in India breaks down how that maths works. Clinics submitting appointment reminders should use the utility category and see WhatsApp for medical health scheduling for how confirm/reschedule flows fit together.

A team drafting WhatsApp message templates together at a screen for approval

Common rejection reasons (and how to avoid them)

Most rejections come down to a handful of avoidable mistakes:

  • Wrong category. Marketing content filed as utility. Match the category to the intent, honestly.
  • Placeholder problems. Starting or ending the body with a {{1}}, two placeholders in a row, or skipped numbers. Always surround variables with real text.
  • Vague variables. A template that is just Hi {{1}}, {{2}} gives Meta no context. Reviewers reject templates that could be filled with anything.
  • Promotional language in the wrong place. Discount codes inside a utility template.
  • Bad grammar, ALL CAPS, or spammy punctuation. "BUY NOW!!!" reads as spam.
  • Broken or shortened links. Use clean, full URLs.

How to submit a template for approval

  1. Pick the category that genuinely matches the message.
  2. Write the body with clearly-labelled placeholders surrounded by context.
  3. Add a sample value for each variable so the reviewer sees real intent.
  4. Attach buttons or a header if useful (a "Track order" link, a quick-reply).
  5. Submit and monitor status — fix and resubmit fast if it's rejected.
  6. Confirm opt-in is in place before you send to anyone.

How to get a WhatsApp message template approved

Most rejections happen on the first submission — not because the idea is wrong, but because the format breaks Meta's rules. If you searched how to get whatsapp message template approved, work through this checklist before you hit submit:

CheckPass?Why it matters
Category matches intent (utility vs marketing)Wrong category = instant rejection
No placeholder at start/end of body{{1}} cannot be the first or last token
Sequential variables ({{1}}, {{2}} — no skips)Gaps confuse reviewers and break send logic
Sample values filled for every variableReviewer must see real intent
No ALL CAPS, spam punctuation, or misleading urgencyReads as low-quality / spam
Full URLs (no shorteners) in buttons/linksBroken or opaque links get flagged
Opt-in captured before first proactive sendPolicy requirement, not optional

Typical turnaround is minutes to a few hours for straightforward utility templates; marketing templates face more scrutiny. If rejected, read Meta's reason code, fix one issue at a time, and resubmit — don't rewrite the whole template unless the category was wrong.

Pair approved templates with acquisition that brings opted-in contacts — many brands combine templates with click to whatsapp ads so the first conversation is customer-initiated and the follow-up templates stay compliant.

WhatsApp message template examples for Indian D2C

Here are seven examples you can adapt. Replace the placeholder text and confirm the category before submitting. (These are illustrative — keep your own brand voice.)

1. Order confirmation (Utility)

Hi {{1}}, thanks for your order with {{2}}! 🎉
Order #{{3}} for ₹{{4}} is confirmed and being prepared.
We'll message you when it ships.

2. Shipping update (Utility)

Good news {{1}}! Your order #{{2}} has been shipped 📦
Track it here: {{3}}
Expected delivery: {{4}}.

3. Abandoned cart reminder (Marketing)

Hi {{1}}, you left {{2}} in your cart.
We've saved it for you — complete your order here: {{3}}
COD and easy 7-day returns available.

This one pairs perfectly with an automated sequence — see our abandoned cart recovery playbook for the full flow.

4. COD order confirmation (Utility)

Hi {{1}}, please confirm your Cash on Delivery order #{{2}}
for ₹{{3}}.
Reply YES to confirm or NO to cancel.

5. Reorder nudge (Marketing)

Running low, {{1}}? It's been a while since your last {{2}}.
Reorder in one tap: {{3}}

6. Feedback request (Utility)

Hi {{1}}, how was your experience with order #{{2}}?
Tap to rate us — it takes 10 seconds: {{3}}
Your feedback helps us serve you better. 🙏

7. Payment reminder (Utility)

Hi {{1}}, a gentle reminder that your payment of ₹{{2}}
for order #{{3}} is pending.
Pay securely here: {{4}}

8. Appointment reminder (Utility)

Hi {{1}}, reminder: your appointment with {{2}} is on {{3}} at {{4}}.
Please reply CONFIRM or RESCHEDULE if you need to change your slot.

Use this for clinics and service businesses — pair it with the scheduling flows on our WhatsApp for medical health scheduling use-case page.

A quick note on adapting these: keep the structure but rewrite the wording in your own brand voice, and always pair each template with the right category from the section above. The same message can be approved as utility or rejected as marketing depending on a single promotional line — so read each one back and ask, "is this a transactional update the customer is expecting, or am I selling?" When in doubt, split it into two cleaner templates rather than one that tries to do both. Build a small, well-organised library and reuse it across campaigns instead of writing from scratch each time.

Headers, buttons, and footers

The body is only part of a template. Used well, the other components lift response rates without risking approval:

  • Headers. A short text header works as a subject line ("Your order has shipped"). An image or document header suits invoices, shipping labels, or a product shot — great for marketing.
  • Buttons. Quick-reply buttons ("Confirm", "Reschedule") make replies effortless, while a call-to-action button can open a tracking link or your store. Buttons reduce typing, which lifts conversion on mobile.
  • Footers. A small footer is the natural home for a gentle "Reply STOP to opt out" line on marketing messages.

Keep components purposeful — every extra element is something a reviewer scrutinises, so add them when they help the customer, not to decorate the message.

Keep your quality rating healthy

Approval is the start, not the finish. Meta assigns each number a quality rating based on how customers react to your messages, and a falling rating can throttle how much you're allowed to send.

  • Send only to people who opted in. Buying or scraping numbers is the fastest route to blocks.
  • Watch your block and report rates. If customers mark you as spam, your rating drops — and so does your daily messaging limit.
  • Match frequency to value. A useful order update is always welcome; a third promo in a week is not.
  • Retire underperforming templates. If a template draws complaints, pause it and rework the copy.

A healthy rating means higher limits and smoother approvals over time — it compounds, so protect it from day one. If you send at scale, our guide on how to send bulk WhatsApp messages without getting banned explains the quality rating and opt-in rules in depth. Volume limits and per-category costs are covered in our pricing guide.

Variables, opt-in, and good habits

A few rules that keep templates approved and customers happy:

  • Always collect opt-in first. A customer must agree to receive messages before you send — a checkbox at checkout or a clear confirmation works.
  • Label every variable. Surround {{1}} with text so its purpose is obvious to both Meta and the customer.
  • Keep marketing and utility separate. Don't smuggle an offer into an order update.
  • Make opting out easy. Honour stop requests instantly to protect your quality rating.
  • Refresh tired templates. Marketing copy fatigues — rotate it every few weeks.

Get the category right, write clear placeholders, and lead with genuine value, and the vast majority of your templates will sail through. Start with the seven above, adapt them to your brand, and build your library from there.

A green thumbs-up signalling a WhatsApp message template approved and ready to send

See QwikPing in action

Run campaigns, manage a shared inbox, and automate WhatsApp journeys from one dashboard.

See QwikPing in action