160 Series Non-Compliance Penalties: What BFSI Entities Risk in 2026

India’s 160 series migration mandate is not optional. The Telecom Regulatory Authority of India issued a binding Direction on 19 November 2025 — backed by DoT’s original numbering allocation of 30 May 2024 — that converts every phase deadline into a hard legal obligation. For BFSI entities still relying on standard 10-digit mobile numbers for service and transactional calls, the clock has already run out for many categories. The question compliance officers and operations heads are now asking is blunt: what exactly happens if we miss it? This article answers that question precisely, drawing directly from the operative regulatory instruments.

Key Facts at a Glance

Item	Detail
Primary regulation	TCCCPR, 2018 (Second Amendment, 12 Feb 2025)
Governing bodies	TRAI / DoT / RBI / SEBI / PFRDA / IRDAI
Applies to	All BFSI entities regulated by RBI, SEBI, PFRDA, IRDAI making service or transactional voice calls
Mandated number series	1600xxxxxxx (1601xxxxxxx for financial entities)
First-violation penalty	Rs 2,00,000
Third-violation penalty	Rs 10,00,000 per instance
Blacklist trigger	5 valid complaints in any rolling 10-day period
Maximum blacklist duration	1 year — all telecom resources, all TSPs
Commercial bank deadline	1 January 2026 (TRAI Direction, PRID 2191647)
Voluntary adoption as of Nov 2025	485 entities, 2,800+ numbers

• BFSI entities that miss their phase-wise 1600-series migration deadline face classification as Unregistered Telemarketers (UTMs) under TCCCPR, 2018.
• Financial penalties scale from Rs 2 lakh (first violation) to Rs 10 lakh per instance for third and subsequent violations.
• Five valid consumer complaints in any 10-day rolling window trigger a 15-day suspension of all outgoing telecom services.
• Repeat violations attract a one-year disconnection and blacklisting across every Telecom Service Provider in India, making OTP delivery, customer alerts, and collections calls impossible.
• Sectoral regulators — RBI, SEBI, IRDAI, and PFRDA — can independently impose penalties on the same underlying conduct, creating a multi-layered enforcement exposure.
• The DPDP Act, 2023 adds a further penalty layer of up to Rs 250 crore for data-processing violations that overlap with non-compliant calling patterns.
• FreJun provisions 1600-series numbers, manages DLT template registration, and provides CDR logging to help BFSI entities achieve and maintain compliance.

Table of Contents

1. What Is the 160 Series Mandate and Why Does It Exist?
2. What Are the Phase-Wise Deadlines for Each BFSI Category?
3. What Happens When a BFSI Entity Misses Its 160 Series Deadline?
4. How Do the TCCCPR Financial Penalties Actually Work?
5. What Is the 15-Day Suspension and One-Year Blacklist?
6. What Is UTM Classification and Why Is It Catastrophic?
7. Which Sectoral Regulator Penalties Apply Simultaneously?
8. How Does the DPDP Act, 2023 Add to the Penalty Exposure?
9. Is There Criminal Liability for Number Misuse?
10. What Calling Behaviours Are Most Likely to Trigger a Complaint?
11. How FreJun Helps BFSI Entities Avoid These Penalties
12. Frequently Asked Questions
13. Key Takeaways
14. Compliance Disclaimer
15. References and Sources

Quick Answer: BFSI entities that do not migrate to the 1600-series face financial penalties from Rs 2 lakh to Rs 10 lakh per violation, a 15-day telecom suspension on first breach, and a one-year blacklist on repeat violations. Each missed deadline also triggers UTM classification, independent sectoral regulator action, and potential DPDP Act penalties. The single most severe consequence is the one-year blacklist — which kills OTP delivery, collections, and customer service calls simultaneously.

What Is the 160 Series Mandate and Why Does It Exist?

The 160 series mandate exists because India’s prior numbering regime created a dangerous trust vacuum. The 140xxxxxxx series — allocated for promotional calls — was used so heavily that consumers stopped answering it. Genuine banks and insurance companies then started using standard 10-digit mobile numbers for legitimate service calls. Fraudsters immediately exploited this pattern, impersonating financial institutions from ordinary mobile numbers. According to industry estimates, India recorded approximately 147 million spam-call complaints in 2024.

