If you send commercial SMS in India, your messages travel through a system called DLT, short for Distributed Ledger Technology. TRAI, the telecom regulator, required every telecom operator to run a DLT platform where businesses register who they are, which sender names they use and exactly what their messages say. A message that does not match those records can be blocked before it reaches the handset.
This guide walks through the registration in the order you will do it, explains what each step is for, and points out where applications usually stall. It is a general overview. Portals and requirements change, so confirm the current process with your operator portal or with our DLT registration service before you file.
What DLT registration actually covers
DLT registration is not one form. It is a chain of linked records, and each one depends on the one before it.
- Your business, called the principal entity, with verified documents
- The sender IDs (also called headers) your messages will show
- The message templates, which fix the wording of each message type
- Consent templates and records, for promotional messaging
- The link between your entity and the platform or aggregator that actually delivers your messages
Step 1: Register the principal entity
The principal entity is the business that owns the messages. You register it on an operator’s DLT portal and submit business details and supporting documents. Typical documents include a business registration or incorporation proof, a tax registration number, proof of address and an authorisation letter or ID for the person signing on behalf of the company. Individual operators may ask for slightly different proofs, so keep scanned copies ready and make sure the name on each document matches exactly.
Most delays at this stage come from small mismatches: a trading name that differs from the registered name, an expired authorisation letter, or a signatory whose ID does not match the letter. Check every name and number against the source documents before submitting.
Step 2: Register your sender IDs
A sender ID, or header, is the short name that appears as the sender of your SMS. You register each one against your entity and choose its type, such as transactional, service or promotional. Choose a name that clearly relates to your brand, because reviewers compare it with your entity details. Our guide to how sender IDs are approved covers naming rules and common rejections in more detail.
Step 3: Register message templates
A template is the approved wording of a message, with variables marking the parts that change, such as a code, a name or an amount. You register one template per message type and choose its category. Once approved, each template gets an ID, and your messages must quote that ID and match the template text. Our guide to DLT templates and common rejections explains how to write templates that pass review.
- Use the variable placeholder for anything that changes, and keep fixed text exactly as you will send it
- Pick the category that matches the purpose: OTP and transactional, service, or promotional
- Do not put offers or promotional wording in a transactional template
- Register separate templates for separate messages instead of one catch-all
Step 4: Set up consent for promotional messages
Promotional messaging depends on recorded consent and on respecting customers’ do-not-disturb preferences. The DLT platform holds consent templates and records, and promotional sends are checked against them. If you plan to send offers, set up consent capture early. It is harder to do it after your list has grown. Our promotional versus transactional guide explains how the two categories differ in practice.
Step 5: Link your entity to your delivery platform
Messages pass from your system through a platform or aggregator to the operators. DLT records that chain, so your entity needs to be linked to the party that actually sends on your behalf. Without this link, otherwise valid messages can fail the scrubbing check. When you work with Orian, our compliance team guides this step as part of onboarding, and you can then send through the bulk SMS and OTP gateway.
Step 6: Test before you launch
Send a handful of test messages for each template to your own numbers across the main operators. Check that the sender name, the wording and the delivery report all look right. Fix mismatches now, before a live campaign exposes them to customers.
Why applications stall
- Document names that do not match the registered business name
- Sender IDs that look unrelated to the entity or imitate a well-known brand
- Templates with promotional wording in a transactional category
- Variables so open-ended that a message could say anything
- Links or phone numbers that are not allowed for the category
- Messages sent that differ even slightly from the approved template text
How long does it take?
Timelines depend on the operator, the quality of your documents and how many rejections you hit. Clean applications can move quickly, while one mismatch can add days. Plan for registration before your launch date, not alongside it, and keep a copy of every approved record next to the code that sends it.
Keeping registration healthy
Registration is not a one-time job. When you add a new message type, you register a new template. When you add a brand or product line, you may need a new sender ID. When rules change, existing templates and links to URLs may need to be reviewed. Keep one person responsible for the DLT account, and keep the login details in a shared password manager rather than in one person’s email.
The compliance centre on our site has an onboarding checklist, and the DLT compliance service page explains what we handle for you. If you are unsure which step you are stuck on, talk to our team and we will help you work it out.