Utility WhatsApp Template Examples That Work

Why utility WhatsApp templates get approved faster

Meta classifies every WhatsApp template into a category: Marketing, Utility, or Authentication. A utility WhatsApp template gets a meaningfully easier ride. It's transactional, expected by the customer, and rarely reported as spam, so it tends to approve faster and protect your quality rating better than marketing sends.

A utility WhatsApp template is anything tied to a transaction the customer already started: an order they placed, an appointment they booked, a payment they made. If the message wouldn't surprise the customer, it's probably utility.

Order update

Hi {{1}}, your order #{{2}} has shipped and is on its way!
Track it here: {{3}}
Expected delivery: {{4}}

Keep the variable count low and every placeholder mapped to something the customer can verify against their own order. Templates with vague or unverifiable variables get rejected more often.

Appointment reminder

Hi {{1}}, this is a reminder for your appointment on {{2}} at {{3}}.
Reply CONFIRM to keep this slot or RESCHEDULE if you need a new time.

Pairing a reminder with a clear reply instruction turns a one-way notification into the start of a conversation. That opens the 24-hour free-form window and lets your team (or an automation) handle rescheduling without another template send.

Payment confirmation

Hi {{1}}, we've received your payment of {{2}} for invoice #{{3}}.
Your receipt: {{4}}

Low-stock / restock alert

Hi {{1}}, {{2}} is back in stock. Since you asked about it, we wanted you to know first.
Shop now: {{3}}

This one sits closer to the marketing/utility line. It's approved as utility only when it's tied to something the customer explicitly expressed interest in (a waitlist signup, an out-of-stock notification they opted into), not a blanket "back in stock" blast to everyone.

What gets utility templates rejected

• Promotional language ("Sale!", "Limited time", "% off") anywhere in the body. That reads as marketing no matter how you tag it.
• Variables with no clear, verifiable meaning to the recipient.
• A call-to-action that leads somewhere unrelated to the original transaction.

Building your own

Start from the transaction, not the message. If you can point to the exact order, booking, or payment event that triggers the send, you're already most of the way to an approvable utility WhatsApp template. InboxCenter's template builder validates structure and variable count against Meta's requirements before you submit, so you catch formatting issues before they cost you an approval cycle.