To close that gap, the DoT allocated the 160xxxxxxx series in May 2024 as a visually distinct, consumer-recognisable prefix for legitimate service calls. The TRAI Direction of 19 November 2025 (PRID 2191647) converted voluntary adoption into a mandatory phase-wise schedule for RBI-, SEBI-, and PFRDA-regulated entities. A follow-up Direction of 16 December 2025 (PRID 2205350) brought IRDAI-regulated insurers into the same framework. Together, these two instruments make non-migration a regulatory violation — not merely a missed administrative step.

What this means for your compliance team: The moment your applicable phase deadline passes without migration, every service or transactional call your entity makes from a non-1600 number is a potential violation. The penalty clock starts immediately.

Talk to FreJun’s Legal Team

Penalties for 160 series non-compliance are now active. If your entity is unsure about its migration status or phase deadline, FreJun’s legal team can walk you through the exact obligations that apply to your entity type and regulatory category.

What Are the Phase-Wise Deadlines for Each BFSI Category?

The TRAI Direction of 19 November 2025 (PRID 2191647) set specific phase-wise deadlines for RBI-, SEBI-, and PFRDA-regulated entities. Understanding which deadline applies to your entity is the first step in assessing your current exposure.

RBI-Regulated Entity Deadlines

Entity Category	Migration Deadline
Commercial banks (public sector, private sector, foreign banks)	1 January 2026
Large NBFCs (asset size above Rs 5,000 crore), payments banks, small finance banks	1 February 2026
Remaining NBFCs, co-operative banks, regional rural banks, smaller entities	1 March 2026

SEBI, PFRDA, and IRDAI Entity Deadlines

Entity Category	Migration Deadline
Mutual Funds and Asset Management Companies (AMCs)	15 February 2026
Qualified Stockbrokers (QSBs)	15 March 2026
Central Recordkeeping Agencies (CRAs) and Pension Fund Managers (PFRDA)	15 February 2026
IRDAI-regulated insurers	Notified separately — TRAI Direction, 16 December 2025 (PRID 2205350)

Notably, the NBFC asset-size cut-off of Rs 5,000 crore is the threshold that separates Phase II from Phase III for RBI-regulated non-banking financial companies. Entities should verify their own classification against the operative TRAI Direction text rather than secondary commentary, which on this point can vary. In my practice advising telecom-sector clients, the single most common error I see is entities misidentifying their own phase tier, resulting in a missed deadline that was entirely avoidable.

What this means for your compliance team: If any of these deadlines has already passed for your entity type, your exposure is live today. Begin the migration process immediately and document the steps taken, as a demonstrated good-faith compliance effort can be a mitigating factor in any regulatory inquiry.

What Happens When a BFSI Entity Misses Its 160 Series Deadline?

Missing a phase deadline triggers an automatic reclassification. Any service or transactional voice call made from a standard 10-digit number after the deadline is classified as Unsolicited Commercial Communication (UCC) from an Unregistered Telemarketer (UTM). That classification alone initiates a cascade of enforcement consequences under TCCCPR, 2018. Furthermore, the call may also trigger consumer complaint rights, sectoral regulator scrutiny, and data protection obligations simultaneously.

The Four-Stage Enforcement Cascade

First, every non-compliant call generates a potential consumer complaint through the DND app or the 1909 helpline. Second, complaints are aggregated across rolling 10-day windows. Third, when five valid complaints accumulate in any such window, TRAI’s complaint threshold is breached. Fourth, once the threshold is breached, outgoing service suspension is mandatory — not discretionary.

Consequently, the severity of the enforcement response depends on how quickly complaints accumulate — not on how large or systemically important the entity is. A bank with one million customers making 10-digit service calls faces the same threshold mechanism as a small NBFC. Additionally, this four-stage cascade can complete in under two weeks, which is far faster than any internal compliance review cycle.

What this means for your compliance team: Do not wait for a formal TRAI notice. The enforcement mechanism is complaint-driven and automated. The first sign of exposure is often a 15-day service suspension, not a warning letter.

