Order and Delivery SMS in India for Growing Businesses

The complete guide

Order and Delivery SMS in India for Growing Businesses: everything you need to know

What is order and delivery SMS in India?

Short answer: Order and delivery SMS in India is a plain-text message about a transaction the customer already started or requested, such as an order confirmation, tracking link, out for delivery alert, COD confirmation or payment reminder. It falls under the transactional or service category on a DLT platform, so it can reach all numbers, including those on the DND registry. On Com.Bot, SMS is one-way.

Order and delivery SMS in India is a plain-text message a business sends to a customer about a transaction the customer already started or requested. It confirms an order, shares a tracking link, announces out for delivery, confirms cash on delivery or reminds the customer about a payment due. Because it is tied to a real transaction, it falls under the transactional or service category on a DLT platform, which means it can reach all numbers, including those on the DND registry.

On Com.Bot, SMS is one-way. The business sends, and the customer cannot reply to the SMS itself. There are no keyword replies and no SMS inbox. When a customer needs to respond, the message carries a link, a phone number or a wa.me WhatsApp link that opens a conversation on a channel where your team can actually answer.

This suits Indian businesses that already collect phone numbers at checkout: D2C brands, pharmacies, grocery sellers, coaching institutes, logistics partners and service businesses. SMS is simply another notification channel you choose to use alongside WhatsApp, Instagram, Messenger, Google RCS and your website chat widget.

• Order confirmation with order ID and amount
• Shipping and dispatch updates with a tracking link
• Out for delivery and delivered alerts
• COD confirmation and payment due reminders
• Appointment and booking reminders
• One-time passcodes for login and checkout

Why send order and delivery SMS in India on Com.Bot?

Short answer: Order and delivery SMS on Com.Bot reaches customers who may not have WhatsApp notifications on, and it works on every phone. Delivery alerts cut support tickets and reduce failed deliveries. Com.Bot is an official Meta Business Partner and brings SMS into one platform with WhatsApp, Instagram, Messenger, Google RCS and web chat, with one shared inbox, one contact record and no monthly conversation cap.

SMS reaches customers who may not have WhatsApp notifications turned on, and it works on every phone. For a business shipping hundreds of orders a day, a short transactional SMS cuts support tickets because customers stop asking where their parcel is. Delivery alerts also reduce failed deliveries, which is one of the biggest hidden costs in Indian ecommerce.

Com.Bot is an official Meta Business Partner with direct WhatsApp Business API integration, and it brings SMS into the same platform as WhatsApp, Instagram DMs, Facebook Messenger, Google RCS and a website chat widget. That means one shared team inbox, one contact record and one automation builder instead of five disconnected tools. You can send a delivery SMS and, in the same flow, open a WhatsApp conversation if the customer taps through.

Com.Bot has 50,000+ active customers, 100+ government bodies, 500+ global partners and processes 100M+ messages a day across 50+ countries. There is no monthly conversation cap on plans, so a festive sale spike does not push you into an overage conversation.

• One shared inbox for SMS, WhatsApp, Instagram, Messenger, RCS and web chat
• Visual drag-and-drop bot builder and AI-powered smart chatbots
• Automation builder with 1,000+ integrations, bot triggers and external actions
• Contacts CRM up to 1M-5M contacts depending on plan
• Native payments and payment collection on WhatsApp
• WhatsApp commerce store with orders and abandoned cart recovery

How do you set up order and delivery SMS in Com.Bot?

