DND & TRAI Compliance for Business Messaging in India
DND (Do Not Disturb) is TRAI's consumer registry letting a mobile number opt out of unsolicited commercial communication. It works alongside - but separately from - DLT sender/template registration, and TRAI has continued tightening enforcement, most recently through a September 2026 amendment specifically targeting automated calls.
This page explains what DND actually governs, how it differs from DLT, and what changed in TRAI's latest regulatory update - so a business sending SMS or voice communication in India understands its actual compliance obligations, not just the term "DND."
What Is DND, And What Does It Govern?
DND is a consumer-facing registry where a mobile number holder registers a preference - Full DND blocks unsolicited commercial communication broadly, while Partial DND allows the consumer to permit specific categories. It governs whether a number should receive unsolicited commercial communication at all, distinct from DLT, which governs which registered sender and template can send a message and its exact approved content.
DND vs DLT
| Aspect | DND Registry | DLT Registration |
|---|---|---|
| What it governs | Whether a consumer number can receive unsolicited commercial communication at all | Which sender and template can send a message, and its exact approved content |
| Who registers | Consumers, via the DND registry/app | Businesses, as senders and template owners |
| What it controls | Full or partial blocking of promotional communication | Sender ID, template wording and message classification |
| Regulator | TRAI | TRAI |
See DLT Compliant CPaaS for how sender/template registration itself works - this page focuses specifically on DND and the broader UCC enforcement framework.
TRAI's September 2026 Amendment
TRAI notified the Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 on September 18, 2026, amending the existing framework governing promotional calls and messages. The amendment specifically brings Application-to-Person (A2P) automated calls - voice calls initiated by an application, software or automated platform without direct human dialing, including autodialing, robocalls and pre-recorded/artificial voice technology - explicitly under the Unsolicited Commercial Communication (UCC) framework.
Automated calls must declare upfront that the call is automated
Calls made without required disclosure are treated as UCC
Enforcement action can trigger after a small number of unique complaints combined with AI/ML-based sender flagging by telecom operators
Repeat non-compliance risks escalating consequences, including suspension of outbound calling services
Questions About Compliant Sending?
Talk to our team about DLT, opt-in handling and staying within current TRAI requirements.
Practical Compliance Guidance
Track Consent, Not Just Templates
DLT template approval doesn't substitute for tracking whether a specific number actually opted in to promotional content.
Monitor Complaint Signals
Rising block/report rates on a sender ID are worth investigating before they trigger enforcement action.
This page explains the regulatory structure as a starting reference - it isn't legal advice, and TRAI's rules can change again. Verify current requirements with TRAI's own notifications or your compliance advisor for decisions specific to your business.
DND & TRAI Compliance FAQs
What is DND in the context of business messaging?
DND (Do Not Disturb) is TRAI's consumer preference registry that lets a mobile number opt out of unsolicited commercial communication - Full DND blocks promotional messages and calls broadly, while Partial DND allows specific categories a consumer chooses to permit.
What's the difference between DND and DLT?
DND is about consumer preference - whether a number wants to receive commercial communication at all. DLT is about sender/template registration - which business can send what content. Both are TRAI-regulated but govern different things. See the comparison table on this page.
What changed in TRAI's 2026 regulations?
TRAI notified the Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 on September 18, 2026, bringing automated calls - including autodialing, robocalls and pre-recorded/artificial voice calls - explicitly under its Unsolicited Commercial Communication (UCC) framework, requiring such calls to declare themselves as automated.
Does DND apply to transactional messages?
Transactional messages tied to a customer's own action (like an OTP or order confirmation) are generally exempt from DND blocking, but promotional content is not - correct message classification is what determines which rules apply, covered on SMS Blast API and SMS Pricing in India.
What happens if a business sends unsolicited communication despite DND?
Enforcement can trigger after a small number of unique complaints in a short window, combined with AI/ML-based flagging of the sender's calling line by telecom operators - repeat violations risk service suspension for the sender.
Does the 2026 amendment apply to automated calls only, or messages too?
The amendment specifically targets Application-to-Person (A2P) automated voice calls - autodialing, robocalls and pre-recorded/artificial voice technology - requiring disclosure that the call is automated. Businesses running outbound voice/IVR campaigns should review current requirements for their use case.
Does Teleopedia handle DND and DLT compliance for me?
DLT entity and template registration is handled as part of onboarding - see DLT Compliant CPaaS for that process. DND compliance depends on how you build and maintain your own opted-in/consented contact lists, which is a business responsibility Teleopedia's platform supports but doesn't replace.
Can a business message a number on the DND registry at all?
Yes, for transactional and consented communication - DND primarily restricts unsolicited promotional content, not communication a customer has consented to or that relates to a transaction they initiated.
How do I avoid DND/UCC violations for outbound voice calls?
Ensure automated calls declare themselves as such where required, only call numbers with appropriate consent for the message category, and monitor complaint and block rates - see Outbound Dialer API for how this applies to automated calling specifically.
Where can I verify current DND/TRAI rules?
TRAI's own notifications and regulations are the authoritative source - policies have changed before and can change again, so verify current requirements directly with TRAI or your compliance advisor rather than relying on older guidance.
Ready to unify your business communication?
Most businesses are live on their own branded panel within days, not months - talk to our team today and see how fast you can start sending.