New: Kedeyo Voice Bot is here!

Book a free demo

Compliance

TRAI DND Compliance: How to Run Outbound Without Penalties

How TRAI's DND framework actually works in 2026, what scrubbing means, and how to run outbound campaigns at scale without compliance penalties.

3 May 202610 min read
Share
Cover image for TRAI DND compliance guide for outbound calling

Most outbound teams in India have heard of "DND" but treat it as a vague compliance worry. It isn't — it's a specific regulatory framework with specific penalties, and ignoring it is the fastest way to get your sender ID blacklisted across carriers. Here's exactly how it works in 2026 and how to stay clean while running outbound at volume.

The framework, in plain terms

TRAI maintains the National Customer Preference Register — a list of phone numbers whose owners have asked not to receive promotional calls or SMS. Categories include 'fully blocked', 'partially blocked' and category-specific blocks (real estate, financial services, etc.). Every outbound campaign must check the register before dialling.

TRAI DND scrubbing flow diagram
Every outbound list goes through NCCP scrubbing before agents ever dial.

What counts as a violation

  • Dialling a number on the NCCP for promotional purposes.
  • Calling outside the 9 AM – 9 PM IST window.
  • Calling without a registered DLT header / sender ID.
  • Failing to record consent for a number you call.
  • Repeated calls to the same number after a 'do not call' request.

What's exempt

Transactional and service calls — OTPs, payment confirmations, EMI reminders to existing customers, delivery notifications — fall outside the DND framework. The line gets blurry when service messages include promotional content; safest to keep them separate.

How modern CCaaS handles compliance

CCaaS compliance dashboard showing DND scrub logs and audit trails
Compliance is automated — scrub on every list, log every decision.
  1. Real-time NCCP sync. The platform pulls the register daily and scrubs every list at dial time.
  2. Calling-window enforcement. Campaigns auto-pause at 9 PM and resume at 9 AM IST.
  3. DLT header binding. Every outbound SMS or voice call carries a registered header.
  4. Consent capture. Form submissions store an opt-in record alongside the number.
  5. Audit logs. Every scrub decision is logged with timestamp for compliance review.

Operational checklist

  • Register your DLT header IDs through your telecom provider before you launch any campaign.
  • Document explicit consent for every contact in your outbound list — date, source, and intent.
  • Have a written DND-suppression process — when a customer says "don't call", remove them within 24 hours.
  • Keep scrub logs for at least 90 days; some regulators want longer retention.
  • Run a monthly compliance review — sample calls, check timestamps, confirm scrub coverage.

Bottom line

TRAI compliance is not optional and the penalties scale fast if you ignore it. Kedeyo's auto dialer handles NCCP scrubbing, calling-window enforcement and DLT binding automatically — you focus on the campaign, the platform handles the rules. Book a demo for a compliance walkthrough.

Source: TRAI's official site publishes the current regulations and penalty schedules.

Frequently asked questions

What is TRAI DND scrubbing?+
Cross-checking your contact list against the National Customer Preference Register (NCCP) before dialling. Numbers on the register are excluded.
Are transactional calls exempt from DND?+
Yes — transactional and service messages (OTP, order confirmations, payment reminders to existing customers) are exempt. Promotional calls are not.
What are TRAI calling hours in India?+
Outbound promotional calling is restricted to 9:00 AM to 9:00 PM IST. Calls outside this window are non-compliant.
What's the penalty for a TRAI violation?+
₹1,000 for the first offence, ₹5,000 for the second, ₹10,000 from the third onwards — per complaint.
Does Kedeyo handle DND scrubbing automatically?+
Yes — every outbound batch is scrubbed against the NCCP before the dialler fires. Audit logs are kept for compliance review.

Kedeyo Editorial

Reviewed by the Kedeyo product team

Last updated

3 May 2026