40 WhatsApp Template Message Examples (Approval-Ready)

The fastest way to understand WhatsApp Business messaging is to read real WhatsApp template examples, so this is a library of 40 you can adapt today. They are grouped by the three categories Meta uses — utility, marketing, and authentication — because the category you choose decides whether a template gets approved, how much each message costs, and when you are allowed to send it. Copy the ones that fit your business, swap in your own variables, and you have a starting point that is far closer to approval than a blank box.

Every example below is written to be approval-ready, but approval-ready is not the same as guaranteed. Meta reviews each template you submit, and the same words can pass in one account and get flagged in another depending on context, history, and how the message reads. Throughout this guide we mark what tends to pass, what tends to get rejected, and the honest constraints — opt-in, category rules, and per-message pricing — that no template can get around.

Full disclosure: we build KlyoChat, a unified inbox that includes WhatsApp template management and broadcasts. That gives us a point of view, but it does not change the rules, which belong to Meta. Where we describe approval behavior or pricing we point you to the official documentation rather than inventing specifics, because those details change and you should budget from the live source.

What is a WhatsApp message template, and why does it need approval?

A WhatsApp message template is a pre-written, pre-approved message you register with Meta so you can send it to customers outside the 24-hour customer service window. When someone messages your business, you get a 24-hour window to reply freely with any content. Once that window closes, you can only reach them again with a template that Meta has reviewed and approved. Templates are the mechanism that lets you send order updates, reminders, and campaigns proactively.

A template is not one block of text. It is a structured object with named parts: an optional header (text, image, video, or document), a required body, an optional footer, and optional buttons (quick replies or call-to-action buttons like a link or phone number). Variables — written as placeholders such as {{1}} and {{2}} — let one approved template serve thousands of personalized messages. You register the shape once and fill the blanks at send time.

Approval exists because WhatsApp is a personal space and Meta protects it aggressively. A template is reviewed for its category accuracy, its content, and whether it looks like something a user would want. The review is usually fast — often minutes to a day — but a rejection means you rewrite and resubmit. The examples in this guide are built to reduce that back-and-forth, not to promise it away. For the full walkthrough of the review process, see our guide to WhatsApp template approval.

The three template categories, and why the category is the whole game

Meta sorts every template into one of three categories, and the category is the single most consequential choice you make. It governs whether a template is approved for its stated purpose, when you are allowed to send it, and — because Meta prices per message by category — what each send costs. Choosing the wrong category is the most common reason a template gets rejected or, worse, gets approved and then re-categorized later.

Utility templates relate to a specific transaction or account event the customer has already engaged with: an order, a booking, a payment, a delivery. Marketing templates promote, announce, or re-engage — anything designed to drive a new action rather than service an existing one. Authentication templates deliver one-time passcodes and verification codes and nothing else. The table below is the mental model to keep as you read the examples.

One nuance worth internalizing early: category is not a label you set and forget. Meta continuously watches how templates are used and how recipients react, and it can re-classify a template after approval if the real-world usage does not match the stated category. A utility template that starts carrying discount codes, or a marketing message routed to people who never opted in to promotions, invites exactly that kind of correction. Getting the category right at submission, and keeping usage consistent with it afterward, is what keeps a template stable over its whole life rather than just through the first review.

Utility template examples: order confirmations and receipts

Order-related messages are the easiest utility templates to get approved because they follow a real transaction the customer just made. They are also the messages customers most want, which is why they post strong read rates. The pattern is simple: confirm what happened, give the key details, and offer one useful next step. Here are eight order and receipt templates to adapt.

