WhatsApp Template Messages: 14 Approved-Format Examples (2026)
By Pushpa Godara · Chief Executive Officer, Wappblaster
In short: A WhatsApp template is a pre-approved message skeleton with numbered variables ({{1}}, {{2}}) that the API fills per customer. Write templates specific enough to be clearly non-spam, generic enough to reuse: state who you are, why this message, one clear action. Utility phrasing (order, payment, appointment) costs a fraction of marketing phrasing, so wording is literally money.
Business-initiated messages on the WhatsApp API must use templates: message skeletons Meta approves in advance, with numbered variables the system fills per customer. Template writing is a small craft with real money attached: category decides your per-message price, approval decides your timeline, and wording decides whether recipients block you into a downgraded tier.
Fourteen examples in approvable shape. Variables are {{1}}-style; in RMDialer’s bulk and auto-send flows they fill from the lead’s record automatically.
Utility templates (the cheap category: transactional, expected)
- Order confirmation: “Hello
{{1}}, your order{{2}}with [business] is confirmed:{{3}}for ₹{{4}}. Expected delivery:{{5}}. Questions? Reply here.” - Delivery update: “
{{1}}, your order{{2}}is out for delivery today between{{3}}. Please keep ₹{{4}}ready if paying on delivery.” - Payment reminder: “Dear
{{1}}, invoice{{2}}of ₹{{3}}is due on{{4}}. Pay via UPI:{{5}}. Please ignore if already paid.” (The full reminder ladder uses variants of this at each rung.) - Appointment confirmation: “
{{1}}, your appointment with{{2}}is confirmed for{{3}}at{{4}}. To reschedule, reply here.” - Appointment reminder: “Reminder:
{{1}}, your{{2}}appointment is tomorrow at{{3}}. Location:{{4}}. Reply YES to confirm.” - Follow-up after call: “Hello
{{1}}, thank you for speaking with [business] today. As discussed, here are the details of{{2}}:{{3}}. I will call you on{{4}}as decided.” - Renewal notice: “
{{1}}, your{{2}}is due for renewal on{{3}}(₹{{4}}). Renew before the date to continue without a break:{{5}}.” (Timing rules here.)
Marketing templates (the expensive category: promotional, opt-in)
- Offer to past customers: “Hello
{{1}}, since you chose our{{2}}earlier, an offer picked for you:{{3}}at{{4}}% off till{{5}}. Reply STOP to opt out.” - New arrival: “
{{1}}, the new{{2}}collection you asked about has arrived at [business]. First look:{{3}}. Shall I keep a piece aside?” - Festival campaign: “Wishing you a bright
{{1}},{{2}}! Our festival range with offers up to{{3}}% is live till{{4}}:{{5}}.” (Better: separate the greeting from the offer.) - Event/webinar invite: “
{{1}}, [business] invites you to{{2}}on{{3}}at{{4}}. Seats are limited: reply YES and we will register you.” - Win-back: “
{{1}}, it has been{{2}}months since your last{{3}}with us: we would love to serve you again. Here is{{4}}as a welcome-back: valid till{{5}}.”
Authentication
- OTP: “
{{1}}is your verification code for [business]. Valid{{2}}minutes. Do not share it with anyone.”
The one every business forgets
- Opt-in confirmation: “
{{1}}, you are now subscribed to updates from [business]: order alerts, offers and reminders on WhatsApp. Reply STOP anytime to unsubscribe.” (This template is your consent record made visible: send it once, keep the goodwill forever.)
Why templates get rejected, and the fixes
- Vague bodies (“Hello
{{1}},{{2}}”): reviewers reject skeletons that could carry anything. Fix: real sentences, variables only for the changing parts. - Category mismatch: promotional wording submitted as utility gets rejected or silently re-categorised to marketing prices. Write utility templates in genuinely transactional language.
- Formatting violations: variables at the very start/end of the body, missing example values at submission, URLs as bare variables. Follow the
{{n}}order and give realistic samples. - Policy content: prohibited categories and spam patterns. If it reads like a lottery SMS from 2014, it is.
Approval usually lands in minutes to a day. Build a small library: one utility set for your lifecycle events, one marketing set per season, and let the records decide who gets which: the craft of templates is nothing next to the craft of sending them to the right people.
- whatsapp api
- marketing