If you’re sending WhatsApp messages through the WhatsApp Business Platform, choosing the right template category can feel surprisingly complicated.
You write a message that looks transactional, submit it as Utility, and it gets rejected.
You add a URL to a Marketing template and suddenly delivery becomes a problem.
You want to send a simple OTP, but your template somehow ends up in the wrong category.
Or you build a perfectly good template and later discover that a feature such as Copy Code is only available for Authentication messages.
The important thing to understand is this:
WhatsApp template categories are not just labels. They determine what your message is allowed to contain and how WhatsApp evaluates it.
In this guide, we'll break down Marketing, Utility, and Authentication templates, the common mistakes businesses make, and how to choose the right category before submitting a template.
The three WhatsApp template categories
WhatsApp Business Platform templates are broadly divided into three categories:
| Category | Primary purpose | Typical examples |
|---|---|---|
| Marketing | Promotion, engagement, or persuasion | Offers, product announcements, abandoned carts, re-engagement |
| Utility | A specific transaction, request, or customer action | Order updates, booking confirmations, account notifications |
| Authentication | Verifying a user's identity | OTPs, login codes, account verification |
The category should follow the actual purpose of the message.
Not the button you want to add.
Not the audience you're sending it to.
Not the fact that the message is triggered automatically.
And not simply because your business considers it "transactional."
1. Marketing templates
Marketing messages are designed to promote, persuade, engage, or encourage a customer to take an action.
This includes much more than traditional advertisements.
Common Marketing examples
Promotional offer:
Get 20% off your next order. Use code SAVE20 before Sunday.
Product announcement:
Our new collection is here. Explore the latest arrivals today.
Re-engagement:
We haven't seen you in a while. Come back and discover what's new.
Cross-sell:
Customers who purchased your laptop also loved these accessories.
These messages may be sent automatically, but that doesn't make them Utility.
If the objective is to encourage a purchase, engagement, or return visit, Marketing is generally the appropriate category.
URLs are commonly used in Marketing messages
A frequent mistake is assuming that adding a URL automatically makes a template Utility.
It doesn't.
For example:
Your order has been delivered. Track your package at example.com/track/12345.
This is potentially a Utility message because it relates directly to a specific transaction.
Compare that with:
Explore our latest products at example.com/new.
That's promotional content, so it belongs in the Marketing category.
The URL itself isn't what determines the category.
The context and purpose of the message matter.
2. Utility templates
Utility messages are intended to provide specific, expected information related to an existing transaction, account, request, or service.
Think of Utility messages as:
"Something happened with something you already did."
Common Utility examples
Order confirmation:
Your order #12345 has been confirmed and is being prepared for shipment.
Shipping update:
Your order #12345 has been shipped. Expected delivery: October 6.
Appointment reminder:
Reminder: Your appointment with Dr. Sharma is scheduled for October 6 at 11:00 AM.
Booking confirmation:
Your hotel booking at ABC Hotel is confirmed for October 10–12.
Payment notification:
Your payment of ₹2,499 for order #12345 was successfully received.
These messages are not trying to sell something. They're communicating information about an existing customer interaction.
The biggest Utility mistake: "It's automated, so it's transactional"
This is one of the most common misunderstandings.
A message being triggered by your backend does not automatically make it Utility.
For example:
Your cart is waiting! Complete your purchase today and get 15% off.
Your system may send this automatically when someone abandons their cart.
But the message is encouraging the customer to complete a purchase and includes a promotional incentive.
That's fundamentally different from:
You left 3 items in your shopping cart. You can review your cart here: example.com/cart/123.
The first message contains a promotional element. The second is primarily informational.
Automation ≠ Utility
Your code can trigger a message automatically and it can still be Marketing.
The category is determined by what the customer is being told and why.
3. Authentication templates
Authentication templates are designed specifically for user verification.
The most common example is an OTP.
For example:
Your verification code is 482913.
Or:
Use 482913 to verify your phone number.
Authentication templates are designed around a very specific purpose: helping the user authenticate or verify their identity.
They aren't intended for promotional content, product recommendations, or general notifications.
Why Authentication is different
Authentication templates have specific components designed around verification flows.
One particularly useful feature is Copy Code.
Instead of forcing the user to manually type an OTP, an Authentication message can provide a button that lets the user copy the verification code.
For example:
Your verification code is 482913
[ Copy Code ]
This makes Authentication templates particularly useful for:
- Login verification
- Phone number verification
- Account registration
- Password recovery
- Two-factor authentication
- Identity verification
The "Copy Code" trap
Here's a situation that catches developers regularly.
You have a message like:
Your login code is {{1}}. Enter this code to continue.
You create it as a Utility template because it's a system-generated message.
Then you discover that you want a Copy Code button.
That's where the category matters.
Copy Code is associated with Authentication templates, not ordinary Utility templates.
So you can't simply take an existing Utility OTP template and expect Authentication-specific functionality to become available.
If the message is genuinely an authentication message, create it as an Authentication template from the beginning.
So how do I choose the category?
A simple way to think about it is:
Ask what the message is trying to accomplish.
Is it promoting or encouraging something?
→ Marketing
Is it communicating information about an existing transaction, request, appointment, account, or service?
→ Utility
Is it verifying the user's identity or providing a verification code?
→ Authentication
Here's where things get confusing
Consider these three messages.
Message 1
Your order #12345 has been shipped. Track it here: example.com/track/12345
Likely category: Utility
The URL provides information about an existing order.
Message 2
Your order has shipped! You can also explore our new products here: example.com/new
Likely category: Marketing
The additional promotional content changes the purpose of the message.
Message 3
Your login verification code is 482913.
Category: Authentication
The message exists specifically to verify the user.
The important part is that small changes in the message can change how the message should be categorized.
The problem with "transactional-sounding" copy
Businesses often try to make promotional messages sound transactional.
For example:
Your account is eligible for our exclusive 30% discount. Claim it now.
It might sound like an account notification.
But the actual purpose is promotional.
Similarly:
Your order is ready. Complete your payment now to receive an additional 10% discount.
The first part sounds transactional, but the discount introduces a promotional objective.
This is why simply using words such as:
- "Your account"
- "Your order"
- "Your payment"
- "Your booking"
- "Your subscription"
doesn't automatically make a message Utility.
The overall intent and content matter.
Another common mistake: putting promotional content inside Utility templates
Let's say you send:
Your subscription will renew on October 10 for ₹999.
Renew today and get an additional 20% discount.
The first sentence is a legitimate account notification.
The second sentence introduces a promotional incentive.
Trying to squeeze promotional content into an otherwise Utility message can create a category mismatch.
If the message contains marketing content, consider whether the entire template should actually be Marketing rather than trying to make a Marketing message look like Utility.
What about URLs?
URLs themselves aren't automatically Marketing.
This is an important distinction.
Utility
Your invoice for order #12345 is ready. View your invoice at example.com/invoice/12345.
The URL supports the transaction.
Marketing
Check out our latest collection at example.com/collection.
The URL is part of a promotional call-to-action.
Authentication
Authentication messages can have their own specific authentication components and restrictions.
So don't use this rule:
"URL = Marketing"
Instead, ask:
"Why is the user receiving this URL?"
If it's to access information about an existing transaction, it can be part of a Utility message.
If it's to discover, purchase, or engage with something promotional, it's Marketing.
A practical decision tree
Before creating a template in Samvad, ask these questions:
Step 1 — Is this about verifying the user's identity?
Yes → Authentication
Examples:
- OTP
- Login verification
- Phone verification
- Password reset verification
No → Continue.
Step 2 — Is the message related to something the user has already done or requested?
Yes → Consider Utility
Examples:
- Order
- Payment
- Booking
- Appointment
- Delivery
- Account update
No → Continue.
Step 3 — Is the message trying to promote, sell, re-engage, recommend, or persuade?
Yes → Marketing
Examples:
- Discounts
- Offers
- New products
- Recommendations
- Re-engagement
- Promotional campaigns
Don't choose a category based on your backend workflow
Your application might have code like:
if order_status == "shipped":
send_whatsapp_message()That doesn't automatically mean the template is Utility.
Likewise:
if user_has_not_purchased_in_30_days:
send_whatsapp_message()That doesn't automatically mean it's Utility either.
The backend event tells you when the message is sent.
The message itself tells you what category it belongs to.
That's an important distinction when designing WhatsApp messaging systems.
What happens when you choose the wrong category?
A category mismatch can create several problems.
Your template may:
- Be rejected during review
- Be categorized differently
- Lose access to category-specific components
- Require you to create a new template
- Cause confusion when designing your messaging workflow
- Make an otherwise valid messaging flow unnecessarily difficult
And in some cases, you don't discover the problem until you're already building your campaign or notification flow.
That's why category selection should happen before you finalize the template.
A simple cheat sheet
| If your message is... | Use |
|---|---|
| Promotional offer | Marketing |
| Product announcement | Marketing |
| Re-engagement | Marketing |
| Product recommendation | Marketing |
| Order confirmation | Utility |
| Shipping update | Utility |
| Appointment reminder | Utility |
| Booking confirmation | Utility |
| Payment notification | Utility |
| Account-related notification | Utility |
| Login OTP | Authentication |
| Phone verification code | Authentication |
| Account verification code | Authentication |
The easiest rule to remember
If you remember only one thing from this article, remember this:
Marketing asks the customer to consider something. Utility tells the customer something they need to know. Authentication proves who the customer is.
And don't try to make one category behave like another.
A promotional message doesn't become Utility because it's automatically triggered.
An OTP doesn't become Utility because it's a system notification.
A URL doesn't automatically make a message Marketing.
And an Authentication template isn't simply a Utility template with an OTP inside it.
The category should follow the actual purpose and content of the message.
Building WhatsApp templates with Samvad?
Samvad helps businesses create and manage WhatsApp Business Platform templates, campaigns, notifications, and customer conversations from one place.
If you're unsure whether a message should be classified as Marketing, Utility, or Authentication, start by looking at the message's actual intent, not the workflow that triggered it.
Getting the category right at the beginning can save you from template rejections, redesigning message flows, and discovering category restrictions after you've already built your campaign.