• 1. Order confirmed: Hi {{1}}, thanks for your order. We have received order {{2}} and it is now being prepared. Total: {{3}}.
• 2. Order receipt: Hi {{1}}, here is your receipt for order {{2}}. Amount paid: {{3}} on {{4}}. Keep this for your records.
• 3. Payment confirmed: Hi {{1}}, we have received your payment of {{2}} for order {{3}}. Thank you.
• 4. Payment failed: Hi {{1}}, your payment for order {{2}} did not go through. You can retry using the button below.
• 5. Order being packed: Good news {{1}} — order {{2}} is packed and will be handed to the courier shortly.
• 6. Order ready for pickup: Hi {{1}}, order {{2}} is ready for pickup at {{3}}. Please bring your order number.
• 7. Order modified: Hi {{1}}, your change to order {{2}} is confirmed. Updated total: {{3}}.
• 8. Order cancelled: Hi {{1}}, order {{2}} has been cancelled as requested. Any charge will be refunded within {{3}} days.

Utility template examples: shipping and delivery updates

Shipping updates are the workhorses of utility messaging. Customers open them because they are waiting for something, and each one reduces a where is my order support ticket. The trick is to send them at the moments that matter — dispatched, out for delivery, delivered, delayed — and to give a tracking link the customer can act on. Six shipping templates you can register today.

• 9. Shipped: Hi {{1}}, order {{2}} has shipped. Estimated delivery: {{3}}. Track it with the button below.
• 10. Out for delivery: Hi {{1}}, your order {{2}} is out for delivery today and should arrive by {{3}}.
• 11. Delivered: Hi {{1}}, order {{2}} was delivered at {{3}}. We hope you love it.
• 12. Delivery delayed: Hi {{1}}, order {{2}} is running late. New estimated delivery: {{3}}. Sorry for the wait.
• 13. Failed delivery: Hi {{1}}, we tried to deliver order {{2}} today but missed you. We will retry on {{3}}.
• 14. Address confirmation: Hi {{1}}, before we ship order {{2}}, please confirm your address: {{3}}. Reply YES to confirm.

Utility template examples: appointments, bookings, and reminders

For service businesses — clinics, salons, restaurants, agencies, tutors — appointment templates are where WhatsApp earns its place. A confirmation and a well-timed reminder cut no-shows more than almost any other message you can send, and both are clean utility use cases because they follow a booking the customer made. Here are six booking and reminder templates.

• 15. Booking confirmed: Hi {{1}}, your appointment for {{2}} is confirmed for {{3}} at {{4}}. See you then.
• 16. Reminder (24 hours): Hi {{1}}, a reminder that your appointment for {{2}} is tomorrow at {{3}}. Reply RESCHEDULE if you need a new time.
• 17. Reminder (1 hour): Hi {{1}}, your appointment for {{2}} is in one hour at {{3}}. We look forward to seeing you.
• 18. Reschedule confirmed: Hi {{1}}, your appointment has been moved to {{2}} at {{3}}. Thanks for letting us know.
• 19. Cancellation confirmed: Hi {{1}}, your appointment for {{2}} on {{3}} is cancelled. Book again any time.
• 20. Booking follow-up: Hi {{1}}, thanks for visiting us on {{2}}. Your next recommended appointment is around {{3}}.

Utility template examples: account, billing, and OTP-adjacent notices

Beyond orders and bookings, a set of account and billing templates rounds out most utility libraries. These are event-driven notices tied to something in the customer's account — a renewal, a low balance, an expiring card, a completed action. Note that these are account notices, not one-time passcodes: true OTP delivery belongs in the authentication category covered later. Four account and billing templates.

• 21. Subscription renewing: Hi {{1}}, your {{2}} plan renews on {{3}} for {{4}}. No action needed to continue.
• 22. Card expiring: Hi {{1}}, the card on file for your {{2}} account expires soon. Update it to avoid interruption.
• 23. Invoice ready: Hi {{1}}, your invoice for {{2}} is ready. Amount due: {{3}} by {{4}}.
• 24. Action completed: Hi {{1}}, your request to {{2}} is complete. Reference: {{3}}.

Marketing template examples: promotions, offers, and sales

