TRAI 160 Series Mandate: What Every BFSI Entity Must Do Before Their Deadline

The TRAI 160 series mandate is no longer a recommendation. Since 19 November 2025, it is a time-bound legal obligation for every entity regulated by RBI, SEBI, PFRDA, and IRDAI. If your organisation makes service or transactional voice calls OTP delivery, EMI reminders, trade confirmations, insurance renewals and you have not yet migrated to a 1600-series number, you are already in breach of the TRAI Direction (PRID 2191647) or are approaching your deadline rapidly. The consequences are not theoretical: penalties start at ₹2,00,000 per violation, and a sustained pattern of non-compliance can result in a one-year blacklisting of all your telecom resources across every Telecom Service Provider (TSP) in India.

In my practice advising telecom-industry clients on TRAI and DoT compliance, I have seen BFSI entities consistently underestimate the lead time required for number allocation, DLT template registration, and CRM integration. Therefore, this article walks you through what the mandate actually requires, who it applies to, what your specific deadline is, and what the layered consequences of missing it look like with every claim anchored to the primary government source documents.

Key Facts at a Glance

Item	Detail
Governing regulation	TCCCPR, 2018 Second Amendment, 12 Feb 2025
Primary authority	TRAI / DoT (Ministry of Communications)
Series allocated	160xxxxxxx; sub-prefix 1601xxxxxxx for BFSI financial entities
Applies to	All entities regulated by RBI, SEBI, PFRDA (Nov 2025); IRDAI (Dec 2025)
Earliest deadline (passed)	15 Feb 2026 Mutual Funds & AMCs (SEBI)
Next deadline (passed)	15 Mar 2026 Qualified Stockbrokers / QSBs (SEBI)
First-violation penalty	₹2,00,000
Maximum blacklist duration	1 year across all TSPs all telecom resources
Voluntary adoption (Nov 2025)	485 entities, 2,800+ numbers (PRID 2191647)

What You Need to Know Right Now

• The TRAI 160 series mandate converts voluntary 1600-series adoption into a binding legal obligation for all RBI-, SEBI-, PFRDA-, and IRDAI-regulated entities making service or transactional voice calls.
• SEBI-regulated Mutual Funds and AMCs had a deadline of 15 February 2026; Qualified Stockbrokers (QSBs) had to comply by 15 March 2026 both deadlines have now passed.
• Continuing to use 10-digit mobile numbers for service calls after your deadline means those calls are classified as Unsolicited Commercial Communication from an Unregistered Telemarketer, attracting escalating penalties and potential disconnection.
• The 1601xxxxxxx sub-prefix is reserved exclusively for financial entities regulated by the four named regulators it is the consumer trust signal the entire framework depends on.
• Non-compliance can simultaneously trigger TCCCPR financial penalties, a one-year telecom blacklist, sectoral regulator enforcement, and DPDP Act, 2023 exposure these are cumulative, not alternative.

Table of Contents

1. Key Facts at a Glance
2. What Is the TRAI 160 Series Mandate?
3. Who Created the 160 Series and Why?
4. Who Must Comply with the 160 Series Mandate?
5. Phase-Wise Deadlines: What Is Your Specific Date?
6. 140 Series vs 160 Series: What Is the Difference?
7. What Types of Calls Must Use a 160-Series Number?
8. How Does a BFSI Entity Apply for a 1600-Series Number?
9. DLT Template Requirements Under the 160 Series Mandate
10. Consent Rules Every 160-Series User Must Follow
11. Penalties for Non-Compliance: What Is at Stake?
12. Recovery Agents and Outsourcing: Who Bears Liability?
13. How FreJun Helps You Meet the 160 Series Mandate
14. Frequently Asked Questions
15. Key Takeaways
16. Compliance Disclaimer
17. References & Sources

What Is the TRAI 160 Series Mandate?

