SMS Marketing in India: 6 DLT Steps Before You Send

Five approvals stand between you and your first SMS. They are sequential, and each one can bounce.

SMS is the only marketing channel in India where the regulator sees your copy before your customer does. Not the tone of it: the literal text, registered in advance as a template, approved, and matched at send time. Get that wrong and the message does not underperform, it never arrives.

If you are still choosing between messaging channels, start with our marketing channels guide, then come back here for the part nobody explains until your first campaign is stuck in approval.

This describes how the system works as of 24 September 2026. It is not legal advice: your telecom operator or SMS aggregator confirms what applies to your account.

Where SMS still beats other channels in India, and where it does not

SMS wins on one thing: it arrives. No app install, no internet connection, no login, no algorithm deciding whether today is your day. On a feature phone in a low-signal district it is often the only message that lands at all.

That makes it right for anything time-bound. A one-time password. A delivery window. A payment failure. An appointment moved to Thursday. A policy about to lapse. Messages where "did it reach the phone" is the entire job.

It loses everywhere else. No image, no button, no thread, no read receipt, and roughly 160 characters before the message splits and the cost doubles. For catalogue browsing or conversational support, WhatsApp does the job better; email wins on long-form and segmentation depth. Those two pages own those channels here.

Language is a real decision here, covered separately in whether vernacular marketing actually works. One constraint to price in: non-Latin scripts drop the per-message limit to about 70 characters, so a Devanagari SMS costs more to send.

The DLT chain, in the order it actually happens

DLT stands for distributed ledger technology, the shared record telecom operators use to hold registered senders, headers and templates. TRAI's Advice to Senders page (last updated 24 September 2026) sets out the sequence: register as a principal entity, register a header, register the structure of your message content, and take consent through a registered consent template.

Registration happens on the telecom operators' own portals, not on a TRAI website. TRAI's TCCCPR page (last updated 22 September 2026) points senders to the TSP's website for entity, header, preference and template registration. You register once with an operator, and your aggregator maps the approved templates to your account.

TRAI defines the header as "an alphanumeric string of maximum eleven characters". Pick that sender ID early, because a brand name that does not fit gets abbreviated into something customers will not recognise.

1. Register the principal entity. Your business registers as the sender on an operator's DLT portal, with company documents and an authorised signatory. You get an entity ID that every later registration hangs off.
2. Register the header. Up to eleven alphanumeric characters, per TRAI's Advice to Senders page. The Second Amendment regulations of 12 February 2025 attach category suffixes to headers, "-P", "-S", "-T" and "-G" for promotional, service, transactional and government messages, so the recipient can tell what kind of message it is from the sender ID alone.
3. Register content templates. A template is the structure of the message: fixed text plus variable fields. TRAI describes it as content "which has fixed and variable part". Register one per message you intend to send, in every language you intend to send it in.
4. Register the consent template and whitelist your links. TRAI tells senders to acquire consent "through a registered consent template" before sending commercial communication. The Second Amendment regulations also require operators to scrub messages containing "URLs/ APKs/ OTT links/ call back numbers" against whitelisted data uploaded by senders, so every domain and callback number you intend to use goes on that list first.
5. Map templates and scrub the list. Your aggregator links approved templates to the header and the entity, and the list is checked against the customer preference registry before the send is accepted.
6. Test on all three networks, then send. Message your own numbers on Jio, Airtel and Vi first. Delivery timing and sender ID display are not identical, and a template that clears on one operator can still fail on another.

Budget calendar time for this. Registration is paperwork; template approval is a queue, and every rejection sends you back to the end of it.

Transactional, service or promotional: the category decides delivery

This is the decision that determines whether your message reaches the people you paid for. TRAI's Advice to Senders page defines a promotional message as commercial communication "for which the sender has not taken any explicit consent", and a service message as one sent with consent or on a template registered for that purpose, to facilitate a transaction or give warranty and safety information. Promotional traffic is filtered against customer preferences; transactional and service traffic is not treated the same way.

Categories and suffixes per TRAI's Advice to Senders page and the Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025, dated 12 February 2025. Approval friction and failure causes are our own observation from running sends, not regulation.

The consent and DND layer, in plain terms

Indian consumers control what commercial messaging they accept. TRAI's UCC and DND guidance (last updated 22 September 2026) says a consumer can "block all commercial communications (calls and SMSs both) or can selectively block UCCs from specified seven categories", registering via 1909 or TRAI's DND app. Those categories cover banking and financial products, real estate, education, health, consumer goods and automobiles, communication and entertainment, and tourism.