How Do the TCCCPR Financial Penalties Actually Work?

The financial penalty structure under the TCCCPR Second Amendment of 12 February 2025 follows a graded escalation. TRAI levies these penalties on Telecom Service Providers (TSPs) for failing to act against violating entities. In practice, TSPs cascade these costs contractually to the Principal Entity responsible for the non-compliant calls. As a result, the entity bears the economic cost even though the formal levy falls on the TSP first.

The Three Penalty Tiers

• First instance of violation: Rs 2,00,000
• Second instance of violation: Rs 5,00,000
• Third and subsequent violations: Rs 10,00,000 per instance

These penalties apply per instance, not per campaign or per calling period. Moreover, they are imposed separately for registered and unregistered senders. A BFSI entity that runs multiple non-compliant calling campaigns simultaneously faces parallel penalty counts. Additionally, the financial disincentives are in addition to — not a substitute for — service suspension, blacklisting, and sectoral regulator action under the same conduct.

Furthermore, the penalties for invalid closure of consumer complaints are levied separately from the penalties for the underlying non-compliant call. This means a single non-compliant call that generates a complaint that is then improperly handled can produce two separate penalty events.

What this means for your compliance team: A sustained pattern of non-compliant calling — even at low volume — compounds penalty exposure rapidly. The third-violation tier of Rs 10 lakh per instance makes systematic non-compliance extremely expensive very quickly.

What Is the 15-Day Suspension and One-Year Blacklist?

The financial penalties are serious. However, the 15-day suspension and the one-year blacklist are materially more disruptive for any BFSI entity in active operations. These are operational consequences, not just financial ones, and they cannot be reversed by paying a fine.

The 15-Day Suspension: What Gets Blocked

On the first breach of the regulatory complaint threshold — which is 5 valid complaints in any rolling 10-day period — outgoing services on all telecom resources of the sender are barred for 15 days. This means not just the specific number from which the non-compliant call was made. It means every PRI, SIP trunk, and outbound number the entity holds with that TSP. OTPs cannot be delivered. Customer service calls cannot be made. Loan delinquency alerts stop. Transaction confirmations are blocked.

For any BFSI entity with an active lending book, a 15-day suspension during a monthly billing cycle or a quarter-end collections period is an operational emergency, not an administrative inconvenience. In my experience advising clients in the telecom space, entities consistently underestimate this risk until a suspension actually occurs.

The One-Year Blacklist: The Most Severe TRAI Power

Subsequent violations after the first suspension trigger a qualitatively different response. TRAI can order disconnection of all telecom resources of the entity for a period of up to one year. This disconnection applies across all Telecom Service Providers simultaneously — not just the TSP through which the violation occurred. The entity is also blacklisted, which means no new telecom number allocations for the blacklist period.

Furthermore, the blacklist entry creates secondary compliance exposure. Regulated entities must typically disclose material regulatory actions in periodic compliance certificates filed with their sectoral regulator. A TRAI blacklist therefore becomes visible to RBI, SEBI, IRDAI, or PFRDA in their routine supervisory oversight cycle. Additionally, cross-default clauses in lending arrangements may be triggered by disclosure of major regulatory action, amplifying the financial consequences well beyond the telecom penalty itself.

What this means for your compliance team: The one-year blacklist is the single most severe lever TRAI can use. A properly managed 160 series migration programme costs a fraction of what one blacklist cycle will cost in operational disruption, regulatory disclosure obligations, and reputational damage.

What Is UTM Classification and Why Is It Catastrophic?

UTM stands for Unregistered Telemarketer. Under TCCCPR, 2018, an entity that makes commercial communications without being properly registered — or that makes calls inconsistent with its registration — is treated as a UTM. After the phase-wise migration deadline, any service or transactional call from a 10-digit number qualifies a BFSI entity for UTM classification regardless of its registration status as a Principal Entity.

The UTM Enforcement Ladder

The UTM enforcement progression follows three steps. First, the entity receives a formal warning. Second, on the second violation, a usage cap is imposed — a maximum of 20 outgoing voice calls per day. Third, on the third and subsequent violations, all telecom resources of the entity are disconnected. This progression is separate from the complaint-threshold mechanism described earlier. Accordingly, a BFSI entity can face both tracks simultaneously: the complaint-based 15-day suspension and the UTM warning on the same set of non-compliant calls.