The TRAI 160 series mandate converts what was previously a voluntary adoption system into a compulsory legal obligation. Before this Direction, the 160xxxxxxx series had been available since May 2024 (DoT Press Release, PRID 2022249, 30 May 2024), and approximately 485 entities had adopted it voluntarily, subscribing to over 2,800 numbers. However, a substantial number of BFSI entities particularly smaller NBFCs, stockbrokers, and insurance intermediaries had not made the switch. Consequently, TRAI concluded, after Joint Committee of Regulators (JCoR) consultations, that voluntary adoption was insufficient and that phase-wise legal deadlines were necessary.

The mandate has two immediate practical consequences. First, it prohibits regulated entities from continuing to make service or transactional voice calls from standard 10-digit mobile numbers after their applicable deadline. Second, it requires them to obtain a 1600-series number from a TSP, register all voice script templates on the Distributed Ledger Technology (DLT) platform, and route all covered calls through that number. Notably, it does not permit a hybrid transition period during which both old and new formats are used simultaneously the switch must be clean and documented.

Who Created the 160 Series and Why?

The Department of Telecommunications (DoT) created the 160xxxxxxx numbering series through a press release dated 30 May 2024 (PRID 2022249), specifically to give consumers a reliable visual cue to distinguish legitimate service calls from fraud. Before the 160 series existed, genuine banks, NBFCs, insurers, and stockbrokers were making OTP, EMI reminder, and trade confirmation calls from standard 10-digit mobile numbers exactly the same format that fraudsters used to impersonate these institutions.

The 140xxxxxxx series had been allocated for telemarketing and promotional calls, but promotional traffic overwhelmed it over time. As a result, consumers stopped answering 140-series calls, and genuine entities began routing service and transactional calls through unregistered 10-digit numbers to improve pick-up rates. This created the fraud window: a consumer receiving a call from a 10-digit mobile number claiming to be their bank had no reliable way to verify the claim. Industry reports indicate that India recorded approximately 147 million spam-call complaints in 2024, reflecting the scale of the problem the 160 series is designed to address.

The DoT’s solution was structural. The 160-series is allocated exclusively for service and transactional calls, and the 1601xxxxxxx sub-prefix is reserved for financial entities regulated by RBI, SEBI, PFRDA, and IRDAI. Over time, as 1601 numbers become associated with legitimate financial institutions in the consumer’s mind, the risk of impersonation via a 10-digit mobile number should decline materially. Furthermore, TSPs are required to verify the eligibility of every entity before assigning a 160-series number the allocation is not self-service. The success of this regime depends entirely on complete adoption, which is why TRAI converted voluntary registration into a mandate in November and December 2025.

Who Must Comply with the 160 Series Mandate?

Every entity that is regulated by RBI, SEBI, PFRDA, or IRDAI and makes service or transactional voice calls to customers must comply with the TRAI 160 series mandate. The two TRAI Directions of November and December 2025 jointly cover the entire BFSI regulatory landscape in India. Additionally, recovery agencies and BPOs calling on behalf of a regulated entity are also within scope a point many entities overlook in their initial compliance assessment.

RBI-Regulated Entities

This category includes scheduled commercial banks, regional rural banks, cooperative banks, non-banking financial companies (NBFCs), housing finance companies (HFCs), payment banks, small finance banks, and microfinance institutions. If your entity holds a valid licence or certificate of registration from the Reserve Bank of India and you make outbound service or transactional calls account alerts, OTPs, EMI reminders, loan disbursal confirmations, or collection follow-ups the mandate applies to you. In practice, this means every bank and NBFC with any form of customer communication via voice must complete the migration. Verify your specific phase-wise deadline directly with your TSP, referencing the operative TRAI Direction text.

SEBI-Regulated Entities

Mutual funds, Asset Management Companies (AMCs), stockbrokers, portfolio managers, investment advisers, and Qualified Stockbrokers (QSBs) all fall within the SEBI-regulated bracket. Moreover, SEBI entities face the earliest confirmed deadlines under the mandate: AMCs and Mutual Funds had to complete migration by 15 February 2026, and QSBs had to do so by 15 March 2026. Both deadlines have passed. Consequently, any SEBI entity still using 10-digit mobile numbers for service or transactional calls is currently in default.

