01What is a principal entity?
A principal entity (PE) is the business or organisation that sends commercial communications — SMS and calls — in India and is registered as their sender of record on the Distributed Ledger Technology (DLT) platforms required by TRAI's TCCCPR 2018 regulations. Banks, retailers, hospitals, schools, government departments and startups sending OTPs are all principal entities. Registering on one access provider's DLT portal, with the organisation's identity documents, produces an entity ID — the PE ID — that identifies the business to every operator.
The PE ID owns everything that follows. Under it the business registers its headers (the sender IDs recipients see), its content templates with their variables and categories, and consent templates for messages that need explicit permission. It declares the telemarketers allowed to carry its traffic through PE-TM chain binding. Every commercial SMS then carries the PE ID and the matching template ID, and the operator's DLT scrubbing checks that header, template, chain and the recipient's consent and DND preferences all line up before delivery.
Responsibilities split three ways. The principal entity decides what is sent, to whom and under which header and template, and answers for consent and content. Telemarketers — SMS platforms and aggregators — transmit messages on its behalf along the declared chain. Access providers (operators) run the DLT platforms, scrub each message and deliver it. A business cannot outsource being the principal entity: even when an agency or SMS provider does the paperwork, the PE ID, headers and templates belong to the business, and complaints about unsolicited messages are traced back to them.
Key takeaways
- A principal entity (PE) is the business registered on India's DLT platform as the sender of record for its commercial SMS and calls.
- Registration gives the PE an entity ID, the PE ID, which owns its headers, content templates, consent templates and telemarketer chains.
- Telemarketers transmit for the PE and operators scrub and deliver, but the PE stays accountable for what is sent in its name.
- Every commercial SMS must carry the PE ID and a matching template ID, and travel a PE-TM chain the PE has declared.
- Registering on one access provider's DLT portal is enough; the entity is recognised across operators.
02Why does a principal entity matter?
The principal entity is the precondition for every SMS a business sends in India. A PE registered under the wrong legal name, an agency holding the only login or an expired document can stop OTPs and alerts overnight. A PE that understands its role keeps control of its headers, templates and chains when it changes vendors, and can account to an operator or regulator for any message sent in its name.
03A principal entity: key facts and limits
- Who
- The business that sends commercial SMS and calls in India
- Identifier
- PE ID (entity ID) issued on DLT
- Owns
- Headers, content templates, consent templates, PE-TM chains
- Registered on
- One access provider's DLT portal, recognised across operators
- Rules behind it
- TRAI's TCCCPR 2018 and later amendments
- Sent with every SMS
- Header + PE ID + content template ID
04 · How it works, step by step
How does a principal entity work?
- Step 1
Register the entity
On one access provider's DLT portal, register as a principal entity — portals may call it an enterprise or sender — with the organisation's documents and an authorised signatory, and pay the platform's fee.
- Step 2
Receive the PE ID
After verification the portal issues the entity ID. Give it to your SMS provider: it must travel with every message.
- Step 3
Register headers and templates
Under the PE ID, register headers for each message category and content templates with {#var#} placeholders, plus consent templates where explicit consent is required.
- Step 4
Bind the telemarketer chain
Declare each telemarketer that carries your traffic, in order, and approve the final chain once they have all accepted.
- Step 5
Govern it
Keep the portal login with the business, review templates and chains when vendors change, and renew documents before they lapse.
05Example: A hospital group takes back its login
A Coimbatore hospital group let an agency register its DLT entity using the agency's email and login. When the group moved to a new SMS provider, appointment reminders stopped: the new provider could not see the headers or templates, and the agency was slow to respond. The group regained access to its principal entity account on the DLT portal with its own documents, moved the login to its IT head, declared the new provider's chain and resumed reminders two days later. It now keeps the PE ID, portal access and a list of every header and template in its compliance register.
06 · Common mistakes, and the fix
Common mistakes with a principal entity
Letting a vendor own the account
If an agency registers with its own email and login, you lose control when you change vendors. Register in the business's name with a company-owned login and contact.
Names and documents that do not match
The entity name must match the registration documents exactly; mismatches delay or block approval. Use the legal name as it appears on your documents.
Messages without your own IDs
SMS missing the PE ID, or carrying a template ID registered under another entity, is rejected in scrubbing. Check your provider sends your IDs on every message.
Forgetting the chain after a vendor change
Headers and templates stay with the PE, but a new provider needs a new PE-TM chain approved before its traffic is delivered.
07PE FAQs
What is a principal entity in DLT registration?+
Where do I find my DLT entity ID?+
What is the difference between a principal entity and a telemarketer?+
Do I need to register as a principal entity for WhatsApp messages?+
08 · Tips from the bench
Best practices for a principal entity
- Keep the PE ID, portal login and authorised contact in your compliance register.
- Review headers and templates every quarter and retire the ones you no longer use.
- Ask every SMS vendor for its telemarketer ID and full chain before signing.
- Treat DLT consent and WhatsApp opt-in as separate records with separate wording.