SMS

Transactional vs Promotional SMS (2026): Key Differences, Use Cases & Compliance

8 min read

If you've ever had an SMS campaign rejected mid-send, or an OTP delivered to only 60% of your users, the answer is usually the same: wrong route.

India's SMS infrastructure runs on two separate tracks — transactional and promotional — and TRAI enforces the separation strictly. The distinction isn't just regulatory paperwork. It determines whether your message reaches a DND number or not, whether it can be sent at 2am or not, and whether a template mismatch silently kills your entire send.

Transactional-vs-Promotional SMS

This guide cuts straight to what you need to know.

One-Line Answer

Transactional SMS = messages your customer needs (OTPs, alerts, confirmations) — delivered 24/7, reaches DND numbers.

Promotional SMS = messages your business wants to send (offers, campaigns) — restricted to 9am–9pm, blocked on DND numbers.

The Practical Difference: A Decision Table

Before diving into rules and compliance, here's the fastest way to decide which route your message belongs on:

If your message is...

Route

An OTP or verification code

Transactional (OTP)

An order confirmation

Transactional

A payment alert or bank notification

Transactional

An appointment reminder

Transactional

A delivery status update

Transactional

A welcome message after signup

Transactional

A Diwali sale offer

Promotional

A product launch announcement

Promotional

A discount or coupon

Promotional

A re-engagement campaign

Promotional

A feedback or referral request

Promotional

One rule of thumb that never fails: if removing the message would inconvenience the user, it's transactional. If the user wouldn't notice it missing, it's promotional.

Transactional SMS: What It Is and How It Works

Transactional SMS is for service communication — messages that arise from an action the customer took or a status that directly affects them. The defining characteristic isn't just the content; it's the intent. The message exists to serve the user, not to sell to them.

What it can do that promotional cannot:

  • Delivered 24 hours a day, 7 days a week

  • Reaches DND-registered numbers — consent is implied by the existing customer relationship

  • Higher delivery priority on operator networks

  • Alphabetic sender ID (e.g., VM-HDFCBK, TM-SWGGY)

Common use cases: OTP verification, transaction confirmations, account alerts, appointment reminders, order status updates, delivery notifications, password reset codes, EMI payment reminders.

The OTP use case is a specific sub-category of transactional — most quality providers offer a dedicated OTP route (messageType: 3 in API) with separate throughput and sub-5-second delivery SLA. How OTP SMS delivery works in India — including why OTPs fail and how to build reliable multi-channel verification — is worth reading separately from this route distinction.

Cost: Typically ₹0.10–₹0.20/SMS from Tier-1 providers. Slightly higher than promotional due to priority routing and DND bypass capability.

Promotional SMS: What It Is and How It Works

Promotional SMS is for outbound marketing — reaching customers (and potential customers) with messages they didn't specifically request. The trade-off for that outreach capability is tighter restrictions.

What you need to know before sending:

  • Only between 9am and 9pm — not a soft guideline, a TRAI mandate enforced at operator level

  • DND-registered numbers are blocked — depending on your list, this can be 20–40% of your audience

  • Numeric or brand-format sender ID (e.g., DM-SHOPIT, VM-BRAND)

  • Templates must be pre-approved on DLT portal

Common use cases: Festive sale campaigns, product launches, flash offers, re-engagement flows, event invitations, loyalty program updates.

Cost: Typically ₹0.08–₹0.15/SMS — cheaper than transactional because delivery priority is lower and DND numbers are filtered out. For a full breakdown of bulk SMS pricing in India across both route types, including volume tiers and GST, the numbers are there in detail.

Head-to-Head Comparison

Feature

Transactional

Promotional

Delivery hours

24/7

9am–9pm only

DND numbers

Reaches DND

Blocked on DND

Sender ID format

Alphabetic (VM-BRAND)

Numeric or brand header

Delivery priority

High

Standard

Cost per SMS

₹0.10–₹0.20

₹0.08–₹0.15

DLT template required

Yes

Yes

Best for

OTPs, alerts, confirmations

Campaigns, offers, outreach

Where Most Businesses Go Wrong

Sending promotional content on the transactional route. This is the most common violation — and it's tempting because transactional routes reach DND numbers and work all hours. TRAI monitors for this. Getting caught risks your sender ID being flagged and blocked, which affects all your messaging, not just the offending campaign.

A "welcome message after signup" with a discount coupon in it is promotional, not transactional — regardless of what triggered it. The moment a message contains an offer, it moves to promotional territory.

Sending OTPs on a promotional route. OTPs fail silently to DND numbers on promotional routes. If 30% of your users are DND-registered, 30% of your OTP sends simply disappear. Users assume the product is broken. SMS delivery failures in India are caused by this more often than by any technical issue.