Marketing templates are where the biggest results and the biggest constraints live. These messages promote, so they cost more per send, they demand clear opt-in, and Meta reviews them more critically. The upside is reach: a well-timed offer to an opted-in list gets read at rates email rarely matches. The discipline is to make each message genuinely worth an interruption. Six promotion templates to adapt.

• 25. Limited-time offer: Hi {{1}}, for the next {{2}} you can get {{3}} off {{4}}. Use code {{5}} at checkout.
• 26. Weekend sale: Hi {{1}}, our weekend sale is live — up to {{2}} off {{3}}. Ends {{4}}.
• 27. First-order discount: Hi {{1}}, welcome. Here is {{2}} off your first order with code {{3}}.
• 28. Loyalty reward: Hi {{1}}, you have earned {{2}} in rewards. Redeem it before {{3}}.
• 29. Free shipping window: Hi {{1}}, free shipping on all orders over {{2}} until {{3}}. Happy shopping.
• 30. Flash sale alert: Hi {{1}}, flash sale — {{2}} off {{3}} for the next {{4}} hours only.

Marketing template examples: product launches and announcements

Launch messages tell an opted-in audience that something new exists. Because the recipient already chose to hear from you, a launch template can be one of the highest-converting messages you send — the interest is presumed. The pattern is a clear headline, one specific benefit, and a single call to action. Avoid stacking three offers into one message; a launch does one job. Four launch and announcement templates.

• 31. New product launch: Hi {{1}}, our new {{2}} is here. {{3}} Be among the first to try it.
• 32. Back in stock: Hi {{1}}, good news — {{2}} is back in stock. It sold out fast last time.
• 33. Early access: Hi {{1}}, as a subscriber you get early access to {{2}} before it goes public on {{3}}.
• 34. Feature or menu update: Hi {{1}}, we have added {{2}}. Here is what is new and how to use it.

Marketing template examples: win-back and re-engagement

Win-back templates reach customers who used to buy and went quiet. They work because these people already know you — the job is to give them a reason to come back, not to introduce yourself. Keep the tone warm rather than desperate, lead with value, and respect that some people have simply moved on. Four win-back and re-engagement templates.

• 35. We miss you: Hi {{1}}, it has been a while. Here is {{2}} off your next order to welcome you back.
• 36. Abandoned cart: Hi {{1}}, you left {{2}} in your cart. It is still there if you would like to finish up.
• 37. Replenishment reminder: Hi {{1}}, you may be running low on {{2}}. Reorder in a couple of taps below.
• 38. Lapsed subscriber: Hi {{1}}, we have not seen you since {{2}}. Here is what is new and a reason to return.

Marketing template examples: seasonal, events, and feedback

Rounding out the marketing set are seasonal moments, event invites, and post-purchase feedback requests. Seasonal messages ride a calendar the customer already has in mind; event invites give a clear date and RSVP; feedback requests, kept short, both improve your product and signal that you listen. Two seasonal and event templates to close the marketing library.

• 39. Seasonal offer: Hi {{1}}, our {{2}} sale starts now. Enjoy {{3}} off {{4}} through {{5}}.
• 40. Event invite: Hi {{1}}, you are invited to {{2}} on {{3}}. Reply YES to reserve your place.

Authentication template examples: one-time passcodes

Authentication templates do exactly one thing: deliver a verification code. They live in their own category with their own format, they are priced separately, and they should never carry marketing or extra content. Meta provides a defined structure for these so that codes render safely and copy reliably. Because the format is tightly controlled, the copy examples here are deliberately minimal.

• Login code: {{1}} is your verification code. For your security, do not share this code with anyone.
• Password reset: {{1}} is your password reset code. It expires in {{2}} minutes.
• Transaction verification: {{1}} is your code to confirm your {{2}} transaction. Do not share it.

What gets a WhatsApp template rejected?

