OBD Calling & DND Compliance India 2026: TRAI Rules Explained

Why DND Compliance Matters for OBD Campaigns

India's Do Not Disturb (DND) registry, maintained by TRAI under the National Customer Preference Registry (NCPR), protects consumers from unsolicited promotional calls and messages. For businesses running OBD campaigns, DND compliance is not optional — violations result in financial penalties, telecom blacklisting, and reputational damage.

This guide explains every compliance requirement your business needs to meet before running an OBD calling campaign in India.

The TRAI DND Framework: What It Covers

The Telecom Commercial Communications Customer Preference Regulations (TCCCPR) govern all commercial communications in India, including OBD voice calls. The framework distinguishes between two types of calls:

Promotional calls: Calls made to generate sales interest, promote a product/service, or solicit a transaction with someone who has not specifically requested the call. These are the most tightly regulated. Transactional calls: Calls related to an existing relationship — EMI reminders, appointment confirmations, order updates, policy renewal alerts. These are exempt from the full DND restrictions.

Understanding which category your campaign falls into determines your compliance obligations.

The NDNC Registry: What It Is and How Scrubbing Works

The National Do Not Disturb (NDNC) registry (also called the DND registry) contains phone numbers that have requested to stop receiving promotional communications. Any number registered on the NDNC cannot receive promotional OBD calls.

How DND scrubbing works:

• You provide your contact database to your OBD provider
• The OBD platform queries the TRAI NDNC registry (via licensed API access that only registered telemarketers have)
• Numbers matching the DND registry are automatically removed from the campaign list
• The cleaned list is used for dialling
• A scrubbing report showing removed numbers is generated for compliance records

TRAI requires DND scrubbing to happen within 7 days before the campaign runs — not at the time of database creation. If your campaign runs on Day 1 with a scrubbing done 10 days ago, new DND registrations in that window may not be excluded.

At Scalify Labs, DND scrubbing is performed within 24 hours of campaign launch, every time.

Calling Hours: TRAI's Time Restrictions

Promotional OBD calls: Permitted between 9:00 AM and 9:00 PM only. Calls outside this window are a TRAI violation regardless of DND status. Transactional OBD calls: Broader window permitted, though best practice is to keep within 8:00 AM to 9:00 PM. Calls at 2 AM for an EMI reminder, even to an existing customer, can attract consumer complaints.

Campaign scheduling should factor in connection rate data alongside compliance. In practice, the 6–9 PM window produces the highest connection and response rates for most Indian consumer segments, staying well within the 9 AM–9 PM permitted window.

Promotional vs Transactional: The Grey Areas

Several common OBD use cases fall in a grey zone between promotional and transactional:

EMI reminders to existing loan customers: Transactional — existing loan relationship. DND exemption applies. Insurance renewal reminders to existing policyholders: Transactional — existing policy relationship. DND exemption applies. Admission campaign calls to a purchased student database: Promotional — no prior relationship. Full DND scrubbing required. Re-engagement calls to lapsed customers (2+ years inactive): Grey area — prior relationship existed but may have expired. Safest to treat as promotional. Webinar invitations to your existing client list: Transactional if they are existing clients, promotional if the list includes non-clients. Calls to students who filled an enquiry form on your website: Grey area — they expressed interest but have not entered a service contract. Treat as promotional; scrub against DND.

When in doubt, apply full DND scrubbing. The cost of removing some contactable numbers is far lower than the cost of a TRAI violation.

TRAI Penalties for DND Violations

Penalties under TCCCPR for verified violations:

Violation	Penalty
First violation (per number called on DND)	₹25,000
Second violation (same number)	₹50,000
Third and subsequent violations	₹1,00,000 or disconnection
Sending from unregistered telemarketer	Immediate service disconnection

Complaints are filed by consumers through the TRAI DND app or by calling 1909. TRAI investigates complaints and charges violations against the registered telemarketer (your OBD provider) and, by extension, the business that commissioned the campaign.

This is why working with a licensed, TRAI-registered telemarketer is non-negotiable. An unlicensed OBD provider cannot legally access the NDNC scrubbing API, meaning they cannot perform proper DND scrubbing — and violations fall on your business.

DLT Registration: The Separate Requirement

DLT (Distributed Ledger Technology) registration under TRAI governs SMS A2P communications. For OBD voice calls, DLT registration is not required — it applies to SMS, not voice.

However, if your OBD campaign includes an SMS follow-up after the voice call (a common workflow — "Press 1 and we'll SMS you our brochure"), that SMS falls under DLT and requires your registered sender ID and pre-approved template.

Consent-Based OBD: The Safest Path

The cleanest compliance posture for OBD campaigns is consent-based outreach — calling only numbers that have explicitly opted in to receive calls from you. This eliminates DND concerns entirely because consent supersedes DND registration.

How to build a consent-based OBD database:

• Website enquiry forms with explicit "I agree to receive calls" checkbox


• Missed call campaigns where customers call your number to opt in


• WhatsApp opt-in flows followed by OBD follow-up


• Event registrations with communication consent

Consent-based databases also produce higher response rates — you're calling people who asked to be called.