Challenge the Future with Technology
Everything you need to register as a Principal Entity, get your sender ID and templates approved, and start sending compliant SMS in India — plus the specific mistakes that send applications back to the queue. We have walked hundreds of businesses through it since the framework began.
DLT registration is the mandatory step every Indian business must complete before sending commercial SMS. Introduced by TRAI under the Telecom Commercial Communications Customer Preference Regulations (TCCCPR) 2018, it requires you to register your business as a Principal Entity, register each sender ID (header), and pre-approve every message format (content template) on a blockchain-based platform run by the telecom operators. Anything that does not match a registered header and template is blocked before delivery. Entity approval typically takes 2–7 working days and costs around ₹5,900 including GST; headers and templates are usually free and clear within 1–3 days each.
Before 2018, blocking a spam sender meant chasing them after the fact. TCCCPR 2018 changed the model: instead of policing messages, TRAI made the operators police senders. Every business that wants to send commercial SMS has to identify itself on a shared, tamper-evident ledger, declare the sender IDs it will use, and register the exact wording of what it intends to send.
The practical consequence is blunt — an unregistered message does not get delayed, it gets discarded. There is no error the recipient sees and no retry that fixes it. This is why businesses that buy SMS credits from a cheap portal and then discover nothing is being delivered are almost always looking at a DLT problem, not a gateway problem.
It also means compliance is not a one-time form. Every new campaign wording needs a template, every new brand or product line may need its own header, and consent records have to be defensible if a complaint is ever raised.
Registration happens on a portal run by a telecom operator — Jio, Airtel, Vodafone Idea or BSNL. You register on one of them; your entity record is then shared across the DLT ecosystem, so you do not repeat the whole exercise four times. Headers and templates, however, are still reviewed per operator, which is why a template can be live on one network a day before another.
You register the legal business: name exactly as it appears on PAN, entity type (private limited, LLP, partnership, proprietorship, trust, society), GSTIN, registered address, and the authorised signatory with self-attested KYC. On approval you receive a unique Entity ID — a long numeric string you will need for every subsequent step and for your gateway configuration.
Timeline: 2–7 working days. Cost: around ₹5,900 (₹5,000 + 18% GST) on the major portals. The fee is per entity, not per header.
A header is the six-character alphanumeric string recipients see instead of a phone number — AVNZON, SBIINB, MYSHOP. Headers are globally unique across the DLT system, tied to your entity, and mapped to a single category. You cannot use one header for both promotional offers and transactional OTPs; register one for each type of traffic you send.
Pick something recognisable. A recipient who cannot tell who sent a message is a recipient who reports it.
Every message format is pre-approved before it can be sent. Variable content — a name, an OTP, an amount, a tracking link — is written with the {#var#} placeholder:
Dear {#var#}, your OTP is {#var#}.
Valid for {#var#} minutes. Do not share it.
– AVNZON
Each template is bound to a header and a category. A variable can hold up to 30 characters, so long dynamic values need to be split across placeholders or shortened.
Registration gets you the right to send; consent decides who you may send to. Keep a defensible record of how each contact opted in — the source, the timestamp and the wording they agreed to.
From there the system does the enforcement for you. Every promotional send is scrubbed against the national DND (Do Not Disturb) registry, and numbers that have opted out are dropped unless you hold valid explicit consent. Transactional and OTP messages are exempt, which is why an OTP still lands on a fully DND-registered number.
Category is not a formality — it determines the sending window, whether DND numbers are reachable, and what wording is permitted. Registering a promotional message as transactional is the single most common rejection reason we see.
| Category | What it covers | Sending window | Reaches DND numbers? |
|---|---|---|---|
| Transactional | OTPs and alerts tied to a transaction the customer initiated | 24×7 | Yes |
| Service — implicit | Order confirmations, delivery updates, appointment reminders based on an existing relationship | 24×7 | Yes |
| Service — explicit | Service updates that carry limited promotional content and require documented opt-in | 10 AM – 9 PM | Only with recorded consent |
| Promotional | Offers, discounts, festival campaigns, new launches | 9 AM – 9 PM | No |
| Government | Reserved for government departments and agencies | 24×7 | Yes |
Not sure which bucket your messages fall into? Our guide on transactional vs promotional SMS works through real examples.
Gather these first. Applications that stall almost always stall on paperwork, not on policy.
One detail is worth more than the rest combined: the entity name must match your PAN and GST records exactly — the same spelling, the same abbreviations, the same "Pvt Ltd" versus "Private Limited". A single mismatched character is a rejection.
These are the rejections we see most often, and each one typically costs three to five days:
{#VAR#}, {# var #} or {{var}} instead of {#var#}| Item | Typical fee | Typical timeline | Notes |
|---|---|---|---|
| Principal Entity registration | ₹5,900incl. 18% GST | 2–7 working days | Charged per entity. Some portals treat it as an annual fee. |
| Header (sender ID) | Freeon most portals | 1–3 working days | Register one per traffic category. Unlimited headers under one entity. |
| Content template | Freeon most portals | 1–3 working days | No practical limit on how many you register. |
| SMS credits | Per volumeseparate | Same day | Charged by your gateway, not by DLT. Ask for rates. |
Figures reflect the major operator portals as of August 2026 and vary between them. DLT fees are paid to the operator portal; they are not an AvanceZone charge.
We check your PAN, GST and entity name against each other before anything is submitted — which is where most of the delay would have come from.
We work out how many headers you actually need and which category each one should carry, so you are not back at the portal in a month.
We write your templates in approved form, with correct variable notation and the sender ID embedded, and cover the campaigns you will want next quarter too.
Entity ID, headers and template IDs mapped into your account and tested end to end, so your first live send is not your first test.
Need OTPs working this week? We can carry transactional traffic on pre-approved routes while your own registration completes.
Compliance questions answered by people in Coimbatore who have done this since the framework started — on the phone, not in a ticket queue.
Routes, deliverability and what to look for when you pick a gateway.
Send against your approved template IDs from your own application.
Local onboarding, Tamil-language campaigns and same-day setup.
The short version, written for businesses registering from Tamil Nadu.
Worked examples of which category your messages belong in.
Reselling SMS? Here is how DLT works across your own customers.
Send us your documents and we will get your entity, headers and templates approved — then map them into a gateway that is ready to send.
Already registered elsewhere? We can map an existing Entity ID to a new gateway — see our SMS gateway in India.