What is DLT registration in India? Entity, header and template guide

What is DLT registration?

DLT registration is the process by which a business in India registers its identity, sender names and message formats before it can send commercial SMS. DLT stands for distributed ledger technology, the shared record on which the telecom operators keep these registrations. The aim, set by the Telecom Regulatory Authority of India (TRAI), is to cut spam and fraud by making sure that every business message can be traced to a verified sender.

In practice it means that a message you send must match something you registered earlier, and an operator will check it before it reaches the phone. This guide explains the pieces, the way the check works, how to register and why registrations fail. For a short checklist, see our DLT registration checklist.

The four things you register

Each one gets an ID, and your messaging provider needs those IDs to send. Telnxo asks for them when you add a sender; see our DLT guide and the sender ID article.

How DLT scrubbing works

Before an operator delivers a commercial SMS, it checks it against the registry. This check is often called scrubbing. It looks at the sender entity, the header, the template and, for promotional messages, the recorded consent. If any one does not match, the message is rejected and you see a failure code. That is why a small change in wording can stop an entire campaign.

Template types and what they allow

Category names and sending windows are set by TRAI and can change, so check the current rules before you plan campaigns. Our guide to opt-outs, sending windows and consent explains the practical side.

How to register for DLT, step by step

1. Collect your documents. Business registration proof, PAN, authorised signatory details and a letter of authorisation if a partner will send for you.
2. Register the entity. Create an account on an operator DLT portal, submit the documents and wait for the principal entity ID.
3. Register headers. Choose names that clearly match your brand. Names that imitate another company are rejected.
4. Write templates. Use plain wording, put the brand name in, keep variables to short items such as names and codes, and pick the right category.
5. Register consent. Either upload existing opt-in records or collect them with a registered consent template.
6. Connect to your provider. Add the IDs in your Telnxo account, send a test and confirm delivery.

A template and the message it allows

Template (approved):
  {#var#} is your Telnxo verification code. It expires in {#var#} minutes. Do not share it.

Message that matches:
  482913 is your Telnxo verification code. It expires in 5 minutes. Do not share it.

Message that fails the scrub:
  Your Telnxo code: 482913. Valid 5 mins.

The second message may be perfectly clear to a person, but it does not match the registered text, so it is blocked.

Why DLT registrations get rejected

When a live message fails, the error code tells you whether the entity, header or template was the cause. Our guide to why an SMS is not delivered helps with the diagnosis, and the template builder helps write wording that fits.

Who has to register

Any business that sends commercial or transactional SMS to Indian numbers needs its own registration or must send through someone who has one. That includes banks, e-commerce stores, schools, clinics, delivery companies and software products that text their users. A software platform that sends on behalf of many customers usually asks each customer to register as the entity, because the entity identifies the business whose message it is, not the provider that delivers it.

Agencies and resellers need care. If you send for clients, each client should have its own entity registration, or you should hold a clear authorisation to act for them. Using one entity for many unrelated brands is a common cause of rejected headers, since the sender name no longer matches the registered business.

Getting approvals faster

• Use one consistent legal name across your documents, your header and your templates.
• Prepare a short, honest purpose statement for every template. Reviewers read it.
• Start with a few templates that cover most of your traffic, rather than dozens of near-duplicates.
• Keep the brand name in the message so the customer knows who is writing.
• Reply promptly if the portal asks a question; silent requests are often closed.

Sending at scale after registration

Once you are registered, the work becomes keeping messages and registrations in step. Keep a list of every template with its ID, category and the system that uses it. When a product team wants a new notification, they raise it before launch so the template is approved in time. When the wording changes, a new template is needed. Review old templates now and then and retire the ones you no longer use, because unused registrations only add confusion.

If you move providers, your registrations stay with you, since the IDs belong to your entity. You tell the new provider your IDs and map each template to its new use. See moving from MSG91, Gupshup or Exotel for examples. For the broader picture of sending in India, read how to send bulk SMS in India and use the sender ID checker before you register a header.

DLT is easiest when you treat it as a content system: one owner, one list of templates, and a rule that nothing is sent that is not registered.