The 20-calls-per-day cap in the second UTM step is particularly damaging for entities with active collections operations. For context, a mid-sized NBFC may have collections teams placing thousands of calls daily. Restricting that to 20 calls per day effectively halts recovery operations entirely. Moreover, the cap applies across all the entity’s telecom resources, not just the offending line.

What this means for your compliance team: UTM classification is not a theoretical risk. It is the automatic legal status of any BFSI entity that continues using 10-digit numbers after its deadline. Treat migration as a hard operational deadline, not a regulatory preference.

Get Legal Guidance

See how FreJun walks BFSI entities through the exact steps of a 160 series migration — from TSP eligibility verification and DLT template registration through to routing segregation and CDR audit trails. Most entities complete the technical setup in under two weeks with FreJun’s platform.

Which Sectoral Regulator Penalties Apply Simultaneously?

The TRAI Direction was issued following Joint Committee of Regulators (JCoR) consultations involving RBI, SEBI, IRDAI, and PFRDA. That joint origin matters for penalty exposure. Non-compliance with the 160 series migration creates regulatory risk not just under telecom law but under each entity’s own sectoral statute. All four regulators can act independently on the same underlying conduct.

RBI and SEBI Penalty Frameworks

For RBI-regulated entities, supervisory action may be taken under Section 35A of the Banking Regulation Act, 1949, or Section 45L of the RBI Act, 1934. Monetary penalties fall under Section 46 or Section 47A of the Banking Regulation Act. Specifically, banks that continue to use non-compliant numbers for customer contact after the deadline face the dual risk of a TRAI enforcement action and an RBI supervisory inquiry triggered by the same consumer complaints.

For SEBI-regulated entities, the relevant provision is Section 15HB of the SEBI Act, 1992. Mutual funds, AMCs, and stockbrokers should note that SEBI’s own enforcement team monitors market participant conduct independently of TRAI. Additionally, SEBI-regulated entities that receive a TRAI notice or suspension must assess their disclosure obligations under relevant SEBI circulars on compliance reporting.

IRDAI and PFRDA Penalty Frameworks

IRDAI-regulated insurers face penalty exposure under Sections 102 to 105B of the Insurance Act, 1938. The IRDAI Direction of 16 December 2025 (PRID 2205350) incorporated insurers into the same migration framework, bringing their supervisory exposure into alignment with the banking sector. For PFRDA-regulated entities, the applicable provision is Section 28 of the PFRDA Act, 2013.

Critically, each sectoral regulator can act independently. A non-compliant call that generates five consumer complaints in ten days may simultaneously trigger TRAI’s blacklist mechanism, an RBI supervisory inquiry under the Fair Practices Code, and a SEBI investigation under market conduct norms — all from the same calling pattern. The layering is not theoretical; it reflects the JCoR architecture that produced the migration mandate in the first place.

What this means for your compliance team: Budget your compliance risk for 160 series non-compliance across all four regulatory tracks — TRAI, RBI or SEBI or IRDAI or PFRDA, DPDP, and potentially criminal law. The cost of a single sustained violation cycle across all four tracks dwarfs the cost of migration.

How Does the DPDP Act, 2023 Add to the Penalty Exposure?

The Digital Personal Data Protection Act, 2023 (DPDP Act) sits alongside the telecom framework as a separate but overlapping compliance obligation. Non-compliant calling patterns frequently involve DPDP violations because they often imply either a lack of lawful basis for processing customer contact data or a failure to honour opt-outs registered on the DLT platform.

DPDP Act Penalty Tiers

The Data Protection Board established under the DPDP Act can impose penalties of up to Rs 250 crore for failure to take reasonable security safeguards. Additionally, penalties of up to Rs 200 crore apply for failure to notify a personal data breach. For entities classified as Significant Data Fiduciaries, a further penalty of up to Rs 150 crore applies for breach of their additional obligations.