Two timing rules from the 12 February 2025 amendment are worth writing into your CRM rather than your campaign brief. A sender may re-acquire consent from a customer who revoked it only after ninety days from the date of that revocation. And explicit consent taken to complete an ongoing transaction runs for seven days unless the Authority directs otherwise.

Enforcement tightened at the same time. The PIB release of 12 February 2025 states that consumers get seven days to complain instead of three, that access providers must act within five days against unregistered senders rather than thirty, and that a first violation can mean a fifteen-day suspension of telecom resources, with repeat offenders facing a year-long disconnection and blacklisting.

Take a hypothetical: Sahyadri Silks, a Kolhapur saree brand with 40,000 buyers on file. Dispatch updates to those buyers sit in the service category. A Diwali blast to the same 40,000 does not, unless each one gave explicit consent the brand can still produce. Same list, two different positions.

Why templates get rejected, and what it costs

Rejection is the expensive part, because it is invisible on a plan and brutal on a calendar: a campaign meant for day one of a sale lands on day four. In our experience the same causes come back:

• Category mismatch. Offer language inside a service or transactional template. This is the most common rejection we see, and the easiest to avoid.
• An unregistered link. A domain or callback number that never made it onto the whitelist the operators scrub against.
• Variables doing too much work. A template that is mostly variable fields reads as an attempt to send arbitrary content under one approval.
• Header and body disagreeing. A brand name in the body that does not match the registered header.
• Language mismatch. A Hindi or Marathi version sent against an English template. Each language needs its own registration.

Build festive and sale templates weeks ahead, not the week of. Approval queues do not care about your launch date. If SMS is one line in a wider paid and lifecycle mix, our performance marketing team sequences it against the campaigns carrying the volume rather than treating it as a last-minute broadcast.

Link shorteners: why bit.ly kills the send

Public shorteners fail for a structural reason. The Second Amendment regulations require operators to scrub messages carrying URLs, APKs, OTT links and callback numbers against whitelisted data uploaded by the sender. A shortener domain is shared by thousands of senders, so it cannot be whitelisted as yours, and the destination behind it is invisible to the check.

The fix is a branded short domain registered and whitelisted under your own entity, carrying your tracking parameters. Set it up before you write the copy: the domain is the part with the lead time.

Measurement: delivery reports are real, open rates are not

SMS has no open event: no pixel, no read receipt, no equivalent of an email open. A vendor quoting a 98% SMS open rate is quoting a delivery report or a study of something else. What comes back from the operator is a delivery receipt, delivered, failed or expired, with a reason code. So measure it like a billboard with a coupon on it:

• Delivery rate by operator. A sharp drop on one network is a routing or template problem, not an audience one.
• Clicks on your own whitelisted short domain, with UTM parameters, so the traffic lands in analytics attributed to SMS.
• Unique codes per send, redeemed at checkout or in store, the only clean read for a brand with offline sales.
• A holdout group. Leave 10% of the segment unmessaged and compare, or you are crediting SMS for purchases that were happening anyway.

The trigger logic behind those sends belongs in your automation stack rather than a campaign calendar; our marketing automation guide covers that side.

Our view: why most Indian SMS campaigns underperform

This section is opinion, not data. The most common reason we see SMS underperform in India has nothing to do with copy, timing or segmentation. The sender is unrecognisable. An eleven-character header nobody remembers opting in to, on a phone already receiving a dozen such messages a day, reads as spam in under a second whatever the offer says.

The brands that do well use SMS narrowly and consistently: one header, tied to moments the customer already expects a message, brand name legible at a glance. The ones that do badly treat it as cheap reach, blast the full list monthly, then blame the channel. Cheap reach nobody reads is not cheap. If you can only maintain one message type properly, make it service messaging: it gets read, builds header recognition, and carries no consent risk.

When RCS makes more sense than SMS

RCS is the richer successor to SMS on Android. Google's Messages Help page on RCS chats with businesses describes a verified sender with a check mark beside the business name, read receipts when a user opens a message, and rich cards carrying photos, videos, audio or PDFs. Its unsubscribe control for RCS business chats is listed as available in a group of countries that includes India.

The caveats sit on the same page. Google states that "availability of RCS on Android varies by region and carrier", that it needs a data connection, and that the user has to turn it on. RCS is therefore an upgrade for the share of your list that can receive it, with SMS as the fallback for everyone else.

It earns its place on order tracking, appointment confirmations and anything visual. It does not on OTPs and critical alerts that must reach every handset. Confirm coverage and pricing with your operator or aggregator first: the reach number is account-specific and moves.