As per TRAI TCCCPR 2018 regulations, every business sending commercial SMS in India must complete all four steps of DLT registration. Unregistered entities will not be permitted to send commercial SMS through any telecom operator network in India.
Register your business on any one authorised telecom operator's DLT platform — Airtel, Jio, Vodafone Idea, BSNL, or others. You must submit valid KYC documents including PAN card, GST certificate, Certificate of Incorporation (CIN), and your business details.
Once your documents are verified by the operator, a unique Entity ID is generated and shared with you. This Entity ID is then synchronised across all other DLT platforms in India automatically.
Download Entity Registration GuideRegister all SMS Sender IDs (Headers) your business intends to use for sending messages. Headers must be registered under the correct message category:
Each approved header is assigned a unique Header ID upon approval. Only DLT-approved headers will be permitted to send SMS through operator networks.
Every SMS message your business sends must have a pre-approved content template registered on the DLT platform. Each approved template receives a unique Template ID which must be passed along with every message at the time of sending.
As per TRAI guidelines effective October 1, 2024, all variable fields within templates must be pre-declared and properly tagged. Templates must clearly include your registered Brand Name or Business Name within the message content.
Review DTL Template GuidelinesAfter completing your Entity, Header, and Template registration, you must bind your account with your authorised Telemarketer (TM) on the DLT portal. This step authorises your SMS service provider to send messages on your behalf.
Stay compliant with the latest TRAI DLT guidelines. All businesses must ensure their DLT account reflects the most current regulatory requirements to avoid message rejections.
As mandated by TRAI under TCCCPR 2018, every Principal Entity (PE) must complete the PE–TM (Principal Entity – Telemarketer) chain binding on the DLT platform before their SMS traffic can be processed and delivered through an authorised Telemarketer.
This binding process creates a verified, transparent communication chain
between your registered business and your SMS service provider — ensuring
every message sent is fully traceable and compliant with TRAI regulations.
View Step-by-Step PE-TM Binding Guide
As per the latest TRAI regulatory update effective 1st October 2024, all variables used within DLT-registered SMS templates must be pre-declared and correctly tagged at the time of template submission. This requirement applies to all template types across all telecom operators.
Businesses must ensure that:
Failure to comply with variable tagging and CTA whitelisting requirements may result in template rejection or complete message blocking by telecom operators. Review all active templates and update them before the effective date to avoid disruption.
As per TRAI-mandated DLT guidelines introduced in October 2020, every SMS content template registered by a Principal Entity must clearly and prominently include the complete registered Brand Name, Business Name, or Trademark within the body of the message content.
This requirement applies to all message categories — Promotional, Transactional, Service Implicit, and Service Explicit. Templates submitted without proper brand identification may be rejected by the operator or require modification and re-submission for approval.
Once your Entity ID and Sender Header are approved on any one telecom operator's DLT platform, the approval details are automatically synchronised across all other operator DLT systems in India. You do not need to re-register separately on each operator's platform for your Entity ID.
If you require assistance with DLT registration, template submission, or PE-TM binding, our compliance team is ready to help. Contact us at support@fivosms.co.uk or call +91 9310 189 890.
You can register your business as a Principal Entity on any one of the authorised DLT platforms listed below. Once approved, your Entity ID, Headers, and Templates will be synchronised across all operators automatically.
The following table outlines the key differences between the pre-DLT and post-DLT regulatory environment for commercial SMS communication in India, as mandated by TRAI under TCCCPR 2018.
| Pre DLT | Post DLT | Remarks | |
|---|---|---|---|
| Customer Consent | No | Yes | Verifiable digital records of all customer opt-ins are recorded and made available on the DLT platform. Customers can view and manage all their communication consents from a single dashboard. |
| Customer Preferences | Yes | Yes | Customers can select specific days and time bands to block or allow commercial communications. This extends beyond standard DND preferences to include message category selection. |
| Entity / Enterprise Registration | No | Yes | All businesses and entities must register with their Originating Access Provider (OAP) on the DLT platform before sending commercial SMS. |
| Telemarketer Registration | Yes | Yes | Telemarketers must now register with their Originating Access Provider (OAP) — not directly with TRAI as was previously the case. |
| Header Registration | No | Yes | Every SMS Sender ID (Header) and Voice CLI used by a business must be individually registered and approved on the DLT platform. |
| Message Categories | Transactional | Transactional | Every SMS template must be registered under one of four approved categories: Promotional, Transactional, Service Implicit, or Service Explicit. |
| Promotional | Promotional | ||
| Govt | Service (Inferred Consent) | Government-issued communications are now classified under the Service (Inferred Consent) category. | |
| Service (Explicit Consent) | |||
| Scrubbing | Yes (DND check for Promotional SMS only) | Yes (Promotional & Service Explicit) | Messages are now scrubbed against multiple parameters including Consent, Customer Preference, Header approval, and Template ID — not just the DND list. |
| Complaint Management | Yes | Yes | Telecom operators are now directly responsible for the resolution of all UCC complaints within defined regulatory timelines. |
| Interoperability Between Telecom Operators | No | Yes | Entity, Telemarketer, Header, and Template registration details are shared and synchronised across all operator DLT networks in India. |
| 100% Traceability | No | Yes | Every commercial SMS sent in India is now fully recorded and traceable across the network using blockchain-based DLT technology. |
| Delivery Reports | Yes | No | Delivery status reports for Promotional SMS traffic are no longer available post-DLT implementation. |
| 1. Promotional Traffic | |||
| 2. Transactional Traffic | Yes | Yes | Delivery status reports for Transactional SMS traffic continue to be available post-DLT as before. |
Access our detailed step-by-step guides to ensure your business is fully compliant with all TRAI DLT regulations — from initial registration to template approval and PE-TM chain binding.
A comprehensive, step-by-step guide to registering your SMS content templates on the DLT platform — including variable tagging requirements, brand name inclusion rules, and best practices for fast approval.
Understand why TRAI introduced DLT registration, what it means for your business, and the consequences of operating without a valid DLT registration in India.
A detailed walkthrough of the PE–TM chain binding process — the final and essential step to authorise Fivo SMS to send messages on behalf of your registered business entity.