# Transactional SMS in India: DLT Compliant Alerts and Updates

> Transactional SMS in India sends time-sensitive updates like order confirmations, delivery alerts and OTPs to your customers through a registered DLT sender ID. Com.Bot handles DLT compliant one-way SMS alongside WhatsApp, RCS and web chat in one platform.

Source: https://com.bot/sms/transactional-sms/ | Publisher: Com.Bot (Com Bot AI Limited), Official Meta Business Partner | Updated: October 2026

## Key takeaways
- Transactional SMS in India sends order, delivery, appointment and OTP updates through a registered DLT sender ID.
- Com.Bot handles DLT compliant one-way SMS alongside WhatsApp, RCS and web chat in one platform.
- SMS is one-way only in India, so include a wa.me link or phone number for customers who want to reply.

## Highlights
- **Fully DLT compliant:** Entity, sender ID and every template are registered on a DLT platform before you send. Com.Bot supports the full TRAI process.
- **One-way and reliable:** Customers receive your message without needing an app. When they need to respond, you point them to a link, a phone number or a wa.me WhatsApp link.
- **No monthly conversation cap:** Send as many transactional SMS as your business needs. There is no FUP limit on your Com.Bot plan.
- **One inbox for every channel:** SMS sits beside WhatsApp, Instagram, Messenger, Google RCS and your website chat widget so your team manages everything in one place.

## Use cases
### 1. Order confirmation SMS
A D2C brand confirms a new order within seconds of checkout. The customer gets the order number, amount and a wa.me link for support.
- Luma Skincare: LUMASK: Order 4821 confirmed. 2 items, Rs 1,498. Delivery in 3 to 5 days. Track or chat: wa.me/919000000000

### 2. Delivery out for dispatch
A logistics update reaches the customer on the morning of delivery. It cuts failed deliveries and support calls about where the parcel is.
- Nirav Home Decor: NIRAV: Order 7712 is out for delivery today between 10 AM and 1 PM. Keep your phone reachable. Need help? wa.me/919000000000

### 3. Appointment reminder SMS
A clinic reminds patients about tomorrow's booked slot. Fewer no-shows mean the schedule stays full without manual calls.
- Sharma Clinic: SHARMACLINIC: Reminder, your appointment with Dr. Sharma is tomorrow at 11:30 AM. To reschedule, call 080 6987 1810.

### 4. Payment due alert
A service business sends a payment reminder for an existing order. The customer gets a clear amount and a link to pay.
- Brightpath Academy: BRIGHTPATH: Fee of Rs 4,500 for course batch B12 is due on 28 Feb. Pay online: wa.me/919000000000

### 5. OTP for login
An authentication SMS delivers a one-time passcode for account login. It reaches customers on any phone, no app needed.
- Kavach Insurance: KAVACH: 482913 is your OTP to log in. Valid for 10 minutes. Do not share it with anyone.

### 6. COD order confirmation
A store confirms a cash on delivery order and the amount payable. The customer knows exactly what to keep ready at the door.
- Rangoli Sarees: RANGOLI: COD order 3390 confirmed. Pay Rs 2,199 on delivery. Delivery in 4 to 6 days. Questions? wa.me/919000000000

## What is transactional SMS in India?
**Short answer:** Transactional SMS in India is a one-way text message that updates a customer about a transaction or account they already started or requested, such as order confirmations, delivery updates, payment reminders, appointment confirmations and one-time passcodes. It is sent from a registered six-character sender ID, can reach DND numbers, and on Com.Bot is available only in India and fully DLT compliant.

Transactional SMS in India is a one-way text message that updates a customer about a transaction or account they already started or requested. Common examples include order confirmations, shipping and delivery updates, payment due reminders for an existing order, appointment confirmations and one-time passcodes. These messages are sent from a registered six-character sender ID, also called a header, such as LUMASK, so the customer sees a consistent business identity instead of a random number.

Because transactional SMS carries service information rather than promotion, it can reach numbers that are on the DND registry. That makes it a dependable channel for updates that a customer expects and needs. On Com.Bot, transactional SMS is available only in India and is fully DLT compliant under TRAI rules. It is one-way: the customer cannot reply to the SMS, so any message that needs a response should include a link, a phone number or a wa.me WhatsApp link.

