TRAI's Commercial Communication Rules (TCCCPR): Can Your Voice Bot Legally Call?
Yes — a voice bot can place calls in India, provided you follow TRAI's TCCCPR 2018. That means registering as a sender on the Distributed Ledger Technology (DLT) platform, using approved headers and templates, respecting consent and Do Not Disturb (DND) preferences, and calling from the correct number series for promotional versus service calls.
This is an explainer, not legal advice. For obligations specific to your organisation, consult a qualified advisor and the official regulation.
The Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) came into force with effect from 28 February 2019 and govern all commercial communication — including automated voice bot calls — in India (TRAI). The Telecom Regulatory Authority of India (TRAI) built the framework on a blockchain-based Distributed Ledger Technology (DLT) system to record entities, headers, templates, consent and complaints.
So your voice bot can legally call — but only inside these rules. Here is what they require.
What Does TCCCPR 2018 Actually Require?
At its core, TCCCPR routes all commercial communication through registered entities, based on the preference and consent of customers. The DLT platform underpins this: the ecosystem already carries roughly 2.5 lakh Principal Entities, more than 6 lakh headers, and over 55 lakh approved message templates (TRAI, Unsolicited Commercial Communication).
For a voice bot deployment, three registrations matter.
- Principal Entity (PE) registration — your business registers on the DLT platform with an access provider (telecom operator).
- Telemarketer registration — the entity actually placing calls must be a Registered Telemarketer (RTM); using unregistered telemarketers invites action.
- Headers and templates — commercial content flows through registered, approved templates rather than free-form scripts.
Why can't a voice bot just dial from any 10-digit number? Because TRAI's 2025 amendment restricts senders from using ordinary 10-digit numbers for telemarketing, requiring commercial communication to originate from designated headers or specific number series (PIB, 2025).
Promotional vs Service vs Transactional — Why Does It Matter?
The category of your call decides the consent you need and the number you dial from. The Department of Telecommunications (DoT) defines them clearly (PIB, 2024).
Call type | Definition (per DoT/TCCCPR) | Consent basis |
|---|---|---|
Promotional | Commercial voice call for which the sender has not taken explicit consent from the recipient | Requires explicit consent; blockable via DND |
Service | Call made with consent or a registered template to facilitate, complete or confirm a transaction the recipient consented to | Consent-based / template-based |
Transactional | Non-promotional call for time-critical alerts to the sender's own customers or account holders | Implicit for own customers |
Which Number Series Must Your Voice Bot Use?
This is where many teams get caught. TRAI's 2025 amendment ties the number series to the call type (PIB, 2025).
- The 140 series continues to be used for promotional calls.
- The newly designated 1600 series (160xxxxxxx) is for transactional and service calls.
The DoT allocated the 160 series on 30 May 2024 specifically so citizens can distinguish genuine service calls from spam. Notably for financial services, service and transactional calls from entities regulated by RBI, SEBI, PFRDA and IRDAI start from 1601 (PIB, 2024). If you are a Banking, Financial Services and Insurance (BFSI) player, this series is where legitimate customer-servicing bot calls belong. Our BFSI voice bot guide explains where automated calling fits across the customer journey.
How Do Consent and the DND Registry Work?
Customers register preferences on the Do Not Disturb (DND) registry to block promotional calls. The 2025 amendment tightened consent handling significantly (PIB, 2025):
- A sender shall not seek consent from a customer who has opted out before 90 days from the opt-out date — though the customer may opt in any time.
- Consent given to complete an ongoing transaction is valid for only 7 days.
- Implicit consent for transactional and service communication is valid only for the duration of the contract — after that, no service call without fresh explicit consent.
- The amendments require disclosure of the use of auto-dialers / robo calls — directly relevant to voice bots.
What Are the Consequences of Getting It Wrong?
The regulation frames these as practices it prohibits — the enforcement is real. The 2025 amendment introduced graded action against senders (PIB, 2025).
Situation | Action prescribed |
|---|---|
First violation of the regulatory threshold | Outgoing services of all the sender's telecom resources barred for 15 days |
Subsequent violations | All telecom resources (including PRI/SIP trunks) disconnected across providers for one year; sender blacklisted |
Access provider misreporting UCC counts | Financial disincentive of ₹2 lakh / ₹5 lakh / ₹10 lakh for first, second and subsequent instances |
The complaint window for customers is now 7 days (up from 3), and access providers must act against unregistered senders within 5 days. In short — a non-compliant voice bot campaign can cost you your calling lines. See how to achieve 100% call compliance in BFSI with AI for the controls that keep you inside the rules.
How AI Helps You Stay TCCCPR-Compliant
YuVoice, YuVerse's voice AI platform, is designed to operate within TRAI's framework. It runs calls from registered templates rather than ad-hoc scripts, can be configured to dial from the correct series — 140 for promotional, 1600 for BFSI service and transactional outreach — and respects consent and opt-out states so suppressed numbers are not called. Every call is logged with a timestamp, giving you the audit trail regulators and access providers expect. That makes it far easier to prove your bot only reached consenting customers with approved content. Pair it with our note on automating payment reminders with AI voice calls to see compliant service calling in action.
FAQ
Is a voice bot legal in India under TCCCPR 2018? Yes, if you comply. You must register as a sender on the DLT platform, use approved headers and templates, honour consent and DND preferences, disclose auto-dialer use, and call from the correct number series for your call type.
What is the difference between the 140 and 1600 number series? The 140 series is designated for promotional calls; the 1600 series is for transactional and service calls. For BFSI entities regulated by RBI, SEBI, PFRDA and IRDAI, service and transactional calls start from 1601.
Do I need consent for every voice bot call? Promotional calls require explicit consent and can be blocked via DND. Transactional calls to your own customers rely on implicit consent for time-critical alerts, and service calls use consent or a registered template — but the 2025 amendment limits how long that consent lasts.
What is DLT registration and why does it matter? Distributed Ledger Technology (DLT) is the blockchain-based system TRAI mandates for registering senders, telemarketers, headers, templates and consent. Calling outside this registered chain exposes you to enforcement action.
Can TRAI disconnect my numbers for spam? Yes. The 2025 amendment allows outgoing services to be barred for 15 days on a first violation, and disconnection across all providers for one year plus blacklisting on subsequent violations.
Does TCCCPR apply only to telecom or to all businesses? It applies to all commercial communication regardless of sector — any business or telemarketer sending promotional, service or transactional voice calls must operate within the TCCCPR framework.
Conclusion
TCCCPR 2018, and its 2025 amendments, do not stand between you and your customers — they demand that automated calling be registered, consented and correctly categorised. Get your DLT registration in order, dial from the right series, disclose the auto-dialer, and honour opt-outs, and your voice bot calls legally and confidently. For the compliance foundation, review how to ensure voice AI compliance with RBI guidelines.
Deploy a voice bot that calls within TRAI's rules from day one. Talk to the YuVerse team
References
- TCCCPR overview (Telecom Regulatory Authority of India) — https://trai.gov.in/tcccpr
- TRAI Strengthens Consumer Protection with Amendments to TCCCPR, 2018 (PIB, 12 Feb 2025) — https://www.pib.gov.in/PressReleasePage.aspx?PRID=2102413
- DoT allots separate numbering series exclusively for service and transactional voice calls (PIB, 30 May 2024) — https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=2022249®=48&lang=2