PFRDA-Regulated Entities

Pension Fund Managers and National Pension System (NPS) intermediaries regulated by the Pension Fund Regulatory and Development Authority (PFRDA) are included in the November 2025 Direction. Their outbound calls related to pension account management, contribution confirmations, and subscriber alerts must originate from 1600-series numbers within the applicable phase. Specifically, the operative TRAI Direction text should be consulted for PFRDA-specific phase deadlines, as secondary commentary on asset-size thresholds has varied.

IRDAI-Regulated Entities

Life insurers, general insurers, health insurers, insurance brokers, and corporate agents regulated by the Insurance Regulatory and Development Authority of India (IRDAI) were brought into the framework by the Direction dated 16 December 2025 (PRID 2205350). As a result, insurance renewal reminders, premium due notices, claim status updates, and policy confirmation calls must all migrate to the 1601-series. IRDAI entities should verify their specific phase deadlines in the December 2025 Direction text.

BPOs, Recovery Agencies, and Outsourced Telecallers

A BPO or recovery agency making calls on behalf of a regulated BFSI entity is not itself the Principal Entity (PE) for the purposes of 160-series allocation. However, it must use the PE’s allocated 1600-series numbers when making those calls not its own number pool. The Principal Entity remains vicariously liable for the calling conduct of its agents under the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) and the RBI Fair Practices Code. Therefore, your compliance programme must extend to every vendor who dials on your behalf, with appropriate contractual controls.

Phase-Wise Deadlines: What Is Your Specific Date?

The TRAI Direction of 19 November 2025 (PRID 2191647) established phase-wise deadlines based on entity type and supervising regulator. The confirmed deadlines drawn directly from the Direction are set out below.

Entity Type	Regulator	Deadline	Status (May 2026)
Mutual Funds & AMCs	SEBI	15 February 2026	Passed migration mandatory
Qualified Stockbrokers (QSBs)	SEBI	15 March 2026	Passed migration mandatory
RBI-regulated entities	RBI	Phase-wise per TRAI Direction	Verify operative text with your TSP
PFRDA-regulated entities	PFRDA	Phase-wise per TRAI Direction	Verify operative text with your TSP
IRDAI-regulated entities	IRDAI	Phase-wise per Dec 2025 Direction (PRID 2205350)	Verify operative text with your TSP

Important note on NBFC asset-size thresholds and further RBI phases: Secondary commentary has varied on the precise asset-size cut-offs used to tier RBI-regulated entities across phases. I strongly recommend that every NBFC, HFC, and other non-bank RBI-regulated entity read the operative TRAI Direction text directly and confirm their specific deadline with their TSP, rather than relying on secondary summaries including this one. The Direction documents are publicly available at the PIB URLs cited in the References section of this article.

What is certain is that both the February and March 2026 SEBI deadlines have already passed. Furthermore, any Mutual Fund, AMC, or QSB still using 10-digit mobile numbers for service calls is currently in violation. The broader mandate for RBI entities is active, and the longer a BFSI entity delays migration, the greater the risk of enforcement action from TRAI, the sectoral regulator, or both simultaneously.

Multiple SEBI deadlines have already passed. If your entity has not yet migrated to a 1600-series number, the window to avoid enforcement action is narrow. FreJun’s team can assess your specific compliance position and help you understand the fastest path to 1600-series operation.

Talk to FreJun’s Legal Team

140 Series vs 160 Series: What Is the Difference?

The 140-series and 160-series serve fundamentally different legal purposes under Indian telecom regulation, and the two are not interchangeable in either direction. Understanding the distinction is essential because using the wrong series for a given call type is itself a TCCCPR violation, independent of whether your entity has a valid number allocation.