Short answer: Setting up order and delivery SMS in Com.Bot starts with DLT registration: register your business entity, a six-character sender ID or header, and every message template with {#var#} variables and the correct category. Once approved, connect your store or CRM, map order events to templates in the automation builder, and add a wa.me link when a reply is needed. Expert help is available.

Start with DLT registration, because nothing sends in India until it is done. You register your business entity on a DLT platform, then register a sender ID, also called a header. The header is six characters, for example LUMASK, and it is what the customer sees as the sender. Then you register every message template you plan to send. Templates use {#var#} variables for the parts that change, such as the order ID or the delivery date.

Each template is registered under a category: promotional, transactional or service, or OTP. Promotional SMS goes only to numbers not on the DND registry and within TRAI-permitted hours. Transactional, service and OTP messages can go to all numbers. Once your entity, header and templates are approved, connect your store or CRM to Com.Bot and map each order event to the right template.

In Com.Bot you build the flow in the automation builder. An order placed event triggers the confirmation template, a shipped event triggers the tracking template, and an out for delivery event triggers the final alert. You can add external actions such as API calls or webhooks to pull live order data from your system. If you would rather not build it yourself, expert help is available at ₹2,500 or ₹5,000 per hour depending on the work.

• Register your entity, sender ID and templates on a DLT platform
• Pick the correct category for each template before you submit it
• Connect your store or CRM and map order events to templates
• Add a wa.me link or phone number when a reply is needed
• Test with a small batch before switching on live orders
• Track delivery and support tickets after launch

What are the DLT and DND rules for SMS in India?

Short answer: DLT is the TRAI registration system required before any business SMS in India. The business entity, the six-character sender ID or header, and every template with {#var#} variables must be registered. Promotional SMS goes only to non-DND numbers within permitted hours, while transactional, service and OTP messages reach all numbers. Com.Bot SMS is one-way and India only.

DLT is the registration system TRAI requires before any business SMS is sent in India. Three things must be registered: the business entity, the sender ID or header, and every message template. The header is six characters, for example LUMASK. Templates use {#var#} variables in place of dynamic content. If any of these are missing or mismatched, the message will not be delivered.

Message category decides who can receive the SMS. Promotional SMS, which covers offers, re-engagement and cart reminders, goes only to numbers that are not on the DND (NCPR) registry and only within TRAI-permitted hours. Transactional, service and OTP messages go to all numbers, including DND-registered ones, because they relate to a transaction or account the customer already started.

SMS on Com.Bot is one-way. Customers cannot reply to the SMS, and there are no keyword replies or STOP replies. If a customer needs to respond, the message must include a link, a phone number or a wa.me WhatsApp link. SMS is plain text at 160 GSM characters per segment, so keep each template tight. Com.Bot offers SMS only in India, fully DLT compliant under TRAI rules.

• Entity, sender ID and every template must be DLT registered
• Header is 6 characters, for example LUMASK
• Templates use {#var#} variables for dynamic content
• Promotional SMS: non-DND numbers only, within permitted hours
• Service and OTP SMS: all numbers, including DND
• One-way only, so include a link or wa.me when a reply is needed

SMS vs WhatsApp vs RCS: which channel for which message?

Short answer: Use SMS for plain-text alerts that reach any phone, such as order confirmations, dispatch updates, out for delivery notices and OTPs, though SMS is one-way so replies must move to another channel. Use WhatsApp when the message is richer or the customer is likely to reply, since approved templates, payments and a 24-hour service window allow free-form replies in the same thread.

Use SMS when you need a plain-text alert that lands on any phone, especially for customers who may not have WhatsApp or who have notifications muted. Order confirmations, dispatch alerts, out for delivery notices and OTPs are natural SMS jobs. SMS is also useful for promotional campaigns to non-DND numbers within permitted hours, though it is one-way, so any reply has to move to another channel.

Use WhatsApp when the message is richer or the customer is likely to reply. WhatsApp Business API supports approved templates, images, buttons, native payments and a 24-hour customer service window where free-form replies are allowed. Order updates, delivery rescheduling, payment collection and cart recovery all work well here because the customer can respond in the same thread.

Use Google RCS when you want a branded sender with a logo and verified badge, images, carousels and suggested reply buttons inside the default messaging app on supported Android phones. RCS needs agent verification before launch. Many businesses run SMS for the alert and WhatsApp for the conversation, and Com.Bot keeps both in one inbox so your team sees the full history.

• SMS: plain-text alerts, OTPs, wide reach, one-way
• WhatsApp: rich templates, replies, payments, 24-hour service window
• Google RCS: branded sender, carousels, suggested replies on Android
• Instagram and Messenger: DM automation for social-first brands
• Web chat widget: on-site questions before checkout

What mistakes should you avoid with order and delivery SMS?

Short answer: Avoid sending promotional content under a transactional template, since a cart reminder or discount offer is marketing and mislabeling it can get your template rejected or your header flagged. Do not ask customers to reply to an SMS, because SMS on Com.Bot is one-way; use a wa.me link or phone number instead. Also avoid over-sending and check DND rules for promotional SMS.

The most common mistake is sending promotional content under a transactional template. A cart reminder, a discount offer or a back-in-stock alert is marketing, not a transaction update, and registering it as transactional can get your template rejected or your header flagged. Keep the categories honest and your delivery rates stay healthy.

The second mistake is forgetting that SMS is one-way. If your message says reply YES to confirm, the customer cannot do that. Replace it with a wa.me WhatsApp link, a phone number or a short URL that opens a page where they can act. This is especially important for COD confirmation, where a reply is often needed.

The third mistake is sending too often. Even transactional SMS can feel like spam if every minor status change triggers a message. Group events where it makes sense, keep templates short, and use the contacts CRM in Com.Bot to segment who gets what. For promotional SMS, always check the DND registry and permitted hours before you send.

• Do not label marketing content as transactional
• Do not ask customers to reply to the SMS
• Do not send promotional SMS to DND numbers or outside permitted hours
• Do not skip DLT registration for any template
• Do not exceed 160 GSM characters without checking the split
• Do not assume SMS will fall back automatically from WhatsApp or RCS

How do you measure order and delivery SMS results?

Short answer: Measuring order and delivery SMS results starts with delivery rate per template, then click-through on tracking and wa.me links. For delivery alerts, track failed delivery rate and support tickets asking where the order is. For COD confirmation, track confirmation rate and returns. For reminders, track on-time payments. Com.Bot shows SMS alongside WhatsApp, Instagram, Messenger, RCS and web chat on the same contact record.

Start with delivery rate per template. If a transactional template is underperforming, the usual causes are a category mismatch, a header that does not match the registered entity, or a variable that is not filled correctly. Fix those before you change the copy. Next, look at click-through on the tracking link or wa.me link, because that tells you whether customers are engaging with the message.

Then measure the business outcome. For delivery alerts, track failed delivery rate and support tickets asking where the order is. For COD confirmation, track confirmation rate and returned orders. For payment reminders, track on-time payment rate. These numbers move when the right message reaches the right customer at the right moment.

Com.Bot gives you one place to see SMS alongside WhatsApp, Instagram, Messenger, RCS and web chat activity, so you can compare channels on the same contact record. Plans are billed quarterly, and there is no monthly conversation cap, so a sale spike does not distort your reporting. If you need help reading the numbers, expert help is available.

• Delivery rate per template and per header
• Click-through on tracking and wa.me links
• Failed delivery rate and support ticket volume
• COD confirmation rate and return rate
• On-time payment rate for reminders
• Channel comparison on the same contact record

What does order and delivery SMS cost in India?

Short answer: Com.Bot plans are priced per quarter, every three months. Silver is ₹10,000 per quarter, Gold is ₹23,000 per quarter and is recommended, and Platinum V1 is ₹1,80,000 per quarter. SMS message charges are billed separately from the plan, based on the message category and the recipient's country, so ask the Com.Bot team for current rates.

Com.Bot plans are priced per quarter, every three months, in USD or INR. Silver is ₹10,000 per quarter and includes 1 WhatsApp API channel, 1M contacts, 5 team members, 1 commerce store and 20 messages per second. Gold is ₹23,000 per quarter and is the recommended plan, with 10 team members, 2M bot triggers, 40 messages per second and support in 6 working hours. Platinum V1 is ₹1,80,000 per quarter with 3 WhatsApp API channels, 5M contacts, 25 team members and 100 messages per second.

SMS message charges are billed separately from the plan, based on the message category and the recipient's country. Ask the Com.Bot team for current rates. Add-ons are available: extra team member, social channel or ecommerce store at $10 per month each, external actions at $10 per 5,000 and bot triggers at $10 per 25,000. Expert help is ₹2,500 or ₹5,000 per hour depending on the work.

Plans accept cards, UPI, PayPal, crypto and bank transfer. Payments are non-refundable, and you can cancel anytime with service running to the end of the billing period. Sign up at https://v3.com.bot/register, or book a demo on WhatsApp at +91 080 6987 1810 or email sales@com.bot.

• Silver ₹10,000 per quarter
• Gold ₹23,000 per quarter, recommended
• Platinum V1 ₹1,80,000 per quarter
• SMS message charges billed separately, ask for current rates
• Add-ons from $10 per month, expert help ₹2,500 or ₹5,000 per hour
• Cards, UPI, PayPal, crypto and bank transfer accepted

Frequently asked questions