DLT made simpler for your business.
Understand entity registration, sender IDs, content templates and the steps required before sending business SMS in India — explained in plain language.
DLT Onboarding
Entity: Registered- Principal Entity registered
- Header / Sender ID approved
- Content template approved
- …Mapping in progress
What is DLT?
DLT stands for Distributed Ledger Technology. In India's commercial communication ecosystem, DLT platforms are used by telecom operators to register and manage business messaging identities — including business entities, sender IDs and approved message templates — before commercial SMS can be sent.
In simple terms, it's the registration layer that connects a verified business identity to the messages it sends, so that operators can validate the sender and the content before delivery.
SMSFY is a business messaging platform, not a telecom operator, TRAI or a DLT platform. We help businesses navigate this registration process and configure the approved details inside their SMSFY account.
Who needs DLT?
Any business sending commercial SMS to customers in India will typically need to complete DLT registration. This covers a wide range of everyday business messaging, including:
The DLT registration process
A typical journey from business registration to your first compliant campaign.
Business / Principal Entity Registration
Register your business as a Principal Entity with the required business details.
Complete required business verification
Provide the verification documents requested during entity registration.
Create / register Header or Sender ID
Register the sender identity your messages will appear from.
Create SMS Content Template
Draft and submit the exact message content you plan to send for approval.
Map required entities / templates
Link your approved entity, sender ID and templates together.
Configure approved information inside SMSFY
Add your approved entity ID, sender ID and template IDs to your SMSFY account.
Test and start messaging
Send a test message to confirm everything is mapped correctly, then go live.
Approval processes, documentation and requirements may vary by telecom operator and message category.
Principal Entity Registration
What a Principal Entity means: it's the verified business identity registered on the DLT ecosystem — every sender ID and content template your business uses is linked back to this entity.
Why businesses register: registration confirms that a real, verifiable business stands behind the messages being sent, which is why telecom operators require it before allowing commercial SMS traffic.
Typical business information required generally includes your business name and registration details, business category, address, contact information, and authorised signatory details. Exact document requirements can vary by operator.
Entity ID: once your business is registered, it's issued a unique Entity ID — this ID is what gets referenced when registering sender IDs and templates later.
Verification process: your submitted business details are verified before approval. Turnaround time depends on the operator and the completeness of your documentation.
Header / Sender ID
A Header, commonly called a Sender ID, is the short alphanumeric code that appears as the sender on a customer's phone — for example:
VM-SMSFY
Sender IDs are generally registered separately for promotional messaging versus service or transactional communication, since the two are treated differently across the ecosystem. Choosing a sender ID that's clearly recognisable as your business helps build customer trust and reduces confusion.
Read the full Sender ID guide →
Naming rules, approval process and how promotional differs from transactional.
Content Templates
Every SMS you send has to match an approved content template. Templates are made up of static text plus variable fields that change per message — common variables include OTP codes, customer names, amounts, order IDs and, where permitted, links.
Read the full Content Template guide →
Variable types, formatting rules and why templates get rejected.
Consent & Promotional Messaging
Customer consent is a core concept across business messaging in India — promotional messages are generally sent only to customers who haven't opted out, while transactional and service communication (like OTPs and order updates) follows a separate, more permissive category since it relates directly to a service the customer is already using.
Maintaining clear consent records and following compliant messaging practices helps protect your sender reputation and keeps your business in good standing with telecom operators.
Before sending your first SMS
DLT Checklist
- Entity registered
- Header approved
- Template approved
- Template ID available
- Sender mapped
- SMS content matches approved template
- API / campaign configured
DLT frequently asked questions
Still need help with DLT?
Our team can guide you through entity registration, sender ID setup and template mapping.
Get DLT Assistance