Specifically, a BFSI entity that makes service or transactional calls to customers who have registered an opt-out is simultaneously breaching the TCCCPR opt-out regime and potentially violating the DPDP Act requirement to honour the withdrawal of consent. Furthermore, calling without a lawful basis — for example, after the implicit consent period tied to the customer contract has lapsed — raises a DPDP processing-basis question on top of the TCCCPR violation. Therefore, the two frameworks must be read together in any compliance audit.

What this means for your compliance team: Map every consent record and opt-out event in your calling database against both the TCCCPR consent framework and the DPDP Act lawful-basis requirements. A single customer who opted out and was called again creates exposure under both statutes simultaneously.

Is There Criminal Liability for Number Misuse?

Criminal exposure exists in aggravated cases involving number masking, impersonation, or fraud. Three primary instruments are relevant here.

Telecommunications Act, 2023 and Bharatiya Nyaya Sanhita, 2023

Section 42 of the Telecommunications Act, 2023 criminalises tampering with telecommunication identifiers. The penalty is imprisonment of up to three years, a fine of up to Rs 50 lakh, or both. This provision captures number masking — which is the practice of overlaying a fake caller ID on a legitimate outbound call. After the 160 series mandate, any BFSI entity that routes service calls through a virtual number masking its allocated 1600-series identifier risks Section 42 exposure.

Sections 318 and 319 of the Bharatiya Nyaya Sanhita, 2023 cover cheating and cheating by personation. These provisions apply where a caller fraudulently misrepresents the identity of the calling entity. Moreover, Sections 66C and 66D of the Information Technology Act, 2000 cover identity theft and cheating by personation using a computer resource — relevant where the impersonation is facilitated by automated calling software.

What this means for your compliance team: Review your outbound calling infrastructure for any virtual number overlay or masking configuration. If your dialer routes calls through a number that differs from the entity’s allocated 1600-series identifier, the technical fix is urgent — the exposure is criminal, not merely regulatory.

What Calling Behaviours Are Most Likely to Trigger a Complaint?

Understanding which calling behaviours generate the most complaints helps compliance teams prioritise their remediation efforts. Based on the TCCCPR framework and the practical experience of advising entities that have faced TRAI scrutiny, seven patterns consistently generate consumer complaints.

Seven High-Risk Calling Patterns

• Calling opted-out subscribers: The most common trigger. Any call to a subscriber who has registered an opt-out on the DLT platform is a complaint-ready event.
• Calls outside 08:00 to 19:00 IST: The RBI Fair Practices Code restricts recovery and collection contact to this window. Calls outside it generate complaints that are both a TCCCPR violation and an RBI FPC violation.
• Calls on unregistered templates: Every voice script must be pre-registered on the DLT platform. A call made on an unregistered or blacklisted template is a violation regardless of the number used.
• Promotional content on a 1600-series number: Using a 1600-series number to deliver any marketing or cross-selling message is a direct violation of the allocation undertaking given to the TSP at registration.
• Calls from recovery agents on personal numbers: Recovery agents must use the Principal Entity’s allocated 1600-series numbers, not their own mobile phones. Personal-number calls for collection purposes after the deadline are UTM violations.
• Excessive call frequency: TRAI’s usage-cap regime can impose a maximum of 20 outgoing calls per day per number on entities found in violation. Unusually high call volumes attract scrutiny before any formal threshold is breached.
• Missing CNAP caller identity: DoT’s Calling Name Presentation (CNAP) regime requires accurate caller identity disclosure on the receiving handset. Calls that do not display the correct entity name generate complaints and regulatory attention.

Furthermore, under the revised complaint threshold introduced by the TCCCPR Second Amendment, 2025, consumers do not need to have registered a preference before filing a complaint. The prior requirement of prior DND registration has been removed. Consequently, any consumer who receives a non-compliant call can now lodge an immediate complaint through the DND app or the 1909 helpline.

What this means for your compliance team: Audit each of the seven patterns above in your current calling operations before your next compliance review. Address opted-out subscriber data hygiene first — it is the highest-frequency complaint trigger and the easiest to remediate with proper DLT integration.

How FreJun Helps BFSI Entities Avoid These Penalties