Feature	140 Series (140xxxxxxx)	160 Series (160xxxxxxx / 1601xxxxxxx)
Permitted use	Promotional and telemarketing voice calls only	Service and transactional voice calls only
Typical content	Product offers, campaign calls, sales pitches	OTPs, EMI reminders, account alerts, trade confirmations
Who can use	Any registered telemarketer or business	Verified Principal Entities only (BFSI under TRAI mandate)
Consumer response pattern	Low associated with spam since 2018	High trust signal reserved for verified institutions
BFSI sub-prefix	Not applicable	1601xxxxxxx exclusively for RBI/SEBI/PFRDA/IRDAI entities
DLT template required	Yes	Yes
Cross-use permitted	No cannot carry service calls	No cannot carry promotional calls

Additionally, the routing segregation between the two series must be technical, not merely a policy statement. The same dialer instance cannot handle both 140 promotional traffic and 1600/1601 transactional traffic through the same outbound number pool. Regulators and auditors have been explicit that a written policy without enforced routing logic does not constitute adequate compliance. Marketing campaigns and OTP delivery must therefore operate on entirely separate outbound trunks with no shared number resources.

What Types of Calls Must Use a 160-Series Number?

Under the TCCCPR Second Amendment dated 12 February 2025, two categories of calls must originate from a 160-series number once your entity has migrated: service calls and transactional calls. The definitional boundary between these categories has practical compliance significance, particularly for BFSI entities managing collections and time-sensitive customer outreach.

Service Calls

A service call is one made with consent or through a registered template to facilitate, complete, or confirm a transaction the customer has consented to, or to provide warranty, recall, safety, or security information related to a product or service the customer has used or purchased. In practice, service calls include account maintenance notifications, fraud alert calls, card activation prompts, loan statement delivery calls, and EMI reminder calls made outside the 30-minute transactional window (see below). Specifically, any call that is not triggered by a customer-initiated event within the preceding 30 minutes defaults to the service-call category and requires the corresponding consent stack.

Transactional Calls

A transactional call is a non-promotional call made by a BFSI entity to its own customers where the information is essential to the customer OTPs, account alerts, and transaction confirmations are the clearest examples. Under the 2025 amendments, transactional content is strictly limited to messages triggered within 30 minutes of a customer-initiated event. Consequently, an OTP call made immediately after a login attempt is transactional; however, an EMI reminder call made three days before a due date is a service call, not a transactional call, because it is not triggered by a customer-initiated event within the 30-minute window.

What Is NOT Permitted on a 160-Series Number

Promotional calls, sales pitches, and any call offering a new product or service the customer has not previously purchased cannot originate from a 1600/1601 number. Sending even a single promotional call from a 1600/1601 number breaches the allocation undertaking given to the TSP at the time of number assignment and independently triggers TCCCPR penalty provisions. Moreover, the allocation undertaking is a contractual obligation the entity promises at the time of number assignment to use it only for service and transactional purposes as defined by TCCCPR, 2018. Breach of this undertaking compounds the regulatory exposure across multiple instruments simultaneously.

How Does a BFSI Entity Apply for a 1600-Series Number?

Obtaining a 1600-series number involves a structured application process through a licensed TSP. The TSP is responsible under the DoT’s allocation framework for verifying the eligibility of every entity before assigning a number this verification step cannot be bypassed. Below are the six key steps every BFSI entity must complete.

