What DLT registration means for a business sending SMS
If your business sends SMS to customers in India, whether OTPs, fee reminders, order updates or offers, the message has to be registered before a telecom operator will deliver it. The system that holds these registrations is called DLT (Distributed Ledger Technology). It comes from TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018, usually shortened to TCCCPR. The regulations and later directions are published on the TRAI website.
This guide is for owners, office managers and IT staff who have been told to "complete your DLT first" by an SMS provider and want to understand what that involves. By the end you should know what you register, who registers it, why messages still get blocked after registration, and how to keep your setup clean as the rules change.
DLT applies to SMS and commercial voice calls on Indian telecom networks. WhatsApp messages follow Meta's own rules; if you are still deciding between the two, read our guide on choosing between SMS and WhatsApp for customer alerts first.
The four registrations: entity, header, content template and consent
Think of DLT as a register that telecom operators check every time your message passes through their network. It holds four kinds of records about your business, and a message is delivered only when all of them line up.
1. Entity (the principal entity)
Your business registers as a principal entity on a DLT portal run by a telecom operator. You submit business identity documents and contact details; the portal lists what it currently accepts. Once approved, you receive an entity ID that travels with every message you send. Register in the name of the organisation your customers know, not in the name of your SMS provider or a staff member.
2. Header (sender ID)
The header is the short sender name that appears on the customer's phone instead of a mobile number. You apply for each header you want and link it to your entity. Headers used for promotional messages follow different format rules from headers used for service messages, so read the portal's guidance before settling on one. Pick something customers will recognise, such as a short form of your school, hospital or shop name, because an unfamiliar sender is easy to ignore or report.
3. Content template
Every message must match a registered content template. A template is the fixed text of a message with marked places for the parts that change, such as a name, amount or date. A fee reminder template, for example, might fix the words "Dear Parent, fee of Rs" and "is due on" and leave the amount and the date as variables. Each approved template gets its own ID and is linked to a category and to the header or headers allowed to send it.
4. Consent
Some messages can be sent only to people who have specifically agreed to receive them. For these, the business registers a consent template that describes what the customer is agreeing to, and the consent is recorded through the process the DLT platform provides. Separately, customers can set their own preferences, such as blocking promotional messages, through the do-not-disturb (DND) preference register. The operator checks both before it delivers.
Promotional, transactional and service messages: picking the right category
Each template is registered under a category, and the category decides who the message can reach and under what conditions. DLT portals generally show the four categories below. TRAI has tightened some definitions over the years, so read the descriptions on your own portal before you choose.
| Category | Meant for | Example | Key condition |
|---|---|---|---|
| Promotional | Offers, discounts, admission campaigns and any marketing message | New season stock has arrived at our Main Road store | Not delivered to numbers that have blocked promotional messages; time-of-day limits apply |
| Transactional | A narrow category for messages such as OTPs linked to banking transactions | OTP to confirm a bank payment | Limited to specific types of sender; most schools, hospitals and shops will not use it |
| Service (implicit) | Messages that follow from the customer's own transaction or existing relationship | Order confirmation, appointment reminder, fee receipt | Must be about the customer's own service; no offers mixed in |
| Service (explicit) | Messages the customer has specifically agreed to receive | Monthly updates a customer signed up for | Needs consent recorded through the DLT consent process |
A common mistake is registering a fee or appointment reminder as promotional "to be safe". It then fails to reach every parent or patient who has DND switched on. The reverse mistake, adding an offer line to a service template, can lead to the template being rejected at scrutiny or the header being flagged after complaints.
Why SMS still gets blocked after DLT registration
Most delivery failures after registration come from a short list of causes. Your delivery report will show the message as failed or rejected; ask your provider for the error code or reason, which usually points to one of the following.
- Text does not match the template: an extra space, a changed word, a different punctuation mark or a variable longer than allowed is enough to fail the match. Software that builds messages from database fields must use the exact registered wording.
- Wrong template and header pairing: the template is approved, but it is linked to a different header from the one used to send it.
- Wrong category: promotional templates do not reach DND numbers, and service templates containing offer language can be rejected.
- Links or call-back numbers not declared: newer TRAI directions expect web links, and in some cases phone numbers, inside messages to be registered on the DLT platform. An undeclared short link is a frequent cause of sudden failures.
- Entity or header inactive: registrations can lapse or be suspended, for example after customer complaints.
- Promotional message sent outside permitted hours: promotional SMS is restricted to certain times of day.
- Delivery chain not declared: recent directions expect the path from your entity through the telemarketers carrying your messages to be recorded on the DLT platform.
Keep a simple register of every template: its ID, exact text, category, header, and which software screen or report sends it. When a message fails, this is the first thing anyone will ask for.
Who does what: your business, the SMS provider and the operator
DLT duties are often confused because the SMS provider handles most of the day-to-day sending. The table shows the usual split. Contracts vary, so confirm the details with your own provider.
| Task | Your business | SMS provider | Telecom operator |
|---|---|---|---|
| Entity registration | Registers and owns the entity account; submits documents | Guides you through the forms | Verifies and approves |
| Headers | Chooses and applies for headers | Advises on format and category | Approves or rejects |
| Content templates | Submits templates or approves drafts | Drafts and checks templates against your use | Scrutinises and approves |
| Consent | Collects and records consent where needed | Explains which categories need it | Checks consent before delivery |
| Sending and reports | Decides who receives what, and when | Sends on the correct route and shares delivery reports | Matches each message against DLT records, then delivers or blocks |
Keep the login for your entity account inside the business, with a named owner such as the office manager or IT head. If the only person who knows the DLT password is a former employee or a previous provider, every new template becomes a slow recovery exercise.
Getting registered: a practical order of work
The order below avoids the usual back-and-forth with the portal. Approval times depend on the operator and on how complete your submission is, so do not plan a launch for the same day you submit templates.
- List every message you send or plan to send: OTPs, fee or bill reminders, order updates, appointment reminders and offers. Note who receives each one and what triggers it.
- Sort the list by category using the definitions on your DLT portal. Most day-to-day operational messages are service messages; offers are promotional.
- Register the entity with your business documents, using an email address and phone number that belong to the organisation rather than to one person.
- Apply for one or two headers that customers will recognise. Fewer headers are easier to manage and audit.
- Draft templates with the fixed text and variables clearly marked. Keep the fixed text plain and factual, and use variables only for details that genuinely change.
- Declare any web links or call-back numbers your messages will contain, as your portal requires.
- Share the entity ID, header and template IDs with your SMS provider, and give the exact template text to whoever maintains your billing software or ERP.
- Send test messages to a few staff phones, including one with DND switched on, and check the delivery report before going live.
Schools and hospitals deciding which messages to put on that first list can use the sample wording in our article on bulk SMS use cases for schools and hospitals.
The rules have changed since 2018: how to stay current
The core ideas of TCCCPR (registering the sender, headers, templates, consent and categories) have stayed the same since 2018. The details have not. TRAI has issued amendments and directions since then, including rules on links and call-back numbers in templates, tracing the chain of entities that carry a message, and changes to how categories are defined. We have deliberately not quoted those details here because they continue to change.
Three habits will keep most businesses out of trouble:
- Check the TRAI website and your DLT portal's notices every few months, and read any email from your portal or provider about new directions.
- Review your template register once a year: retire templates you no longer use and re-check each category against the current definitions.
- When messages suddenly fail across many numbers at once, ask your provider whether a new rule has come into force before assuming a technical fault.
How MATROP helps with DLT, and when you can manage on your own
MATROP PRIVATE LIMITED provides bulk SMS for promotions, alerts and OTPs from our office in Ranchi to businesses across India. On the DLT side, we give setup guidance for entity and template registration, help choose the right route (promotional, transactional or OTP) for each message, and avoid sending patterns that look like spam. Delivery reports show submitted, delivered and failed counts, and API integration lets your ERP, CRM, website or app send messages automatically using your registered templates.
Whichever provider you use, the entity registration and its login should stay in your business's name. If you send only a handful of messages a month, a clean template register and a reliable route may be all you need. A template audit is worth the time when messages are sent automatically from school, hospital or retail software and keep failing. You can reach us on 9430106005 or through the contact page.
Questions people ask
Do we have to register separately with every telecom operator?
Usually not. A registration made on one operator's DLT portal is generally shared with the other operators, but confirm this on the portal you use and keep your entity ID handy for every SMS provider you work with.
Can we change one word in an approved SMS template?
No. The fixed text must match the registered template exactly, so any change in wording has to be submitted and approved as a new or modified template before you send it.
Do OTP messages also need a DLT header and template?
Yes. An OTP sent by a business over a telecom network is a commercial message like any other, so it needs a registered header and a matching content template.
Does DLT registration cover WhatsApp messages?
No. DLT governs commercial SMS and voice calls on Indian telecom networks. WhatsApp Business messages follow Meta's own template and opt-in rules.
What should we keep if we change our SMS provider?
Keep the login to your DLT entity account, your entity ID, and the IDs of your headers and templates. Because the registrations belong to your business, a new provider can usually be linked to them instead of you starting again.
