DLT registration for SMS in India: why your messages get blocked
DLT registration is TRAI's mandatory system requiring every business, sender header and SMS template to be pre-registered before sending commercial SMS in India. An SMS that does not exactly match a registered header and template is silently blocked by telecom operators, which is the most common reason business SMS messages never reach customers.
- DLT registration has three layers: your business as an entity, your sender header, and each individual message template.
- A template's registered text must match the sent SMS almost exactly, including punctuation and variable placeholders.
- Unregistered SMS is not delayed, it is blocked outright by telecom operators before it reaches the customer.
- Transactional and promotional headers are treated differently, with different consent and time-of-day rules.
- DLT is entirely separate from WhatsApp's approval process — registering a WhatsApp template does not cover SMS.
What DLT actually is
DLT (Distributed Ledger Technology) registration is a system mandated by TRAI, India's telecom regulator, requiring every business that sends commercial SMS to register itself, its sender headers and its exact message templates on a shared ledger accessible to all telecom operators. It exists to cut down on spam and to make every commercial SMS traceable back to a specific registered business.
The practical effect for a business is blunt: an SMS that is not built from a registered header-and-template combination simply does not get delivered. Telecom operators check against the DLT registry before allowing a message through, and there is no warning email when this happens. The message just silently disappears.
This surprises many business owners the first time it happens, because everything else about the setup looks correct: the SMS provider account is active, the balance is topped up, the API call reports success. The block happens one layer further downstream, at the telecom operator, entirely outside the sending platform's own visibility. This is also why DLT confusion is so common among businesses new to SMS automation, since nothing in the sending tool itself indicates that a delivery failure is a registration issue rather than a technical fault.
The three layers of registration
- Entity registration: your business registers once as a Principal Entity with a telecom operator's DLT portal, providing basic business details.
- Header registration: you register a sender ID, typically a 6-character code shown as the SMS sender (like CONVO3) instead of a random number.
- Template registration: every distinct message format you plan to send is registered in advance, with fixed text and clearly marked variable placeholders.
All three have to exist and match before a single SMS using that combination will go through.
Businesses that send SMS through more than one telecom operator or aggregator sometimes discover that registration does not automatically carry across every route. Depending on your provider's setup, the same header and template may need to be linked correctly on each route it is meant to send through.
Why templates fail more often than expected
The most common cause of SMS suddenly "stopping" for a business that was sending fine before is a small change to the message text: a rewritten sentence, an added emoji, or a punctuation tweak that no longer matches the exact registered template. Even variable placeholders have to sit in the same position and format as they were originally registered.
Because of this, treat an approved SMS template the way you would treat a WhatsApp template: as a fixed asset you use as-is, not something to lightly edit whenever the wording feels like it could be improved.
A practical habit that avoids this problem: keep a copy of the exact registered template text alongside your flow documentation, and treat any wording change as a two-step process: register the new version first, confirm it is approved, and only then update the live flow to use it.
Transactional vs promotional headers
| Transactional | Promotional | |
|---|---|---|
| Typical use | OTPs, order confirmations, appointment reminders | Offers, discounts, marketing campaigns |
| Consent needed | Implied by the transaction relationship | Explicit opt-in required |
| Sending window | Generally unrestricted | Restricted hours under TRAI rules |
| DND registry effect | Usually still delivered | Blocked to DND-registered numbers unless opted in |
Getting this classification wrong at registration time is a frequent cause of otherwise-correct messages being blocked or delayed. See TRAI's own guidance on commercial communication for the current rules at trai.gov.in.
Common mistakes
- Assuming WhatsApp approval covers SMS too: they are entirely separate systems with separate registrations; a WhatsApp-approved template has no bearing on SMS delivery.
- Editing a live template without re-registering: even a small wording change needs a fresh template registration before it will send.
- Registering the wrong header type: a promotional message sent under a transactional header can be flagged and blocked once the mismatch is detected.
- Ignoring consent records: DLT does not remove the need to keep your own record of who actually opted in to promotional messages.
- Assuming one registration covers every provider: if you ever switch or add an SMS provider or aggregator, check whether your existing header and templates need to be re-linked on the new route.
How this affects the Send SMS block in Convo360
Convo360's Send SMS flow block sends through your own connected Plivo account under BYOK, but the DLT entity, header and template registration itself has to be completed by your business directly with your telecom operator or SMS provider before those messages will be delivered. Convo360 does not perform DLT registration on your behalf. Once your header and template are approved, insert the exact registered text (with variables in the same positions) into the Send SMS block, and messages sent through the flow will pass the same DLT check as any other SMS from your business. If a business relies mainly on WhatsApp and uses SMS only as a fallback for customers without WhatsApp, it is still worth completing DLT registration ahead of time for at least one transactional template, rather than discovering the gap the day a fallback message actually needs to send.
Example conversation
Automate SMS the right way
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
What happens if I send an SMS without DLT registration?
The telecom operator blocks it before it reaches the recipient. There is usually no error notification to the sender, which is why undelivered SMS is often mistaken for a technical bug rather than a registration issue.
Does DLT registration apply to WhatsApp messages too?
No, DLT is specific to SMS and is a TRAI requirement. WhatsApp has its own separate template approval process managed by Meta, and the two systems do not share registrations.
How long does DLT registration usually take?
Entity registration is typically the slowest step, often taking a few working days; header and template registration are generally faster once the entity is approved. Timelines vary by telecom operator.
Can I change the wording of an already-approved SMS template?
Not without registering the change as a new or updated template. Even minor edits, including punctuation, can cause the message to fail the DLT match check and get blocked.
Why do some of my SMS reach DND-registered numbers and others don't?
Transactional messages are generally still delivered to DND-registered numbers, while promotional messages are blocked to those numbers unless the recipient has specifically opted in, which is why correct header classification matters.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.