1. Confirm your regulatory status: Gather your current licence or certificate of registration from RBI, SEBI, PFRDA, or IRDAI. The TSP will require evidence of your regulated-entity status as part of eligibility verification.
2. Identify a licensed TSP: Contact a TSP holding a valid Unified Licence (UL) or UL-VNO authorisation. Verify provider licence status through the SARAL SANCHAR portal at saralsanchar.gov.in. FreJun works with licensed TSPs to provision 1600-series numbers on behalf of BFSI clients.
3. Submit your application and undertaking: The entity must formally undertake to use the allocated number only for service and transactional calls as per TCCCPR, 2018. This is a legal commitment breach of this undertaking compounds the regulatory exposure.
4. Register on the DLT platform: All call templates every IVR opener, agent introduction script, EMI reminder, OTP delivery message must be pre-registered on the DLT platform operated by the access provider. Template registration commonly takes 2–3 weeks for first-time registrants. Start this process in parallel with number allocation, not after it.
5. Configure routing segregation: Ensure your telephony infrastructure routes all 1600-series transactional traffic through a separate outbound trunk. Marketing and promotional traffic must remain on a separate 140-series number pool with no shared resources.
6. Test and audit before going live: Conduct a call audit to confirm that every outbound service and transactional call type originates from the 1600-series number, all Template IDs are passed correctly in call signalling, and no promotional traffic is crossing into the 1600-series trunk.

For broader guidance on the BFSI calling compliance architecture, see our BFSI Communication Compliance Guide 2026 and our detailed breakdown of 160 series vs 140 series obligations.

DLT Template Requirements Under the 160 Series Mandate

Every voice script used in a 1600-series call must be pre-registered as a content template on the Distributed Ledger Technology (DLT) platform. This requirement exists independently of the 160-series number allocation a valid 1600-series number does not make an unregistered call script compliant with TCCCPR.

The following voice scripts must be individually registered as DLT templates by a BFSI entity using 1600-series numbers:

• IVR opening messages and menu navigation scripts
• Agent introduction scripts (name, entity name, and purpose of call)
• OTP delivery scripts
• EMI reminder and payment due date notifications
• Loan disbursal and account credit confirmation scripts
• Trade execution and portfolio update notifications (SEBI entities)
• Insurance renewal and premium due reminder scripts (IRDAI entities)
• Fraud alert and account security notification scripts
• Collection follow-up scripts (subject also to RBI calling hour restrictions)

Calling with an unregistered template, an outdated template, or a blacklisted template is a TCCCPR violation regardless of whether the originating number is a valid 1600/1601 allocation. Therefore, entities should build a template review cycle into their compliance calendar templates must be updated whenever the underlying script changes and re-registered before deployment. Additionally, the Template ID must be mapped to each corresponding Call Detail Record (CDR) for audit purposes.

Consent Rules Every 160-Series User Must Follow

The TCCCPR Second Amendment dated 12 February 2025 substantially tightened consent requirements for BFSI entities using 1600-series numbers. These rules also intersect with Section 7 of the Digital Personal Data Protection Act, 2023 (DPDP Act, 2023), which requires all personal data processing to rest on either consent or a specified legitimate use and documentation of that lawful basis must be available on demand.

Consent Type	Rule
Implicit consent (existing customer)	Valid only for the duration of the underlying contractual relationship
Explicit consent (no ongoing contract)	Valid for only 7 days from grant for the specific stated purpose
Post opt-out lockout	Entity cannot contact the subscriber on the same purpose for 90 days after opt-out
Auto-dialer / robo-call disclosure	Must be disclosed at the start of every call non-disclosure is an independent violation
Consent capture mechanism	Must align with the Digital Consent Acquisition (DCA) framework on the DLT platform
Transactional call window	Transactional calls must be made within 30 minutes of the customer-initiated event

For collections teams specifically, the RBI Fair Practices Code and the RBI Responsible Lending Conduct directions further restrict outbound contact to the window of 08:00 to 19:00 IST. Customer-initiated contact outside that window is permissible but outbound contact initiated by the BFSI entity is not. In practice, this means collection teams need dialer systems that automatically enforce the calling hours window and maintain an auditable log of every call attempt, outcome, and timestamp. Furthermore, consent records must be retained in a form that can be produced to the Data Protection Board under the DPDP Act, 2023 if processing is later challenged.

Penalties for Non-Compliance: What Is at Stake?

Non-compliance with the TRAI 160 series mandate does not attract a single penalty it triggers a multi-layered regulatory response from at least three authorities simultaneously. Understanding the full penalty architecture is essential for any BFSI entity still weighing the cost of delayed migration against the cost of compliance.