FreJun is India’s cloud telephony and AI-powered calling platform built for BFSI, SaaS, and enterprise teams that need to operate within the 160 series and 140 series regulatory framework. The platform handles the technical compliance layer so legal and compliance teams can focus on substantive obligations rather than infrastructure.

FreJun’s Compliance Stack for 1600-Series Migration

FreJun provisions 1600-series numbers directly for eligible BFSI entities, managing the TSP eligibility verification process that is mandatory before any 1600-series allocation. Additionally, FreJun’s fully DLT-integrated platform handles voice template registration, consent management, call routing, and CDR logging in one place. This integration addresses the most time-consuming compliance steps — template registration with access providers can take 2 to 3 weeks for first-time registrants, in my experience with telecom clients, and that lead time must be built into any migration timeline.

Moreover, FreJun enforces routing segregation at the system level — the same requirement that auditors look for when assessing whether 140-series promotional traffic and 1600-series transactional traffic are genuinely separated, not just stated to be separate in a policy document. The platform integrates with HubSpot, Zoho, Salesforce, and Leadsquared, enabling real-time opt-out data synchronisation that eliminates the most common complaint trigger for BFSI calling operations.

For further reading on the complete regulatory framework underlying the 160 series mandate, see FreJun’s BFSI Communication Compliance Guide 2026 and our detailed TCCCPR 2018 Compliance Guide. For a side-by-side analysis of both numbering series, see the 160 Series vs 140 Series comparison.

Talk to FreJun’s Legal Team

FreJun’s platform manages your 1600-series provisioning, DLT template registration, CDR logging, and routing segregation — end to end. Book a call with FreJun’s legal and compliance team to see exactly how the migration works for your entity type.

Frequently Asked Questions

What is the penalty for not migrating to the 160 series in India?

Under the TCCCPR Second Amendment of 12 February 2025, financial penalties scale from Rs 2,00,000 for a first violation, Rs 5,00,000 for a second, and Rs 10,00,000 per instance for third and subsequent violations. These sit alongside service suspension and potential blacklisting, which are operationally far more damaging than the fines themselves.

160 series vs 140 series: what is the difference?

The 140xxxxxxx series is restricted to promotional and telemarketing voice calls. The 1600xxxxxxx series is restricted exclusively to service and transactional calls by verified Principal Entities. The two series are not interchangeable. Using a 140 number for a service call or a 1600 number for a promotional call each constitutes an independent TCCCPR violation.

How does a BFSI entity apply for a 1600 series number?

A BFSI entity applies through a licensed Telecom Service Provider (TSP). The TSP must verify the entity’s eligibility — its regulatory status with RBI, SEBI, PFRDA, or IRDAI — before assigning a 1600-series number. The entity must also undertake to use the number only for service and transactional calls under TCCCPR, 2018. FreJun manages this provisioning process directly for eligible BFSI entities.

What is the blacklist trigger under TRAI’s complaint threshold?

Five valid consumer complaints within any rolling 10-day period trigger the complaint threshold. On breach, outgoing services on all telecom resources of the sender are barred for 15 days. Subsequent violations can lead to a one-year disconnection and blacklisting across all Telecom Service Providers in India. Consumers no longer need prior DND registration to file a complaint under the 2025 amendments.

Can RBI or SEBI penalise entities separately from TRAI for the same non-compliance?

Yes. The TRAI Direction was issued after Joint Committee of Regulators consultations involving RBI, SEBI, IRDAI, and PFRDA. Each regulator retains independent authority to act under its own statute. RBI may act under the Banking Regulation Act; SEBI under the SEBI Act; IRDAI under the Insurance Act; PFRDA under the PFRDA Act. These actions are additive — not alternative — to TRAI’s enforcement powers.

Does missing the 160 series deadline affect collections operations?

Significantly. A 15-day outgoing services suspension halts all collections calls, OTP delivery, and customer alerts for the suspension period. The UTM usage cap of 20 calls per day on the second violation is even more damaging for active collections teams. Additionally, the one-year blacklist makes recovery operations effectively impossible for its entire duration, creating substantial credit-risk and liquidity implications for lending entities.