Transactional SMS works best as a notification layer, not a conversation layer. Pair it with a channel where customers can actually talk back, like WhatsApp, and you cover both delivery and dialogue.

- Order confirmation and invoice sent
- Shipping and out for delivery updates
- Payment due for an existing order
- Appointment confirmation and reminder
- One-time passcodes for login or payment
- Service alerts for an account the customer holds

## Why transactional SMS still works for Indian businesses
**Short answer:** Transactional SMS works for Indian businesses because it reaches every phone without a data connection, app install or smartphone, and arrives in the default messaging app that most people check within minutes. Service and OTP messages can also reach DND numbers, making it a dependable notification rail that pairs well with WhatsApp for two-way follow-up.

SMS reaches every phone. It does not need a data connection, an app install or a smartphone. For a customer waiting on a delivery or a payment reminder, that reliability matters. A transactional SMS arrives in the default messaging app, which most people check within minutes. For a D2C brand shipping thousands of orders a month, or a coaching institute confirming class schedules, that immediacy reduces support tickets and missed appointments.

Transactional SMS also carries a compliance advantage. Because service and OTP messages can go to numbers on the DND registry, you are not limited to a subset of your customer base for updates they have already opted into through a purchase or a booking. The message category is registered on the DLT platform, so the intent of the message is clear to the operator and to the customer.

The channel is not a replacement for WhatsApp or RCS. It is a dependable notification rail. When a customer needs to choose a delivery slot, confirm an appointment or ask a question, point them to WhatsApp with a wa.me link. Com.Bot keeps both channels in one inbox so your team sees the full history.

- Works on every phone without an app or data plan
- Service and OTP messages can reach DND numbers
- Registered sender ID builds trust and recognition
- Ideal for high-volume order and appointment updates
- Pairs with WhatsApp for two-way follow-up