Layer 1: TCCCPR Financial Disincentives

Under the TCCCPR Second Amendment, 2025, graded financial disincentives apply per instance of violation. The first instance carries ₹2,00,000; the second carries ₹5,00,000; and the third and subsequent instances each carry ₹10,00,000. Importantly, these are levied in addition to any penalty for invalid complaint closure or non-fulfilment of other TCCCPR obligations they are not a ceiling on total exposure, they are a per-instance floor.

Layer 2: Service Suspension and Blacklisting

Materially more disruptive than the financial disincentive is the service suspension power. The blacklist trigger threshold has been tightened to 5 valid complaints in any rolling 10-day period. First violation results in outgoing services on all telecom resources being barred for 15 days. Subsequent violations result in disconnection of all telecom resources PRI lines, SIP trunks, all numbers across all TSPs for up to one year. For a BFSI entity, a one-year blacklist is operationally catastrophic: OTPs cannot be delivered, customer service calls cannot be made, and collections activity stops entirely. The financial cost of that operational failure far exceeds the cost of any compliance programme.

Layer 3: Unregistered Telemarketer Classification

A BFSI entity that continues using 10-digit mobile numbers for service calls after its applicable deadline will have those calls classified as Unsolicited Commercial Communication from an Unregistered Telemarketer (UTM). The UTM enforcement progression starts with a warning, escalates to a six-month usage cap limiting the entity to a maximum of 20 outgoing calls per day, and ultimately results in full disconnection of all telecom resources. Additionally, the 20-calls-per-day cap is crippling for any entity making high volumes of OTP or transaction confirmation calls throughout the business day.

Layer 4: Sectoral Regulator Action

The TRAI Directions were issued after JCoR consultations involving RBI, SEBI, IRDAI, and PFRDA, meaning non-compliance with the telecom mandate can independently trigger action from the entity’s sectoral regulator. RBI can act under Section 35A of the Banking Regulation Act, 1949; SEBI under Section 15HB of the SEBI Act, 1992; IRDAI under Sections 102 to 105B of the Insurance Act, 1938; and PFRDA under Section 28 of the PFRDA Act, 2013. Crucially, these penalties are applied independently of TRAI’s enforcement for the same underlying conduct they are not alternatives, they stack.

Layer 5: DPDP Act Exposure

If the non-compliant calling pattern involves a breach of personal data obligations calling without lawful basis, failing to honour opt-outs, or using customer data for purposes beyond the original consent the DPDP Act, 2023 empowers the Data Protection Board to impose penalties of up to ₹250 crore for failure to take reasonable security safeguards, ₹200 crore for failure to notify a personal data breach, and ₹150 crore for breach of obligations applicable to Significant Data Fiduciaries. Additionally, these penalty bands apply to each qualifying breach independently.

Recovery Agents and Outsourcing: Who Bears Liability?

The 1600/1601 number is allocated to the Principal Entity the bank, NBFC, insurer, or other regulated body not to the recovery agency or BPO it engages. The legal position on outsourcing liability under the TRAI 160 series mandate is settled and should not be underestimated by compliance teams.

A recovery agency or BPO making calls on behalf of a BFSI entity must use the Principal Entity’s allocated 1600/1601 numbers. It cannot use its own number pool for those calls. The Principal Entity bears vicarious liability for the conduct of its agents under the TCCCPR, under the RBI Fair Practices Code, and under the RBI Master Direction on Outsourcing of Information Technology Services dated 10 April 2023. Furthermore, individual recovery agents must hold a valid IIBF certification obtained after the prescribed 100-hour training programme, and the Principal Entity must maintain a board-approved Code of Conduct for all recovery agents.

In practice, this means BFSI entities need to audit their entire outsourced calling chain, not just their own internal dialer setup. Every vendor contract should include an explicit compliance clause requiring the use of the Principal Entity’s 1600-series numbers, adherence to TCCCPR calling rules, maintenance of call records that can be produced on regulatory demand, and a right of audit by the Principal Entity. Absent these contractual controls, the Principal Entity has limited recourse when an agent’s non-compliant call triggers a TRAI complaint cycle.