Are recovery agents required to use the Principal Entity’s 1600-series numbers?

Yes. The 1600-series number is allocated to the Principal Entity, not its recovery agency or BPO. Recovery agents must make calls using the Principal Entity’s allocated numbers. The Principal Entity bears vicarious liability under TCCCPR and the RBI Fair Practices Code for its agents’ conduct. Additionally, individual recovery agents must hold a valid IIBF certification from the prescribed 100-hour training programme.

Key Takeaways

• All phase-wise migration deadlines are hard legal obligations. For commercial banks, the deadline was 1 January 2026. Large NBFCs faced 1 February 2026. Remaining NBFCs, co-operative banks, and RRBs faced 1 March 2026. Mutual Funds and AMCs faced 15 February 2026. QSBs faced 15 March 2026.
• Financial penalties under TCCCPR, 2018 range from Rs 2 lakh (first violation) to Rs 10 lakh per instance (third and subsequent violations), applied separately per violation instance and separately for complaint-handling failures.
• Five valid consumer complaints in any 10-day rolling window trigger mandatory outgoing service suspension for 15 days. Subsequent violations lead to a one-year blacklist across all TSPs — the single most operationally severe consequence available to TRAI.
• UTM classification after a missed deadline additionally subjects entities to a 20-calls-per-day usage cap and eventual disconnection on the UTM enforcement ladder, running parallel to the complaint-based suspension track.
• Sectoral regulators — RBI, SEBI, IRDAI, PFRDA — can act independently on the same non-compliant conduct under their own statutes, creating layered multi-regulator penalty exposure from a single calling pattern.
• The DPDP Act, 2023 adds a further penalty layer of up to Rs 250 crore for data-processing failures that overlap with non-compliant calling, particularly where opt-outs are not honoured.
• FreJun provisions 1600-series numbers, handles DLT template registration, enforces routing segregation, and manages CDR logging — providing the technical infrastructure for sustainable 160 series compliance.

Compliance Disclaimer

Disclaimer: This article is published for informational purposes only and represents FreJun’s understanding of the relevant legal and regulatory position based on its own independent research and interpretation of publicly available materials. It should not be construed as legal advice, legal opinion, or regulatory guidance. Readers are encouraged to seek independent legal counsel or consult the appropriate regulatory authorities before taking any action based on the information contained herein. While reasonable efforts have been made to ensure the accuracy and completeness of the information presented, laws, regulations, interpretations, and enforcement positions may evolve or vary based on specific facts and circumstances. FreJun does not warrant that the contents are free from inaccuracies, omissions, or inadvertent errors and shall not be responsible or liable for any misinformation, inaccuracies, or reliance placed upon the contents of this article, whether published knowingly or unknowingly.

References and Sources

• DoT Press Release, 30 May 2024 (PRID 2022249) — pib.gov.in
• TRAI Direction, 19 November 2025 (PRID 2191647) — pib.gov.in
• TRAI Direction (IRDAI), 16 December 2025 (PRID 2205350) — pib.gov.in
• TCCCPR Second Amendment, 12 February 2025 — trai.gov.in (PDF)
• TCCCPR 2018 — trai.gov.in
• RBI Master Direction on Outsourcing of IT Services, 10 April 2023 — rbi.org.in
• DPDP Act, 2023 — meity.gov.in
• SARAL SANCHAR Portal (TSP licence verification) — saralsanchar.gov.in

About the Author: Nimish Gavali is a Legal and Compliance Analyst and appointed Data Protection Officer (DPO) with prior experience practising before the Hon’ble Bombay High Court. Having transitioned into a corporate role, he advises on telecom regulation, digital compliance, data governance, and customer communication frameworks. His work spans TRAI regulations, DoT licensing, the TCCCPR 2018 and related amendments, DLT registration, and the 160 and 140 series numbering framework, with a focus on BFSI and communication platforms navigating compliant customer-outreach architectures. Prior to his in-house role, he worked on regulatory, civil, and commercial matters before the Bombay High Court. He holds an LL.B. from Government Law College, Mumbai, an LL.M. in Business and Corporate Law, and a Diploma in Cyber Laws. Connect on LinkedIn