DLT Registration for Bulk SMS in India: Step-by-Step Guide

If you want to send bulk SMS to Indian numbers, DLT registration is the gate you cannot skip. This guide is for marketing, product and compliance teams, and for agencies sending on behalf of Indian clients. It explains what DLT is, what you register and in what order, which rules apply when you send, and where campaigns usually go wrong. It is a practical overview based on TRAI's published rules, not legal advice.

What is DLT and why does India require it?

DLT stands for distributed ledger technology. The Telecom Regulatory Authority of India (TRAI) requires operators to keep a shared registry of senders, headers, templates and consents under its Telecom Commercial Communications Customer Preference Regulations (TCCCPR) 2018, amended several times since. The platforms are run by the operators Jio, Airtel, Vi (Vodafone Idea) and BSNL.

The purpose is to stop unsolicited commercial communication and fraud. The registry is checked at delivery: a message is delivered only if its sender, header, template text and the recipient's preferences all match what is on record. That check is called scrubbing.

For you, the consequences are practical:

• Every business SMS to an Indian mobile, promotional or transactional, must use a registered header and template.
• A new message wording means a new template, not a quick edit.
• Rejections are silent from the sender's point of view unless you watch delivery reports.

What do you register on DLT?

You register five things. The first is done once; the rest grow as your use cases grow.

The category matters. TRAI's rules distinguish promotional messages, transactional messages (such as OTPs and banking alerts), service messages sent to your own customers on an inferred relationship, and service messages that rely on explicit consent. The network appends a suffix to the header (-P, -S, -T or -G) so the recipient can see which category a message belongs to.

How does the registration process work?

Portal screens differ by operator, but the order is the same. Treat this as a checklist.

1. Sign up as an enterprise (Principal Entity) on one operator's DLT portal, using your business PAN, authorised person details and business proof. Pay the portal's registration fee.
2. Wait for the entity registrar to verify. Vi's FAQ states a target of 72 hours from receipt of the fee; missing documents restart the clock.
3. Register headers. Choose the category for each. Special characters and spaces are not allowed. Headers are non-transferable.
4. Register consent templates for any traffic that relies on explicit consent.
5. Register content templates. Pick the type, category and linked header, write the fixed text and tag the variable parts. Include your brand name; templates without it can be rejected.
6. Whitelist URLs, app links and call-back numbers that appear in templates.
7. Add your telemarketer and declare the chain. Your messaging provider is typically the telemarketer; you authorise it with a letter of authorisation on the portal.
8. Test. Send one message per template to numbers on each operator before launch.

Portal fees are set by each operator and paid on the portal, so check the current amount there. We do not list them here. For documents, expect your PAN, proof of business such as GST or incorporation papers, the authorised person's identity and an authorisation letter on letterhead.