How FreJun Helps You Meet the 160 Series Mandate

FreJun is a cloud telephony and AI-powered calling platform built specifically for BFSI entities navigating India’s voice-channel compliance requirements. The platform handles the technical compliance layer so your legal and operations teams can focus on the substantive obligations rather than the infrastructure plumbing.

FreJun’s 160-series compliance support covers number provisioning through licensed TSPs, DLT template registration and management, call routing segregation enforced at the system level (1600-series transactional traffic separated from 140-series promotional traffic), CDR logging with full audit trail, and CRM integration with HubSpot, Zoho, Salesforce, and Leadsquared. Moreover, the platform enforces calling hours rules at the dialer level collection calls are automatically restricted to the 08:00–19:00 IST window mandated by the RBI Fair Practices Code, with time-stamped logs available for regulatory inspection.

For entities that have already missed the February or March 2026 SEBI deadlines, FreJun’s team can assist in expediting the provisioning and DLT registration process to minimise the period of ongoing non-compliance. Additionally, read more about BFSI-specific compliance architecture in our TCCCPR 2018 compliance guide and our comprehensive BFSI Communication Compliance Guide 2026.

FreJun manages number provisioning, DLT template registration, CDR logging, and CRM integration the full technical compliance stack for the TRAI 160 series mandate. Book a call to see how it works for your specific entity type and calling volumes. Most entities are operational within days, not months.

Book a Call

Frequently Asked Questions

What is the TRAI 160 series mandate and which entities does it apply to?

The TRAI 160 series mandate is a binding regulatory direction requiring all BFSI entities regulated by RBI, SEBI, PFRDA, and IRDAI to migrate their service and transactional voice calls to 1600-series numbers by phase-wise deadlines. It applies to banks, NBFCs, mutual funds, stockbrokers, insurers, pension fund managers, and every intermediary making outbound service or transactional calls to customers in India under the TCCCPR, 2018 framework.

160 series vs 140 series what is the difference for BFSI entities?

The 140-series is allocated exclusively for promotional and telemarketing calls. The 160-series is allocated exclusively for service and transactional calls by verified Principal Entities. The two series are not interchangeable in either direction. Using a 140-series number for a service call, or a 160-series number for a promotional call, is an independent TCCCPR violation regardless of whether the entity holds valid allocations in both series.

What is the penalty for failing to comply with the TRAI 160 series mandate?

Penalties are multi-layered and cumulative. Under TCCCPR, the financial disincentive is ₹2,00,000 for the first violation, ₹5,00,000 for the second, and ₹10,00,000 per instance thereafter. TRAI can additionally blacklist all telecom resources for up to one year across all TSPs. The entity’s sectoral regulator RBI, SEBI, IRDAI, or PFRDA may independently impose penalties under the relevant statute for the same conduct.

How does a BFSI entity apply for a 1600-series number under the TRAI mandate?

The entity must apply through a TSP holding a valid Unified Licence (UL) or UL-VNO authorisation, provide evidence of its regulated status (RBI, SEBI, PFRDA, or IRDAI licence), and formally undertake to use the number only for service and transactional calls under TCCCPR 2018. The TSP verifies eligibility before allocation. DLT template registration, which commonly takes 2–3 weeks for first-time registrants, must be completed before the number is used operationally.

What is the phase-wise deadline for SEBI-regulated entities under the TRAI 160 series mandate?

SEBI-regulated Mutual Funds and AMCs had to complete migration by 15 February 2026. Qualified Stockbrokers (QSBs) had a deadline of 15 March 2026. Both deadlines have now passed. Any SEBI-regulated entity still using 10-digit mobile numbers for service or transactional calls is currently in violation of the TRAI Direction dated 19 November 2025 (PRID 2191647) and should seek to remediate its position without further delay.