Template mismatch after content changes. A registered DLT template must match your actual message exactly — variable fields are the only permitted deviation. If you change the message copy without updating the DLT template, every message is rejected at the operator level. It looks like a successful send in your platform dashboard. Nothing reaches the user.

Not accounting for DND in promotional volume estimates. If your contact list has 1,00,000 numbers and 30% are DND-registered, your effective promotional reach is 70,000. Buying credits for 1,00,000 sends when only 70,000 will deliver is wasted spend.

DLT Compliance: What Both Routes Require

Both transactional and promotional SMS require DLT registration — there's no opt-out for either. The framework introduced by TRAI in 2020 requires every commercial SMS sender to register three things:

Entity registration — your business on the DLT portal. One-time process.

Sender ID (header) registration — every sender ID you use must be approved. Transactional and promotional sender IDs follow different format rules and must be registered separately.

Template registration — every message format needs a pre-approved template. Variables are permitted; deviations from the registered structure are not.

The complete DLT registration process in India — from entity registration through to template approval — walks through each step. The key operational implication: you cannot send a message on a new template the same day you create it. Build DLT approval time into your campaign calendar.

Using Both Routes Together: The Right Approach

The strongest SMS strategies for Indian businesses combine both routes — not as alternatives, but as complementary tools serving different parts of the customer relationship.

A bank sends transactional SMS for every account event (OTP, transaction alert, balance update) and promotional SMS for product announcements (new credit card, fixed deposit rates). The customer receives service messages on the transactional route whenever relevant, and marketing messages on the promotional route within the permitted window.

An e-commerce platform sends transactional order confirmation, shipping update, and delivery notification — then follows up with a promotional re-engagement campaign 30 days after purchase asking the customer to review or reorder. Two different routes, two different intents, one coherent customer communication strategy.

This is also why bulk SMS marketing in India and bulk SMS API integration are separate disciplines — the marketing strategy layer sits on top of the technical integration layer, and both need to be designed with route awareness built in.

API Integration: Route Selection in Code

When integrating via SMS API, route selection happens through the messageType parameter:

{
  "apiToken": "YOUR_TOKEN",
  "messageType": "3",
  "destinationAddress": "917006822667",
  "sourceAddress": "MBOTIN",
  "messageText": "Your OTP is 849201. Valid for 10 minutes.",
  "dltEntityId": "YOUR_DLT_ENTITY_ID",
  "dltEntityTemplateId": "YOUR_DLT_TEMPLATE_ID"
}

messageType: 1 = Promotional messageType: 2 = Transactional messageType: 3 = OTP (dedicated high-priority transactional sub-route)

Never auto-select route based on message content at the application layer — hardcode the correct type per message class and validate it during QA before deployment. A bug that accidentally routes OTPs on the promotional path won't show errors; it will silently fail for DND users and you'll discover it through support tickets.

Frequently Asked Questions

Can I send a promotional offer inside a transactional message?
No. If a message contains promotional content — an offer, a discount, a product recommendation — it must go through the promotional route regardless of what else is in the message. Mixing promotional content into a transactional message to bypass DND restrictions violates TRAI policy.

What happens if I send promotional SMS after 9pm?
The message is blocked at the operator level. It won't reach the recipient, and depending on your provider, may not be retried. Plan campaign sends to complete before 9pm — large sends near the cutoff risk partial delivery if processing time crosses the limit.

Can a transactional SMS be sent to a DND number?
Yes. DND filtering applies only to promotional SMS. Transactional messages — OTPs, alerts, confirmations — reach DND-registered numbers because the customer has an existing relationship with the sender that implies consent for service communication.

Why are my OTPs failing for some users but not others?
If your OTPs are on a promotional route, they'll fail for DND users — which can be 20–40% of your list. Check your messageType parameter. If it's set to 1 (promotional) when it should be 3 (OTP), that's the cause. Why OTP delivery fails in India covers all the failure modes including route mismatch.

Is DLT registration required for both routes?
Yes. Both transactional and promotional SMS require DLT entity registration, sender ID approval, and template pre-registration. There is no exemption for either route type.

Conclusion

The transactional vs promotional distinction in India isn't bureaucracy for its own sake — it's the mechanism that keeps SMS a trusted channel. When OTPs arrive reliably because they're on a dedicated high-priority route, and marketing messages don't reach people who've opted out, the whole ecosystem works better for everyone including the businesses sending the messages.

Get the classification right from the start. Register your templates before you need them. Keep promotional content out of transactional messages. Monitor your SMS delivery rates and DLR accuracy — route issues show up in DLR patterns before they show up in user complaints.

MessageBot handles both transactional and promotional SMS through a single API with full DLT automation and Tier-1 routing for Indian businesses. Explore Messagebot SMS service.

Share

Ready to Transform Your Business Communication?

Join thousands of Indian businesses already using MessageBot to engage customers effectively and drive business growth.

Free 100 SMS credits
24/7 support
TRAI compliant setup
No setup fees