Knowing what to write is half the job; knowing what gets rejected is the other half. Most rejections come from a short list of avoidable mistakes, and once you recognize them you can clear them before you ever submit. The table below maps the common reasons to what triggers them and how to fix each one.

Utility or marketing? Where the line actually falls

Because category drives approval, timing, and cost, the utility-versus-marketing decision deserves its own reference. The principle is consistent: utility services a specific transaction or account event the customer already engaged with; marketing tries to create new engagement. The table below runs common messages through that test so you can categorize your own with confidence.

How to write a WhatsApp template that passes approval first time

You can raise your first-pass approval rate to nearly automatic by following a short routine before you submit. None of these steps is complicated; the value is in doing all of them every time rather than submitting on instinct and hoping. Here is the five-step routine we use.

1. Pick the category honestlyRun the message through the utility-versus-marketing test above. Choosing correctly here prevents the most common rejection and the most common post-approval re-categorization.
2. Write the body as a real sentenceWrap every variable in normal text so the message reads clearly with the blanks filled and even when they are empty. Avoid all caps, walls of emojis, and clickbait urgency.
3. Add sample values for every variableGive the reviewer example content for {{1}}, {{2}}, and so on. Missing samples are an easy, avoidable rejection, and good samples show the reviewer exactly what the message becomes.
4. Include a footer and opt-out where relevantFor marketing templates, add a clear opt-out such as reply STOP to unsubscribe. It signals good practice and protects your quality rating over time.
5. Proofread against policy, then submitRead it once as a customer and once against WhatsApp Business policy. Remove anything misleading, restricted, or borderline. Then submit and track the status.

Personalization and variables done right

Variables are what make one approved template feel like a personal message. Used well, they turn a generic shell into something that reads as if you wrote it for one person. Used carelessly, they produce awkward messages like Hi , your order is ready — the empty name that instantly signals automation. The difference is in how you set up and fall back on your data.

The rule of thumb is to personalize with information the customer expects you to have and would find useful: their name, their order number, the item, the date, the amount. Avoid stuffing variables for the sake of it. A message with a name and one relevant detail feels personal; a message with six variables feels like a form letter with the blanks showing.

There is also a timing dimension to personalization that copy alone cannot solve. A variable is only as good as the data behind it at the instant you send. If your shipping status is pulled at send time, the tracking line is accurate; if it is copied from a stale export, the customer sees yesterday's status and trusts you a little less. This is why the strongest template programs treat personalization as a live data pipeline into a fixed, approved shell — the words are locked by Meta, but the values stay fresh — rather than as a one-time mail merge you run and forget.

• Always set a fallback for name variables, so an empty field does not produce Hi , — use a neutral default like there.
• Keep variable count low; two or three meaningful variables beat six shallow ones.
• Put variables inside sentences, never as a naked body, both for approval and readability.
• Match the data source to the moment so the value is current — a stale order status reads worse than none.
• Test with real and empty values before you send at scale, so every fallback behaves as intended.

Opt-in: the rule you cannot template your way around

No template, however well written, exempts you from opt-in. Before you send any template — utility or marketing — the recipient must have opted in to receive messages from your business on WhatsApp. Meta is explicit about this in its business and developer documentation, and enforcement runs through both review and ongoing quality monitoring based on how users react to your messages. You can read the platform's own framing on the official WhatsApp Business site and the developer WhatsApp Business Platform docs.

Opt-in can be collected in many ways — a checkbox at checkout, a keyword the customer texts you, a form, a click-to-WhatsApp ad — but it must be clear, specific, and logged. Marketing opt-in is a higher bar than utility: a customer agreeing to order updates has not necessarily agreed to promotions. Keep the two consents distinct so your marketing list is genuinely people who asked to hear offers.

The payoff for taking opt-in seriously is not just compliance; it is performance. A list of people who chose to hear from you reads, clicks, and buys at rates a scraped or assumed list never will. And because WhatsApp scores your quality on how users respond, a clean list protects your ability to send at all. For campaign-level detail, see our guide to WhatsApp broadcasts and how a WhatsApp newsletter is built on real consent.

