The 7 WhatsApp Templates Every Indian SMB Needs (With Real Examples)

Every Indian SMB on the WhatsApp Business API ends up with a "templates" folder. Most of them have 30+ templates that no one uses, plus 3–5 they actually rely on every day. This post is about those 3–5 — except we'll give you 7, because we've seen the same patterns work across hundreds of businesses we've onboarded.

For each template you'll get the actual copy (with placeholder variables), why it works, and the most common reason Meta rejects it during template approval. Save this post; the templates here are paste-ready.

A quick refresher on template categories

Meta classifies WhatsApp Business API templates into four categories. The category determines:

• Whether the customer needs to opt-in
• The cost per conversation
• Approval strictness

Category	Use	Opt-in needed	INR/conversation (2026)
Utility	Order updates, alerts, reminders, post-purchase service	No (transactional)	~₹0.30
Authentication	OTPs only	No	~₹0.10
Marketing	Promotions, offers, broadcasts	Yes (explicit)	~₹0.65
Service	User-initiated conversations only	N/A (free first 1k/month)	Free initially, then ₹0.30

Six of the seven below are utility. One is marketing. We'll flag each.

Template 1: Order confirmation (utility)

The first template every D2C and ecommerce business needs.

Hi {{1}},

Thanks for your order! 🎉

Order ID: *{{2}}*
Items: {{3}}
Total: *₹{{4}}*

Payment: {{5}}
Delivery: {{6}} (estimated {{7}})

We'll send tracking once it ships. Reply HELP if you need anything.

Why it works. Customers anchor their expectation when they get this. Setting "estimated delivery" upfront cuts "where is my order?" inbound by ~40% in our data. The order ID becomes the single point of reference for all future conversations.

Approval gotcha. Don't mark this as marketing. Meta's bots flag transactional templates that look promotional ("our amazing products are on the way!") — keep it factual.

Template 2: COD confirmation before dispatch (utility)

This is the single highest-ROI template in Indian D2C. We dedicated a whole post to why it cuts RTO from 30% to 10%. Here's the template.

Hi {{1}},

Your order *{{2}}* ({{3}}) is going out for delivery to:
{{4}}

Total to pay on delivery: *₹{{5}}*

Reply to confirm:
✅ YES — I'll receive it
❌ NO — please cancel

If we don't hear from you in 12 hours, we'll cancel to avoid wasted delivery.

Why it works. The 12-hour window with cancel-by-default catches the "soft cancellations" that would otherwise become RTO. Customers who would have refused on doorstep just don't reply, and your warehouse cancels — saving the round-trip shipping cost.

Approval gotcha. Make sure the message is unambiguous about cancellation behaviour. Templates that say "we'll cancel" without explaining the trigger get rejected more often.

Template 3: Appointment reminder (utility)

For salons, clinics, tutors, real estate site visits, photographers — anyone whose business runs on appointments.

Hi {{1}},

This is a reminder for your appointment:

📅 *{{2}}* at *{{3}}*
📍 {{4}}
👤 With: {{5}}

To reschedule, reply RESCHEDULE.
To cancel, reply CANCEL.

Why it works. Salon no-show rates drop from ~22% to ~7% with a 24-hour-before reminder, per data from our portfolio. The cancel/reschedule shortcut is critical — customers who'd otherwise no-show will use it ~80% of the time, freeing the slot for someone else.

Approval gotcha. Stick to one reminder. A second one ("just 2 hours away!") is fine as long as it's also categorized as utility, but Meta sometimes rejects the second-reminder template if the wording is too marketing-flavoured ("Don't miss your appointment!").

Template 4: Payment reminder (utility)

For services, subscriptions, B2B invoicing.

Hi {{1}},

A friendly reminder that invoice *{{2}}* for *₹{{3}}* is due on *{{4}}*.

Pay now in 30 seconds: {{5}}

Already paid? Reply PAID and we'll mark it cleared.

Why it works. Indian SMBs collect 30%+ faster on invoices reminded via WhatsApp than via email. The "already paid?" out is important — half of overdue invoices have actually been paid via UPI but not reconciled, and giving the customer a way to flag it without logging in saves them the friction of arguing.

Approval gotcha. Don't send these more than once per invoice. Meta's quality system flags templates sent repeatedly to the same customer.

Template 5: Re-engagement / win-back (marketing)