## How to set up transactional SMS in Com.Bot
**Short answer:** Setting up transactional SMS in Com.Bot starts with DLT registration of your business entity, six-character sender ID and every message template, using the {#var#} variables DLT requires. You then connect your sender ID to Com.Bot and build sending flows in the automation builder, which connects to 1,000+ integrations, or send from the shared inbox or CRM.

Setup starts with DLT registration. Your business entity, your six-character sender ID and every message template must be registered on a DLT platform before you send. Com.Bot guides you through the process and helps you prepare templates with the {#var#} variables that DLT requires. Once approved, you connect your sender ID to Com.Bot and your transactional SMS channel is ready.

Inside Com.Bot, you build the sending flow. You can trigger an SMS from the automation builder when an order is placed, when a payment is due or when an appointment is booked. The automation builder connects to 1,000+ integrations, so your ecommerce platform, CRM or booking tool can fire the message automatically. You can also send from the shared team inbox or through the contacts CRM when a one-off update is needed.

Every message is plain text and fits 160 GSM characters per segment. If your template runs longer, it is split into multiple segments. Keep transactional messages short, specific and free of promotional language. The customer should know exactly what happened and what to do next, if anything.

- Register entity, header and templates on DLT
- Connect your sender ID to Com.Bot
- Build triggers in the automation builder
- Use {#var#} variables for names, order IDs and dates
- Send from the inbox or CRM for one-off updates
- Keep each message under 160 characters per segment

## DLT rules and compliance for transactional SMS in India
**Short answer:** DLT registration is mandatory for transactional SMS in India: the business entity, sender ID and every template must be registered before delivery. Templates use {#var#} variables, and the category (promotional, transactional or service, or OTP) is registered too. Transactional and service messages can reach DND numbers; promotional SMS only goes to non-DND numbers within TRAI-permitted hours.

DLT registration is mandatory. The business entity, the sender ID and every template must be registered before a message can be delivered. Templates use {#var#} variables for dynamic content such as a customer name, an order number or a delivery date. The message category is also registered: promotional, transactional or service, and OTP. Transactional and service messages can go to all numbers, including those on the DND registry, because they relate to a transaction the customer already started.

Promotional SMS follows different rules. It goes only to numbers not on the DND or NCPR registry and only within TRAI-permitted hours. If you are sending an offer, a cart reminder or a re-engagement message, that is promotional, not transactional. Registering a promotional message as transactional is a compliance risk and can get your sender ID blocked. Keep the categories honest.

Com.Bot SMS is one-way. Customers cannot reply to the SMS, so there are no keyword replies, no STOP replies and no SMS inbox. If a customer needs to respond, your message should include a link, a phone number or a wa.me WhatsApp link. This is a channel rule, not a limitation you can work around. Design every transactional SMS with that in mind.

- Register entity, header and templates on DLT
- Use {#var#} variables in every template
- Transactional and service messages can reach DND numbers
- Promotional SMS only to non-DND numbers in permitted hours
- One-way only: no replies, no keywords, no STOP
- Include a link, phone number or wa.me link when a response is needed

## SMS vs WhatsApp vs RCS: when to use which
**Short answer:** Use transactional SMS for short, time-sensitive updates that must reach every phone, WhatsApp when the customer needs to reply or continue a conversation, and Google RCS for rich branded messages on supported Android devices. Com.Bot lets you include a wa.me link in SMS to move customers into WhatsApp, and manage SMS, WhatsApp and RCS from one shared inbox.

Use transactional SMS when the message is a short, time-sensitive update that must reach every phone, including feature phones and numbers without data. Order confirmations, delivery alerts, payment reminders for an existing order and OTPs fit here. SMS is plain text, one-way and dependable. It is the notification rail that works when nothing else does.

Use WhatsApp when the customer needs to reply, choose an option or continue a conversation. WhatsApp Business API supports approved templates for business-initiated messages and opens a 24-hour customer service window when the customer replies. That window is where free-form conversation happens. For a delivery reschedule, a product question or a payment confirmation, WhatsApp is the better channel. Com.Bot lets you include a wa.me link in your SMS so the customer lands directly in your WhatsApp thread.

Use Google RCS when you want a rich, branded message with images, carousels and suggested reply buttons in the default messaging app on supported Android phones. RCS is useful for visual updates and interactive notifications, but it depends on carrier and device support. Many businesses run SMS for reach, WhatsApp for conversation and RCS for rich engagement, all from the same Com.Bot inbox. You choose the channel for each message.

- SMS: short updates to every phone, one-way
- WhatsApp: two-way conversation and rich templates
- RCS: branded rich messages on supported Android devices
- Use wa.me links in SMS to move customers to WhatsApp
- Manage all channels from one shared inbox

## Mistakes to avoid with transactional SMS
**Short answer:** The biggest transactional SMS mistake is sending promotional content through a transactional template, which is a compliance violation and can get your sender ID blocked. Other common errors include asking customers to reply or send STOP when SMS is one-way, writing messages longer than 160 GSM characters per segment, and sending late at night unless the update is truly urgent.

The most common mistake is sending promotional content through a transactional template. A discount offer, a cart reminder or a back-in-stock alert is marketing, not a transaction update. Registering it as transactional is a compliance violation and can get your sender ID blocked. Keep marketing on the promotional category, follow DND rules and permitted hours, and reserve transactional templates for messages the customer already expects.

The second mistake is forgetting that SMS is one-way. If your message asks the customer to reply YES or STOP, they cannot. There is no reply keyword, no STOP reply and no SMS inbox. Every call to action must be a link, a phone number or a wa.me WhatsApp link. If you need a confirmation, send the customer to WhatsApp or a web page where they can act.

The third mistake is writing long messages. SMS is plain text and 160 GSM characters per segment. Long messages split into multiple segments, which costs more and reads poorly. Keep it short: what happened, what it means, what to do next. Also avoid sending at odd hours. Even though transactional SMS is not bound by promotional hours, a 2 AM delivery update feels intrusive. Schedule sends for reasonable hours unless the update is truly urgent.

- Do not use transactional templates for offers or cart reminders
- Do not ask customers to reply or send STOP
- Always include a link, phone number or wa.me link
- Keep messages under 160 characters per segment
- Avoid late-night sends unless the update is urgent
- Match the DLT category to the real intent of the message

## How the three channels compare for Indian businesses, based on what each channel supports today.
| Channel | Best for | Reply handling |
|---|---|---|
| Transactional SMS | Order, delivery, payment and OTP alerts to any mobile number | One-way only. Include a wa.me link or phone number for replies. |
| WhatsApp | Two-way support, order updates, offers and payment collection | Customers reply in the 24-hour service window; free-form replies allowed. |
| Google RCS | Rich branded updates with images, carousels and buttons | Customers can tap suggested replies and action buttons. |
| DLT registration | Required before any SMS send in India | Entity, sender ID and every template are registered on a DLT platform first. |
| Promotional SMS | Offers and re-engagement, not transactional updates | Goes only to numbers not on DND and within TRAI permitted hours. |

## How to set it up in Com.Bot
1. **Register on DLT:** Register your business entity, your six-character sender ID and your message templates on a DLT platform. Com.Bot helps you prepare templates with {#var#} variables and the correct category.
2. **Connect your sender ID:** Once approved, connect your DLT sender ID to Com.Bot. Your transactional SMS channel is ready to send from the shared inbox or automation builder.
3. **Build your automation:** Use the automation builder to trigger an SMS when an order is placed, a payment is due or an appointment is booked. Connect your ecommerce, CRM or booking tool through 1,000+ integrations.
4. **Add a WhatsApp path:** Include a wa.me WhatsApp link in every SMS where the customer may need to respond. This moves the conversation to a channel where they can actually reply.
5. **Track and refine:** Monitor delivery and response patterns in Com.Bot. Shorten templates, adjust send times and move conversational updates to WhatsApp where they perform better.

## Message templates
**Order confirmation** (n/a)
> LUMASK: Order {#var#} confirmed. Total Rs.{#var#}. Track: lumask.in/t/{#var#}

**Delivery update** (n/a)
> LUMASK: Order {#var#} out for delivery today. Keep phone reachable. Reschedule: wa.me/919000000000

**Payment due reminder** (n/a)
> LUMASK: Payment of Rs.{#var#} for order {#var#} is due on {#var#}. Pay: lumask.in/pay/{#var#}

## Frequently asked questions
### What is transactional SMS in India?
Transactional SMS in India is a one-way text message that updates a customer about a transaction or account they already started or requested. Examples include order confirmations, delivery updates, payment reminders for an existing order, appointment confirmations and OTPs. It is sent from a registered six-character DLT sender ID and can reach numbers on the DND registry.

### Is transactional SMS different from promotional SMS?
Yes. Transactional SMS carries service information about a transaction the customer already started, so it can go to all numbers including DND numbers. Promotional SMS carries offers and marketing, so it goes only to numbers not on the DND registry and within TRAI-permitted hours. Registering a promotional message as transactional is a compliance risk.

### Can customers reply to transactional SMS from Com.Bot?
No. Com.Bot SMS is one-way. Customers cannot reply to the SMS, and there are no keyword replies, no STOP replies and no SMS inbox. If a customer needs to respond, include a link, a phone number or a wa.me WhatsApp link in the message so they can continue on a channel that supports replies.

### What is DLT registration and why is it required?
DLT registration is the process of registering your business entity, your six-character sender ID and every message template on a DLT platform before sending SMS in India. It is required under TRAI rules. Templates use {#var#} variables and are registered under a category: promotional, transactional or service, and OTP.

### Can transactional SMS reach DND numbers?
Yes. Transactional and service messages can go to all numbers, including those on the DND or NCPR registry, because they relate to a transaction the customer already started or requested. Promotional SMS cannot go to DND numbers and is limited to TRAI-permitted hours.

### When should I use SMS instead of WhatsApp?
Use SMS when the message is a short, time-sensitive update that must reach every phone, including feature phones and numbers without data. Use WhatsApp when the customer needs to reply, choose an option or continue a conversation. You can include a wa.me link in your SMS to move the customer to WhatsApp for two-way follow-up.

### How much does transactional SMS cost on Com.Bot?
Com.Bot plans are priced per quarter, not per month. Silver is $149 per quarter, Gold is $349 per quarter and Platinum V1 is $2,500 per quarter. India pricing is Rs.10,000, Rs.23,000 and Rs.1,80,000 per quarter. SMS message charges are billed separately from the plan. Contact the Com.Bot team for current SMS rates.

---
Com.Bot: WhatsApp Business API, Instagram, Messenger, Google RCS and SMS automation. Official Meta Business Partner. Plans from $149 per quarter. Start: https://v3.com.bot/register