What are the calling hour restrictions for BFSI entities making 1600-series calls?

While TCCCPR does not prescribe specific calling hours for service calls, the RBI Fair Practices Code restricts collection and recovery outbound contact to 08:00–19:00 IST. Calls outside this window initiated by the BFSI entity are prohibited. Customer-initiated contact outside those hours remains permissible. These restrictions apply independently of whether the call originates from a 1600-series number or a standard number.

Does the TRAI 160 series mandate apply to recovery agencies calling on behalf of a bank?

Yes. Recovery agencies and BPOs making calls on behalf of a BFSI Principal Entity must use the Principal Entity’s allocated 1600-series numbers not their own number pool. The Principal Entity bears vicarious liability for all calling conduct of its agents under TCCCPR and the RBI Fair Practices Code. Every outsourced vendor contract should include an explicit 160-series compliance clause with audit rights for the Principal Entity.

What is the 1601 sub-prefix and why does it matter under the TRAI 160 series mandate?

The 1601xxxxxxx sub-prefix is reserved exclusively for financial entities regulated by RBI, SEBI, PFRDA, and IRDAI. As complete migration is achieved, consumers can treat a 1601 number as a reliable signal that the call originates from a verified, regulated financial institution. Conversely, a call purporting to be from a bank that arrives from a standard 10-digit mobile number should be treated with suspicion regulated BFSI entities are now legally required to use 1601 numbers for such calls.

Key Takeaways

• The TRAI 160 series mandate converts voluntary 1600-series adoption into a binding legal obligation for all RBI-, SEBI-, PFRDA-, and IRDAI-regulated entities making service or transactional voice calls in India.
• SEBI deadlines (15 February 2026 for Mutual Funds and AMCs; 15 March 2026 for QSBs) have already passed non-migrated SEBI entities are currently in default and face active enforcement risk.
• The 1601xxxxxxx sub-prefix is reserved exclusively for financial entities regulated by the four named regulators it is the consumer trust signal the entire regulatory framework depends on delivering.
• DLT template registration is a parallel and independent obligation to number allocation both must be completed before 1600-series calls begin, and templates must be updated whenever scripts change.
• Non-compliance can simultaneously attract TCCCPR financial penalties, a one-year telecom blacklist, sectoral regulator enforcement under RBI, SEBI, IRDAI, or PFRDA statutes, and DPDP Act penalties these are cumulative, not alternative consequences.
• Recovery agencies and BPOs calling on behalf of a BFSI entity must use the Principal Entity’s 1600-series numbers; the Principal Entity is vicariously liable for agent conduct under TCCCPR and the RBI Fair Practices Code.
• Technical routing segregation between 140-series promotional traffic and 1600-series transactional traffic must be enforced at the system level a written policy without enforced routing logic is not adequate compliance.

You have now seen the full scope of the TRAI 160 series mandate the deadlines, the penalty layers, the DLT requirements, and the outsourcing liability rules. If you still have questions about how the compliance architecture applies to your specific entity type or calling volumes, reach out before your next audit cycle.

For Any Questions Reach Out to Our Legal Team

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 & Sources

• DoT Press Release, 30 May 2024 (PRID 2022249) — pib.gov.in
• TRAI Direction, 19 Nov 2025 — Phase-wise 1600 series mandate for RBI, SEBI & PFRDA entities (PRID 2191647) — pib.gov.in
• TRAI Direction, 16 Dec 2025 — IRDAI inclusion (PRID 2205350) — pib.gov.in
• TCCCPR Second Amendment, 12 Feb 2025 (Gazette PDF) — trai.gov.in (PDF)
• TCCCPR 2018 — trai.gov.in
• RBI Master Direction on Outsourcing of IT Services, 10 Apr 2023 — rbi.org.in
• DPDP Act, 2023 — MeitY Reference — meity.gov.in
• SARAL SANCHAR Portal — TSP Licence Verification — saralsanchar.gov.in