DLT Guide

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
Entity Verified
VM-SMSFY
01 · Basics

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.

02 · Applicability

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:

OTP messages
Transactional SMS
Service notifications
Promotional campaigns
Customer alerts
Appointment reminders
Order updates
Process

The DLT registration process

A typical journey from business registration to your first compliant campaign.

1

Business / Principal Entity Registration

Register your business as a Principal Entity with the required business details.

2

Complete required business verification

Provide the verification documents requested during entity registration.

3

Create / register Header or Sender ID

Register the sender identity your messages will appear from.

4

Create SMS Content Template

Draft and submit the exact message content you plan to send for approval.

5

Map required entities / templates

Link your approved entity, sender ID and templates together.

6

Configure approved information inside SMSFY

Add your approved entity ID, sender ID and template IDs to your SMSFY account.

7

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.

03 · Registration

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.

04 · Sender Identity

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:

Example only 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.

05 · Message Content

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.

Example only "Your OTP for login is {#var#}. Do not share it with anyone. – SMSFY"

Read the full Content Template guide →

Variable types, formatting rules and why templates get rejected.

06 · Compliance

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.

Checklist

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
FAQ

DLT frequently asked questions

DLT registration is the process of registering your business, sender ID and message templates on the platforms telecom operators use to validate commercial SMS in India.
Yes — businesses sending commercial SMS, including OTP and promotional messages, are generally required to complete entity, sender ID and template registration as per operator requirements.
A Principal Entity is the verified business identity registered on the DLT ecosystem that all your sender IDs and templates are linked to.
A Header, or Sender ID, is the short alphanumeric code that appears as the sender of your SMS — for example, VM-SMSFY.
A Template ID is the unique identifier issued for an approved SMS content template, used to match outgoing messages with their registered format.
Templates are commonly rejected for formatting mismatches, unclear variable placement, or content that doesn't match the declared message category. Reviewing the exact wording and variable structure usually resolves this.
Yes — templates support variable fields such as OTPs, names, amounts, order IDs and, where permitted, links, alongside fixed static text.
Delivery failures are often linked to a mismatch between the sent content and the approved template, an unmapped sender ID, or operator-side filtering. Checking your delivery report is the first step to diagnosing the cause.
SMSFY provides onboarding and technical assistance throughout the DLT process — guidance on entity registration, sender ID setup, template drafting and mapping. Final approvals remain subject to the applicable telecom operator / DLT platform.
Processing time depends on the relevant telecom operator / DLT platform and the completeness of your submitted documentation.
Yes — many businesses register separate sender IDs for different purposes, such as transactional versus promotional messaging.
Messages that don't match their registered template are typically blocked or filtered by the telecom operator before delivery, which is why keeping content aligned to the approved format matters.

Still need help with DLT?

Our team can guide you through entity registration, sender ID setup and template mapping.

Get DLT Assistance