India's SMS compliance system is unlike every other market in this series. In Nigeria, Kenya, and Tanzania, the core requirement is registering a sender name with each operator. In Australia and the US, you register with a centralized authority or registry. India requires you to register three distinct things, your business entity, your sender header, and the exact text of every message you intend to send, before a single message can reach a recipient. Miss any one layer, or let a single character in your message body differ from the registered template, and the carrier's system drops the message silently. Your platform shows it as sent. It never arrives.
Business SMS in India operates under the Telecom Commercial Communications Customer Preference Regulations (TCCCPR 2018), enforced by the Telecom Regulatory Authority of India (TRAI). All commercial SMS requires three-layer DLT registration: entity registration (your business identity), header registration (your sender ID), and content template registration (the exact text of each message type). Real-time template scrubbing at the network level blocks any message whose content does not match an approved template exactly. As of May 2025, all message headers automatically carry a category suffix appended by the carrier during scrubbing: -T for Transactional, -S for Service, -P for Promotional, and -G for Government.
India is the world's second-largest mobile market with over 1.18 billion mobile subscribers. For organizations running vaccination reminder programs, beneficiary communication workflows, or field staff coordination in India, the DLT framework is not optional and not avoidable. The registration system was designed to eliminate spam and SMS fraud at scale, and it is technically enforced in real time at the carrier level. Understanding each of the three registration layers, and how template scrubbing works in practice, is prerequisite knowledge before any program in India is built.
What DLT is and why India built it
DLT (Distributed Ledger Technology) is the registration and verification framework used for commercial SMS under the TCCCPR, enforced by TRAI. It maintains synchronized records of registered entities, headers, templates, and provider relationships across participating telecom operators. Organizations sending commercial A2P SMS in India are generally required to register on a TRAI-approved DLT platform operated by one of the major Indian telecom operators.
The DLT platform serves four functions simultaneously. It maintains a registry of all verified sending entities. It maintains a registry of all approved sender headers (equivalent to sender IDs in other markets). It maintains a registry of all approved content templates. And it performs real-time scrubbing of every outgoing commercial SMS against all three registries before the message is released for delivery. Registering on one operator's DLT portal covers all networks: the platforms synchronize across operators. You do not need to register separately with Airtel, Jio, Vodafone Idea, and BSNL.
As of early 2026, the DLT ecosystem includes approximately 250,000 registered principal entities, 600,000 registered headers, and over 55 million approved content templates.
The three registration layers
Layer 1: Entity registration (Principal Entity)
Your organization must be registered as a Principal Entity on a TRAI-approved DLT portal. You can register on any operator's portal: Airtel, Jio, Vodafone Idea, BSNL, and others all operate approved platforms. The registration requires your legal business name (matching your registration documents exactly), your PAN card, GST registration where applicable, your business address, and an authorization letter. For NGOs and development sector organizations, the entity type is specified during registration.
Entity registration carries a one-time fee of approximately ₹5,900 plus GST at the time of writing, with annual renewal required. The DLT platform issues a unique Entity ID after approval, which typically takes one to three business days from complete document submission.
Layer 2: Header registration (Sender ID)
After entity approval, you register your headers. In India, a header is the six-character sender identifier that appears on the recipient's phone. For transactional and service messages, the header is six alphanumeric characters representing your brand (for example, BANKCO or HEALTHK). For promotional messages, a six-digit numeric header is used. The header type must match the message category it will be used for.
From May 6, 2025, following the TCCCPR 2025 Amendment, all SMS headers are automatically appended with a one-letter category suffix by the telecom operator during DLT scrubbing. This happens automatically and does not require any action on your part. A service message from HEALTHK via an Airtel route now appears on the recipient's phone as something like AI-HEALTHK-S, where AI are Airtel's operator prefix codes and -S indicates a Service category message. If the same organization sends a promotional message, it would appear with a -P suffix. The framework is designed to prevent promotional content from being transmitted through headers registered for other categories.
Header registration costs approximately ₹590 per header per year. Multiple headers can be registered under a single entity: if your organization runs both a patient communication program and a staff coordination program, those can run under different headers.
Layer 3: Content template registration
Every commercial message type you intend to send must be registered as a content template before it can be sent. A template consists of the fixed text of the message, with placeholders (typed variable tags such as or ) for the dynamic elements like patient names, appointment times, or confirmation codes. The fixed text must be exact. The variable type tags must be declared in advance.
Template approval is free but takes 24 to 72 hours per template. A template must include your organization's name or brand in the fixed text, so recipients can identify the sender even when the header is alphanumeric. The template must be submitted under the correct category (Transactional, Service, or Promotional), and a template registered under one category cannot be used to send content that belongs to another.
Each approved template is assigned a unique Template ID, which must be passed with every API call that sends that message type. If the Template ID is missing from the API request, the message will fail DLT scrubbing.
How template scrubbing works and why it fails silently
When you send a commercial SMS in India, the following sequence happens before the message reaches the recipient:
- Your SMS platform submits the message via the telecom operator's API.
- The operator's DLT scrubbing engine checks whether the sending header is registered and active.
- The engine checks whether the message content matches an approved template for that header, comparing the fixed text character by character.
- The engine checks whether the recipient is on the NCPR (National Customer Preference Register, India's DND system) and whether the message category is permitted to reach DND numbers.
If any check fails, the message is blocked and never delivered. Your platform receives a submission confirmation because your API call was accepted. The delivery report shows failure. This is the most common silent failure pattern in India: a program that appears to be sending successfully is actually delivering nothing because a template mismatch is being caught at step three.
The most common template mismatch causes are a single extra space, different capitalization, punctuation differences, or a variable tag format that does not match what was registered. A template registered as "Your appointment is confirmed for at ." will fail if the message body sent reads "Your appointment is confirmed for at ." because the generic format is being phased out in favor of typed variable tags. Every template registered after the October 2024 enforcement update must use typed variable tags.
Treat templates as application code, not marketing copy. Once a template is approved, even small editorial changes often require a new approval cycle. Organizations that expect to revise wording frequently should design template governance into their deployment process so operational teams do not accidentally introduce changes that trigger DLT scrubbing failures. The discipline required here is closer to software release management than content editing: changes go through a defined review and approval flow before they reach production.
Message categories and the DND system
India's DND system, the National Customer Preference Register, works differently from the DND systems in Nigeria, Kenya, or Tanzania. The category of the message determines whether it can reach a DND-registered number.
Transactional messages (-T) are the most restricted category: they are reserved for banks, regulated financial institutions, and OTPs directly related to banking transactions. They can reach DND numbers at any time of day.
Service messages (-S) cover updates, alerts, and notifications arising from an existing relationship or a user-initiated action, such as appointment confirmations, order updates, delivery notifications, non-bank OTPs, and operational alerts from programs or services the recipient is enrolled in. They can reach DND numbers and can be sent at any time.
Promotional messages (-P) cover marketing, offers, and any content that could be considered advertising. They cannot reach DND numbers. They can only be sent between 9 AM and 9 PM IST. Messages sent outside this window are dropped at the scrubbing layer and are not queued for later delivery. For organizations running promotional campaigns in India, this is a hard operational constraint: a campaign scheduled to start at 8 PM must be finished or paused by 9 PM or messages will be lost, not held.
Government messages (-G) cover public interest alerts, regulatory communications, and messages from government bodies.
The Service Explicit category, which previously covered informational messages to opted-in subscribers, was discontinued from May 7, 2025. All existing Service Explicit templates were automatically migrated to Promotional (-P) and are now subject to DND scrubbing and time window restrictions. Organizations that relied on Service Explicit for newsletters, member updates, or informational campaigns should audit whether their content has shifted to the Promotional category as a result.
The PE-TM binding chain
Since December 2024, a fourth mandatory step has been added to the compliance chain. Every organization must establish a PE-TM (Principal Entity to Telemarketer) binding chain on the DLT portal, linking their registered Entity ID to their SMS provider (Telemarketer). Without an approved PE-TM chain, messages are blocked regardless of whether entity, header, and template registrations are all in order.
The PE-TM chain is created on your DLT portal by requesting the chain and having your SMS provider accept the link from their side. Once approved, the chain is active. If you change SMS providers, a new chain must be established with the new provider before sending can resume. This is an operational dependency worth planning around, particularly for programs that might need to change routes for deliverability or pricing reasons.
The Digital Personal Data Protection Act 2023
India's Digital Personal Data Protection Act (DPDP Act) was enacted in August 2023. The implementing DPDP Rules were notified in November 2025. Full enforcement is being phased in, with the Data Protection Board of India established in November 2025 (Phase 1), consent manager framework becoming operational in November 2026 (Phase 2), and all remaining substantive provisions enforceable from May 2027 (Phase 3).
The Digital Personal Data Protection Act 2023 applies to the processing of personal data of individuals in India, and has extraterritorial reach to organizations outside India offering goods or services to Indian data subjects. Phone numbers collected for SMS programs are personal data. Many SMS marketing programs will rely on consent as their primary lawful basis under the DPDP framework, though the Act recognizes other lawful bases depending on the nature of processing. Organizations processing Indian personal data for SMS programs should be building their consent architecture now, ahead of the May 2027 full enforcement deadline, because the practical infrastructure for consent management, including supplier agreements and data processing records, takes time to implement.
The TRAI TCCCPR framework (DLT consent and DND management) and the DPDP Act operate in parallel. TCCCPR governs the messaging channel. DPDP governs the data. Both apply simultaneously.
India in the Asia compliance picture
India's DLT framework is the most technically complex compliance environment in this series of market guides. The Philippines and Indonesia both require sender registration and consent frameworks, but neither has real-time content template scrubbing at the carrier level. India's system locks down not just who can send but exactly what they can say in each message, making it the highest bar in terms of pre-launch preparation.
The operational implication for organizations running multi-market programs is that the India setup timeline is longer than any other market. Entity registration, header registration, template registration, PE-TM chain approval, and (for promotional programs) DCA consent registration together can take two to four weeks from initial submission to a compliant first send. That timeline needs to be built into program planning rather than discovered when launch is imminent.
For vaccination reminder programs, patient outreach, and field coordination workflows, the message categories are typically Service or Transactional, which avoids the DND and time-window restrictions that apply to Promotional. Classifying correctly at the template registration stage is essential: the category cannot be changed after approval without re-submitting the template.
BYOC architecture matters in India for the same reason it matters across Asia: your content templates, your Entity ID, your consent records, and your PE-TM chain are registered to your organization, not to any specific provider. If you need to change SMS providers in India, the DLT registration stays with you. Only the PE-TM binding chain needs to be updated to point to the new provider. That portability is worth preserving from the outset by treating the compliance infrastructure as an organizational asset rather than a provider dependency.
Frequently asked questions
What are the three DLT registration layers required for SMS in India? Entity registration (your organization registered as a Principal Entity on a TRAI-approved DLT portal), header registration (your sender ID, six characters, registered under the correct message category), and content template registration (the exact text of each message type you intend to send, with typed variable placeholders). All three must be complete and a PE-TM binding chain must be established with your SMS provider before any commercial message can be delivered.
Why does my platform show messages as sent when recipients are not receiving them? This is the template scrubbing pattern. Your SMS provider accepted the message (showing it as submitted or sent), but the carrier's DLT scrubbing engine blocked it because the message content did not exactly match the registered template. Even seemingly minor differences, an extra space, different punctuation, or a generic tag instead of a typed tag like , cause a block. Check your template registration and compare the exact content of your message body against the registered template character by character.
What happened to the Service Explicit message category? Service Explicit was discontinued from May 7, 2025, under the TCCCPR 2025 Amendment. All existing Service Explicit templates were automatically migrated to the Promotional category and are now subject to DND scrubbing and the 9 AM to 9 PM sending window restriction. Organizations that previously used Service Explicit for newsletters, member updates, or informational campaigns should review their current template categories and update their consent and scheduling practices accordingly.
Does the DLT registration cover all Indian networks? Yes. Registering on any one TRAI-approved DLT portal, whether Airtel, Jio, Vodafone Idea, BSNL, or another approved operator, covers all networks. The DLT platforms synchronize across operators. You do not need to register separately with each carrier.
Does India's data protection law apply to organizations outside India? Yes. The Digital Personal Data Protection Act 2023 has extraterritorial reach and applies to organizations outside India that process the personal data of individuals located in India. Organizations running SMS programs targeting Indian recipients, regardless of where they are based, should be building DPDP-compliant consent and data management practices ahead of the May 2027 full enforcement deadline.
This article provides general operational information and should not be considered legal advice. Organizations should consult qualified legal or data protection professionals regarding their specific compliance obligations under Indian telecommunications and data protection law.
Talk to our team about running a compliant SMS program in India and across your other operating markets.
