NDNC + DND compliance for B2B sales calls — what TRAI actually requires

If you are doing outbound sales to Indian phone numbers, you have heard "B2B calls do not need to follow DND" at some point. It is one of those half-true industry beliefs that gets businesses into trouble at scale.

The actual rule is more nuanced. This post explains what TRAI actually requires for outbound B2B calls, when the NDNC scrub matters, and how to set up your dialer to stay on the safe side.

What NDNC (now NCPR) is

NDNC stands for National Do Not Call registry, which TRAI renamed to NCPR (National Customer Preference Register) under the TCCCPR 2018 regulation. Both names are used interchangeably.

Every Indian mobile subscriber can register their preference on NCPR:

• Fully Blocked — no commercial calls or SMS at all
• Partially Blocked — opt out of specific categories (banking, real estate, tourism, etc.)

The list is maintained by the telecom operators and updated daily. Senders are expected to scrub their outbound lists against NCPR before each campaign.

The B2B "exemption" myth

The common claim is "calls between businesses are not regulated by TCCCPR." This is incorrect on three counts:

1. The recipient is identified by phone number, not by intent. If a mobile number is on NCPR, TRAI's regulation kicks in regardless of whether you call to sell software or sell tickets. There is no special status for "this person works in procurement."

2. The exempted categories are narrow. TCCCPR Regulation 19 lists exemptions for transactional messages (OTPs, delivery confirmations, banking alerts, govt notifications). Marketing calls to a corporate contact — even if you got the number from LinkedIn — are not transactional and not exempt.

3. Even "service" calls have rules. Service-Implicit (the recipient has an existing relationship with you and you are informing them about it) is permitted, but the call must be related to that relationship. Calling an existing customer to pitch a new product line crosses into Promotional and needs NCPR scrub + consent.

The realistic B2B carve-out is much smaller than people assume:

| Call type | NCPR scrub required? | |---|---| | Cold sales call to a prospect | Yes | | Follow-up to a download-form lead | Yes (consent helps, scrub still needed) | | Existing customer service ticket follow-up | No (service) | | Cross-sell pitch to existing customer | Yes (it is promotional) | | Demo confirmation call | No (transactional) | | Renewal reminder | Borderline (lean towards scrubbing) |

The 9 AM – 9 PM window

TCCCPR also caps the calling window to 9:00 to 21:00 local time. Calls outside this window are violations even for service or transactional messages. Two practical implications:

• Saturday/Sunday calling is allowed (TRAI does not exempt weekends)
• "Local time" means the recipient's local time, which in India is one zone (IST). For international agents calling Indian numbers, this is the relevant clock.

How a compliant dialer enforces this

If you build the dialer yourself or buy one without enforcement, you are relying on agent training to stay compliant. That fails the first time a queue runs after 21:00 by accident. A compliant setup enforces:

1. NCPR scrub at queue-import time — every number is checked against the operator NCPR feed before being eligible to dial
2. Time-window enforcement — the dialer refuses to start dialing outside 9-21 IST
3. DLT category match — the campaign's DLT template category must align with the call intent (service vs promotional)
4. Consent recording — if you claim consent-based exemption, the consent record must be queryable per recipient
5. Audit log — every blocked number and the reason is logged for regulator inquiry

dialque does this at the queue level — the import-CSV pipeline marks NCPR-blocked numbers as "Excluded — NCPR registered" and they never enter the dial queue. You can still override on a per-record basis with documented consent, but it requires a recorded justification.

Consent — the only legitimate override

The TCCCPR allows commercial communication to NCPR-blocked subscribers if you have explicit consent. The catch is that the consent must be:

• Specific to your entity (a generic "I agree to receive offers" form does not count)
• Time-stamped and stored
• Revocable on demand (you must honour opt-out within 24 hours)
• Maintained even if the relationship ends, for at least 90 days after revocation

Most teams do not have this infrastructure and should not rely on consent as a NCPR override. Easier to just scrub.

Penalties

TCCCPR has a graduated penalty schedule:

• First violation: warning + correction notice
• Second violation: ₹1,000 per complaint
• Third+ violations: up to ₹5,000 per complaint + sender ID deactivation

In practice the biggest cost is not the fines — it is the header deactivation. When a sender ID is paused for repeated complaints, you cannot send anything from it for the duration of the suspension. For a sales-led business this can be a week of lost outbound.

What "good" looks like — operational checklist

• NCPR scrub on every list at import; weekly refresh of the operator feed
• 9 AM – 9 PM dial window enforced at the dialer, not the agent
• DLT template category matches the call intent
• Consent records (where claimed) are tied to the specific recipient and timestamped
• An opt-out keyword ("STOP", or pressing 9 on IVR) is honoured within 24 hours
• Audit log of every blocked number with the block reason
• Monthly review of complaints in the Vilpower / Jio / Airtel portals

Frequently asked questions

If the recipient gave me their card at a conference, is that consent?

No, not in the TCCCPR sense. Consent must be specific to commercial communication from your entity, and time-stamped. A business card exchange is not consent for marketing calls.

Does the 9-21 window apply to scheduled callbacks?

Yes. A scheduled callback from the recipient does not override the window. If they ask you to call them at 21:30, you call them at 21:00 the same day or 9:00 the next.

Can I use an international number to bypass NCPR?

No. The destination number (Indian mobile) triggers TCCCPR jurisdiction. The origin does not matter.

Does this apply to recorded voice broadcasts ("OBD" / robocalls)?

Yes, and more strictly. Voice OBD is heavily restricted; expect operator-level scrutiny.

The short version: NCPR scrub is non-optional for B2B prospect calls, the 9-21 window is enforced regardless of category, and consent-based exemptions need real infrastructure to be defensible. Set up the scrub at the queue level and stop relying on agent discipline.