1. Ask clearly and separatelyUse a distinct checkbox or keyword for WhatsApp messaging, and separate marketing consent from transactional consent so each is unambiguous.
2. Log the consentRecord when, where, and how each contact opted in. If your quality is ever questioned, this record is what backs you up.
3. Honor opt-out immediatelyWhen someone replies STOP or asks to leave, remove them promptly. Fast, reliable opt-out is both required and good for your standing.

How does template pricing work, honestly?

Approval gets a template live; pricing decides what it costs to use. Meta charges for template messages, and the amount depends on the category and the country you are messaging into. Broadly, authentication, utility, and marketing are priced differently, and marketing typically costs more than utility. Rates and the exact billing model have changed over time — Meta has moved between conversation-based and per-message pricing — so the only reliable figure is the current one on Meta's own page.

We are deliberately not quoting per-message rates here, because a number that is stale is worse than no number: you would budget wrong. Instead, check the official WhatsApp pricing documentation for your destination countries and message categories before you plan spend. This is also why category discipline matters financially: mislabeling marketing as utility is not only a policy risk, it distorts your cost model.

A practical way to think about template spend is to separate the two levers you control from the one you do not. You control which category each message honestly falls into, and you control volume and audience — sending fewer, better-targeted messages to a genuinely opted-in segment beats blasting your whole list and paying for messages that get ignored or reported. What you do not control is Meta's rate card, which is why the discipline is to design the program to minimize wasted sends and then accept the per-message fee as a fixed input. Teams that measure cost per outcome, not cost per message, tend to make far better decisions about which templates are worth sending at all.

• Category affects price — authentication, utility, and marketing are billed differently.
• Destination country affects price — the same template costs different amounts by market.
• The billing model itself has changed over time, so verify the current structure, not last year's.
• These are Meta's fees and apply on any platform you use to send WhatsApp, including KlyoChat.

How KlyoChat helps you manage templates and broadcasts

Once you have a template library, the work shifts to managing it: submitting templates, tracking approvals, personalizing at send time, choosing who receives what, and reading the results. This is the part KlyoChat is built for. KlyoChat is an AI-native unified inbox that brings WhatsApp together with your other channels, and it includes template management, broadcasts, and segments so the whole lifecycle lives in one place.

Inside KlyoChat you build and submit templates from the template manager, track their approval status, and reuse approved templates across campaigns. When you are ready to send, broadcasts let you personalize with contact fields, target a segment rather than your whole list, and schedule the send — then analytics show delivery and engagement so you learn what works. The AI-native inbox handles the replies those templates generate, drafting and triaging across channels.

Being honest about limits, because you should hear them before you decide: templates still need Meta approval and valid opt-in on KlyoChat, exactly as they do anywhere — no tool can bypass Meta's review or consent rules. Category still affects Meta's per-message fees, which are charged by Meta regardless of platform. KlyoChat also does not send native SMS or email, so if those channels are core to your plan, factor that in. And we are a newer, smaller community than the largest incumbents, which some teams weigh. See real numbers on our pricing page.

That is the library: 40 WhatsApp template examples across utility, marketing, and authentication, plus the rules that decide whether they get approved and what they cost. The examples give you a running start, but the durable wins come from the discipline around them — honest categorization, variables wrapped in real text, a footer and opt-out where they belong, and opt-in you can stand behind. Copy what fits, adapt it to your brand, and submit early so your library is ready before you need it.

From here, deepen the parts that matter most to you: walk the full review process in our template approval guide, plan your first send with the broadcast guide, and see how consent-first sending scales in our WhatsApp newsletter piece. Then verify current pricing on Meta's own page and build your library once, properly, so every future campaign starts from approved copy rather than a blank box.