20+ WhatsApp Business API Template Message Examples (By Use Case)

The fastest way to get a WhatsApp template approved and actually working isn't starting from a blank box - it's adapting a template that's already proven itself for the same job. Below are real-world template patterns organized by use case, covering the categories almost every business ends up needing: transactional confirmations, reminders, marketing, and authentication.

Order and payment confirmations are the single most common template on WhatsApp, and for good reason - customers open these almost instantly. A working pattern: "Hi {{1}}, your order #{{2}} has been confirmed and will ship by {{3}}. Track it here: {{4}}." Keep it factual and skip the marketing language entirely - this falls under the UTILITY category, which has different (usually cheaper) pricing than MARKETING, and mixing in promotional language risks Meta reclassifying it.

Appointment and booking reminders work best sent twice: a confirmation immediately after booking, and a reminder 24 hours before. Pattern: "Reminder: your appointment with {{1}} is tomorrow at {{2}}. Reply YES to confirm or CANCEL to reschedule." Pairing this with a QUICK_REPLY button (not just asking the customer to type a word) meaningfully improves response rates, since a button is a single tap versus a typed reply.

Delivery and shipping updates benefit from a status-specific template per stage rather than one generic "order update" template reused for everything - "Your order has shipped," "Out for delivery today," and "Delivered" as three separate approved templates read as considered, timely updates instead of one vague message repeated three times with different text stuffed into the same placeholder.

Abandoned cart and re-engagement templates sit in MARKETING and need a genuinely soft touch to avoid getting reported - "Still thinking it over? Your cart is saved: {{1}}" outperforms anything that reads as pressure ("Don't miss out!", "Last chance!"), both in click-through and in staying off spam reports, which is exactly the discipline this blog's own post on broadcast campaigns covers in more depth.

One-time passcodes (OTP) use WhatsApp's AUTHENTICATION category, which has its own stricter template rules - no marketing content, no links, and Meta requires the code itself to be the only real content: "{{1}} is your verification code. It expires in 5 minutes. Do not share this code." This category also supports a one-tap autofill button on supported devices, worth enabling since it removes the copy-paste step entirely.

Whichever category you're building for, the pattern that gets approved fastest and performs best afterward is the same: one template, one clear job, written the way a person would actually say it - not a generic placeholder-stuffed paragraph trying to cover every possible scenario at once. Build the specific version for the specific moment, and approval plus real engagement both come easier.