The one marketing template you'll actually use. For lapsed customers who haven't bought in 60+ days.

Hi {{1}},

It's been a while! 👋

We're running a special offer for customers we haven't seen in 60+ days:

*{{2}}* off your next order, code *{{3}}*

Valid till {{4}}. Browse what's new: {{5}}

Reply STOP if you'd prefer not to hear from us.

Why it works. Win-back campaigns have a 4–7% reactivation rate when sent at the 60–90 day window. Earlier than 60 days feels intrusive; later than 90 days the customer has fully moved on. The discount code makes the call-to-action concrete; the STOP option preserves your quality rating.

Approval gotcha. This is the template most often rejected. Reasons: (a) the discount sounds too aggressive ("HUGE 50% OFF!!!"), (b) it lacks the STOP option, (c) the offer expiry is unrealistic ("offer ends in 1 hour" — Meta flags urgency manipulation). Keep it calm.

Template 6: Review request (utility)

After a customer has experienced your product/service.

Hi {{1}},

Hope you're enjoying *{{2}}*!

Mind sharing a quick review? It takes 30 seconds and genuinely helps us:
{{3}}

Or just reply with a number 1–5 if that's easier 🙂

Why it works. Review request response rates on WhatsApp average ~24% — about 8× higher than email. The "or just reply 1–5" fallback captures the customers who'd rate but not navigate to a form. You'll convert ~30–35% of those private replies into public reviews via a follow-up nudge.

Approval gotcha. The link should go to a review page on your domain or to a marketplace listing — not to a form that asks for personal data Meta hasn't approved you for. If your review form asks for an email address, it might trigger a "personal data harvesting" rejection.

Template 7: Welcome / onboarding (utility)

When a customer makes their first purchase or signs up.

Welcome to {{1}}, {{2}}! 🎉

A few things you might find useful:

📦 Track your order: {{3}}
💬 WhatsApp us anytime — we typically reply within 1 hour
⭐ Refer a friend, get ₹{{4}} off your next order: {{5}}

Reply MENU anytime to see options.

Why it works. The welcome message is your highest-engagement window — open rates are >95% within an hour. Don't waste it on "hi we exist." Pack it with the four things they'll need: tracking, support channel, referral, and a way to navigate.

Approval gotcha. "Reply MENU" needs to actually do something — Meta sometimes spot-checks templates by following the instructions. If MENU isn't wired to a chatbot flow, the template can be flagged for "broken interaction."

Approval tips that apply to all templates

Across Meta's template approval system, these are the patterns that get rejected most often:

• All-caps or excessive emoji. "🎉🎉 HUGE SALE 🎉🎉" gets rejected. One emoji is fine.
• URL shorteners. Don't use bit.ly. Use full URLs on your own domain.
• Data collection without consent. "Reply with your email and we'll send you a coupon" — flagged.
• Urgency manipulation. "Last chance!" "Only 2 hours left!" Meta cracked down on these in 2024.
• Promotional language in utility templates. Mixing "your order is on the way" with "and check out our new collection!" gets the template recategorized to marketing.
• Vague variable names. Template variables ({{1}}, {{2}}) need example values that make sense. Don't use "test" or "asdf" as samples.

Templates typically approve in 5–60 minutes for utility, 1–24 hours for marketing. If approval takes longer than 24 hours, log a support ticket — usually a manual reviewer needs to look at it.

Frequently asked questions

How many templates can I have?

There's a soft cap at 250 active templates per WhatsApp Business Account. Most SMBs use 7–15. If you're hitting 50+, you're probably duplicating templates that should be variables instead.

Do I need separate templates per language?

Yes. Each language is a separate template (English template + Hindi template = 2 separate approvals). You can also send a multi-language template where Meta auto-picks based on the customer's locale, but the individual language versions still need approval.

Can I edit a template after it's approved?

Limited edits, yes. You can change the body text within the same category. You can't change category. You can't add/remove variables. Big changes mean creating a new template.

How do I know which templates are performing?

Meta exposes per-template metrics: sent, delivered, read, replies, blocks. Track block rate above all — anything over 0.5% means your template is annoying enough that customers are reporting it as spam, which damages your account quality rating.

---

If you want these templates pre-loaded into your WhatsApp inbox with the variables wired to your actual orders, contacts, and CRM data, start a Doggu trial — they're in the template library by default and approved with Meta on day one.