FreJun 160 Series 140 Series BFSI Setup: No Compliance Headaches

Last updated on October 8th, 2026 at 08:10 pm

Key Facts at a Glance

• TRAI mandated 1600-series adoption for all BFSI entities in India, with deadlines from January to March 2026.
• The 140-series is restricted to promotional calls only; using it for service or transactional calls is a TCCCPR violation carrying penalties up to Rs 10,00,000 per instance.
• DLT platform registration is mandatory before any 1600-series number is activated; every voice template must carry a valid Template ID in call signalling.
• FreJun provisions 1600-series numbers, manages DLT template registration, enforces routing segregation, and integrates directly with HubSpot, Zoho, Salesforce, and LeadSquared.
• A one-year telecom blacklist across all TSPs is the single most operationally severe consequence of non-compliance; a compliant setup costs far less than one violation cycle.

Table of Contents

1. What Is the 160 Series and Why Does It Matter for BFSI?
2. 140 Series vs 160 Series: What Is the Difference?
3. Who Must Comply with the 1600-Series Mandate?
4. What Are the Phase-wise Deadlines for 1600-Series Adoption?
5. How Does a BFSI Entity Get a 1600-Series Number?
6. What Is DLT Registration and Why Is It Non-Negotiable?
7. Why Must 140 and 1600 Series Traffic Be Kept Separate?
8. What Operational Rules Apply When Using 1600-Series Numbers?
9. What Are the Penalties for Non-Compliance?
10. How FreJun Helps BFSI Companies Set Up 160 and 140 Series Calls
11. Frequently Asked Questions
12. Key Takeaways

What Is the 160 Series and Why Does It Matter for BFSI?

The 160 series BFSI setup requirement exists because the 140xxxxxxx series became saturated with promotional traffic. Consumers stopped answering 140-prefix calls. Genuine banks, insurers, and NBFCs then began using standard 10-digit mobile numbers for OTPs, EMI reminders, and policy alerts. That pattern created a fraud window: scammers mimicked those same 10-digit numbers to impersonate regulated institutions.

The DoT’s solution was architectural. By creating a separate prefix that only verified entities can access, the 160 series gives consumers a reliable visual cue. Specifically, calls from 1601xxxxxxx come from financial entities regulated by RBI, SEBI, PFRDA, or IRDAI. A customer seeing that prefix can answer with confidence. A customer seeing a regular 10-digit number claiming to be from their bank has every reason to be suspicious.

Why the 160 Series Creates a Compliance Obligation, Not Just an Option

TRAI converted voluntary adoption into a time-bound mandate on 19 November 2025 (PRID 2191647). The Direction applies to entities regulated by RBI, SEBI, and PFRDA. A parallel Direction dated 16 December 2025 (PRID 2205350) brought IRDAI-regulated insurers within the same framework. After the applicable phase deadline, TRAI classifies any service or transactional call made from a 10-digit number as Unsolicited Commercial Communication from an Unregistered Telemarketer (UTM). The enforcement progression for UTMs begins with a warning but escalates quickly to disconnection of all telecom resources.

In my practice advising telecom-sector clients, the question I encounter most often is not whether to comply but how to migrate without disrupting OTP delivery, collection workflows, and customer-service IVRs simultaneously. That operational challenge is exactly what FreJun was built to solve.

FreJun provisions your 1600-series numbers, completes DLT registration, and connects everything to your CRM before your compliance deadline. Most BFSI clients are fully live within 5 to 7 business days. No credit card needed to start the conversation.

140 Series vs 160 Series: What Is the Difference?

The 140 series and the 160 series are not interchangeable. TRAI and DoT have drawn a hard legal boundary between the two. Using the wrong series for the wrong call type is itself a TCCCPR violation, regardless of whether the content of the call is appropriate.

Does a BFSI Entity Still Need a 140-Series Number?

Yes, absolutely. If the entity runs any promotional outbound campaigns, it still needs 140-series numbers. The 1600-series mandate covers service and transactional calls only. Promotional calls, including cross-sell campaigns, product announcements, and lead-generation outreach, must still use registered 140-series numbers. The two series must operate through technically segregated routing; a single dialer instance cannot route both streams through the same number pool.

Furthermore, the entity must enforce routing segregation at the system level, not just as a written policy. Regulators and auditors have consistently held that a policy document without enforced routing logic does not count as real compliance. What this means for your technical team is that your team must set up separate outbound trunk configurations for 140 traffic and 1600 traffic.

Who Must Comply with the 1600-Series Mandate?

The 160 series BFSI setup mandate covers all entities regulated by the four BFSI-sector regulators. Additionally, outsourced vendors, recovery agencies, and BPOs that make calls on behalf of a regulated Principal Entity must also use the Principal Entity’s allocated 1600-series numbers, not their own number pool.

RBI-Regulated Entities

• Scheduled commercial banks (public, private, and foreign)
• Large NBFCs, payments banks, and small finance banks
• Remaining NBFCs, cooperative banks, and regional rural banks

SEBI, PFRDA, and IRDAI-Regulated Entities

• Mutual funds and Asset Management Companies (AMCs)
• Qualified Stockbrokers (QSBs)
• Central recordkeeping agencies and pension fund managers
• All entities regulated by IRDAI, including life and general insurers

What About Recovery Agents and BPOs?

TRAI allocates the 1600-series number to the Principal Entity, which is the bank, NBFC, insurer, or other regulated entity. A recovery agency or BPO acting on behalf of the Principal Entity must make calls using the Principal Entity’s allocated 1600-series numbers. The Principal Entity carries legal responsibility for its agents under TCCCPR, under the RBI Fair Practices Code, and under the RBI Master Direction on Outsourcing of IT Services dated 10 April 2023.

In practice, this means the Principal Entity must ensure its telephony platform routes agent calls through its own 1600-series allocation. FreJun’s multi-user routing architecture handles this by assigning agent sessions under the Principal Entity’s number header, so the platform presents the correct caller identity on every outbound call regardless of which agent or BPO team is dialling.

What Are the Phase-wise Deadlines for 1600-Series Adoption?

Specifically, TRAI set these phase-wise deadlines after consultations through the Joint Committee of Regulators (JCoR). Each phase corresponds to a specific sub-sector or entity type. The verified deadlines from the TRAI Direction (PRID 2191647, 19 November 2025) and the follow-up Direction (PRID 2205350, 16 December 2025) are as follows.

Notably, 485 entities had already adopted the 1600 series voluntarily as of November 2025, subscribing to over 2,800 numbers (TRAI Direction, PRID 2191647). The mandate now applies to the remaining entities that had not yet migrated. For entities whose deadlines have passed, the clock for TCCCPR enforcement is already running.

What Happens If Your Entity Missed Its Deadline?

Importantly, missing the deadline does not create a grace period. From the morning after the applicable deadline, TRAI treats any service or transactional call made from a 10-digit mobile number as a UTM call. The enforcement progression begins with a warning, then a usage cap of 20 outgoing calls or messages per day, and then disconnection of all telecom resources. The practical step for any entity that has missed its deadline is to begin migration immediately and document the good-faith effort in case of a regulatory inquiry.

How Does a BFSI Entity Complete the 160 Series BFSI Setup and Get a Number?

Completing a 160 series BFSI setup involves four sequential steps. Each step must finish before the next one begins. Shortcuts at any stage result in the number not being activated or the call traffic being rejected at the telecom layer.

Step 1: Confirm Regulatory Eligibility

The entity must hold a valid, current registration or licence with its sectoral regulator. TSPs are required under the DoT allocation framework to verify this before assigning any 1600-series number. Entities should pull their current registration certificate and confirm the exact registered name that will appear in the TSP’s records, because name mismatches slow the process.

Step 2: Register as a Principal Entity on the DLT Platform

Next, DLT registration is mandatory before a 1600-series number can be activated. The entity registers itself as a Principal Entity on the DLT platform operated by an access provider. This registration captures the entity’s identity, regulatory status, and the categories of calls it intends to make. The registration process typically takes 2 to 3 weeks for first-time registrants, according to clients I advise in the telecom space, largely because document verification queues at the DLT operator level create the delay.

Step 3: Register Voice Call Templates

Simultaneously, every voice script, including IVR openers, agent introductions, OTP delivery prompts, and EMI reminders, must go through pre-registration as a content template on the DLT platform. Each template receives a unique Template ID. The calling system must include this Template ID in the call signalling for every outbound call. Calling with an unregistered or outdated template is a violation, even if the 1600-series number is itself a valid allocation.

Step 4: Apply to a TSP for Number Allocation and Configure Your System

Finally, after DLT registration is confirmed, the entity applies to a Telecom Service Provider for the actual 1600-series number allocation. The TSP verifies the entity’s eligibility and DLT registration status before assigning the number. Subsequently, the entity must configure the allocated number in its IVR, dialer, CRM, and call recording systems. The entity must update all outbound trunks for service and transactional calls to use the new 1600-series CLI before go-live.

FreJun coordinates Steps 2, 3, and 4 directly. The entity provides its regulatory registration details; FreJun manages the DLT registration, template submission, and number configuration end-to-end. Most clients reach go-live within 5 to 7 business days.

What Is DLT Registration and Why Is It Non-Negotiable?

DLT registration is non-negotiable in any 160 series BFSI setup. First, a TSP cannot activate a 1600-series number until the entity completes DLT Principal Entity registration. Second, every outbound call is validated at the telecom layer against the DLT registry; the telecom layer rejects a call from a 1600-series number carrying an unregistered Template ID before it reaches the consumer’s handset.

Managing Templates as Scripts Change

In practice, template management is where many BFSI entities experience operational friction after go-live. New product launches, regulatory updates, and seasonal campaigns require new or updated voice scripts. If template registration runs manually outside the deployment cycle, non-compliant calls get rejected at the telecom layer before they reach the customer. FreJun’s platform integrates DLT template submission into the deployment pipeline: new scripts are submitted automatically, and Template IDs sync back to the calling system without manual intervention.

Moreover, the entity must log Template IDs against corresponding Call Detail Records (CDRs). This is an audit-trail requirement under TCCCPR and under the data retention obligations that RBI imposes on regulated entities. FreJun’s CDR logging module captures Template ID, caller CLI, timestamp, and call duration in a format that meets both TRAI and RBI audit requirements.

Why Must 140 and 1600 Series Traffic Be Kept Separate?

Routing segregation is a core part of any proper 160 series BFSI setup. A single dialer instance cannot route both 140-series promotional traffic and 1600-series transactional traffic through the same number pool. The boundary must be technical, enforced in the routing logic, not merely stated in a policy document.

The Practical Reason Segregation Matters

For example, consider a collections team using a shared dialer that handles both EMI reminder calls (service calls, must use 1600-series) and cross-sell calls (promotional calls, must use 140-series). If both call types run through the same outbound trunk, one of three problems occurs: either the 1600-series number carries a promotional call (a direct TCCCPR violation), or the 140-series number carries a transactional call (also a violation after the mandate deadline), or the caller ID presented to the consumer does not match the allocated number (an anti-spoofing violation under Section 42 of the Telecommunications Act, 2023).

Consequently, the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR), as amended on 12 February 2025, require marketing campaigns and OTP delivery to operate through entirely separate outbound trunks. FreJun enforces this at the platform level by assigning distinct trunk pools to each call category, so the routing split is built into the system, not just written in a policy.

What Auditors Look For

Specifically, during a TRAI or sectoral-regulator audit, the auditor will request CDR logs mapped to Template IDs and the corresponding number series used for each call category. If the CDRs show 1600-series numbers associated with promotional Template IDs, that is direct evidence of a violation. Similarly, if the same outbound trunk appears in CDRs for both 140-series and 1600-series calls, the auditor will infer that routing segregation was not technically enforced. Consequently, the compliance documentation must show separate trunk configurations, not just a policy statement.

What Operational Rules Apply When Using 1600-Series Numbers?

However, the 1600-series mandate covers more than just number provisioning. Several operational rules govern how calls may be made once the number is active. Each rule has an its own enforcement route, meaning a single non-compliant call can simultaneously attract action under telecom law, sectoral regulation, and data protection law.

Call Timing and Frequency Rules

The RBI Fair Practices Code and the RBI Responsible Lending Conduct Directions restrict recovery and collection contact to 08:00 to 19:00 IST. Customer-initiated contact outside that window is permitted, but outbound contact from the BFSI entity is not. For transactional calls such as OTPs and account alerts, the TCCCPR Second Amendment (12 February 2025) limits transactional content to messages triggered within 30 minutes of a customer-initiated transaction. Anything beyond that 30-minute window is treated as service content and requires the corresponding consent stack.

Consent Rules Under the Second Amendment

Specifically, implicit consent for transactional or service calls is valid only for the duration of the underlying contract between the BFSI entity and the customer. Explicit consent holds valid for 7 days from grant for the specific stated purpose. Once a subscriber opts out, the entity may not contact them again for 90 days on the same purpose. These consent periods are stricter than many BFSI teams expect, particularly for entities with short-cycle products such as personal loans or insurance renewals.

Caller ID and Anti-Spoofing Rules

Section 42 of the Telecommunications Act, 2023 makes it a crime to tamper with telecommunication identifiers. TRAI’s TCCCPR requires the originating number presented in the call to be the actual allocated number; no masking and no overlay are permitted. After the mandate, any service or transactional call made from a virtual number masking the allocated 1600 number, or from a number not allocated to the entity, TRAI treats it as unauthorised commercial communication. FreJun’s CLI presentation layer passes the entity’s registered 1600-series number as the calling line identity for every outbound call, ensuring CNAP (Calling Name Presentation) compliance on the consumer’s handset.

What Are the Penalties for Non-Compliance?

Indeed, non-compliance with the 1600-series mandate and the associated TCCCPR rules attracts a multi-layered penalty structure. A single non-compliant calling pattern can simultaneously trigger action under telecom law, sectoral regulation, data protection law, and in serious cases, criminal law.

TCCCPR Financial Penalties Per Violation Instance

• First instance: Rs 2,00,000
• Second instance: Rs 5,00,000
• Third and subsequent instances: Rs 10,00,000

Service Suspension and the One-Year Blacklist

Materially more disruptive than the financial penalty is the service suspension and blacklisting mechanism. The blacklist trigger is 5 valid complaints in any rolling 10-day period. On the first crossing of that threshold, TRAI bars outgoing services on all telecom resources of the sender for 15 days. On a subsequent violation, TRAI disconnects all telecom resources of the sender, including PRI and SIP trunks, across all TSPs for up to one year, and blacklists the sender.

Ultimately, for a BFSI entity, a one-year blacklist is a major operational disaster. OTPs cannot be delivered, customer-service calls cannot be made, and collections cease entirely. The cost of any one violation cycle, including revenue loss, regulatory remediation, and reputational damage, far exceeds the cost of a compliant setup from day one. This is the single fact that compliance officers and CTOs should communicate clearly to their boards.

Sectoral Regulator and DPDP Act Penalties

Furthermore, non-compliance exposes the regulated entity to independent action by its sectoral regulator. The RBI may act under Section 35A of the Banking Regulation Act, 1949, or Section 45L of the RBI Act, 1934. IRDAI may act under Sections 102 to 105B of the Insurance Act, 1938. Additionally, if the misuse involves a breach of personal data obligations under the Digital Personal Data Protection Act, 2023, the Data Protection Board may impose penalties of up to Rs 250 crore for failure to take reasonable security safeguards. These sectoral and data-protection penalties apply independently of any TRAI penalty for the same underlying conduct.

How FreJun Makes 160 Series BFSI Setup Simple and Compliant

FreJun is an AI-powered cloud telephony platform built to make 160 series BFSI setup fast, compliant, and fully integrated. Specifically, the platform handles the full technical compliance layer so your legal and operations teams focus on core compliance duties rather than technical setup.

160 Series BFSI Setup Step One: Number Provisioning and DLT Management

FreJun coordinates directly with TSPs to provision your entity’s 1600-series numbers. The platform manages your Principal Entity registration on the DLT platform, handles voice template submission, syncs Template IDs back to your calling system, and maintains the CDR-to-Template-ID mapping required for audit trails. When scripts change, FreJun’s DLT integration pushes the updated templates automatically, eliminating the manual registration bottleneck that disrupts most entities mid-operation.

Technical Routing Segregation Between 140 and 1600 Series

Specifically, FreJun enforces routing segregation at the platform architecture level. Separate outbound trunk pools are assigned to your 140-series promotional traffic and your 1600-series transactional traffic. The two streams cannot co-mingle in the routing layer. This structural separation satisfies the TRAI and RBI audit requirement that segregation be technical, not merely a policy statement. Compliance documentation generated by FreJun reflects the separate trunk configurations, making audits straightforward.

CRM Integration and Workflow Automation

Additionally, FreJun integrates natively with HubSpot, Zoho CRM, Salesforce, and LeadSquared. FreJun logs every outbound call made from a 1600-series number automatically in the CRM with the call recording, call duration, agent name, and Template ID used. Collections teams gain a single dashboard view across all customer interactions. Additionally, FreJun’s AI call summaries reduce manual follow-up time by automatically tagging call outcomes and generating next-step notes in the connected CRM.

Recovery Agent and BPO Routing Under the Principal Entity

Moreover, FreJun’s multi-user architecture allows recovery agents and BPO teams to make outbound calls under the Principal Entity’s 1600-series number header. Agents dial through the FreJun platform; the consumer sees the Principal Entity’s verified 1600-series CLI. This eliminates the vicarious-liability exposure that arises when agents use their own number pools. Moreover, the Principal Entity’s compliance officers monitor all agent calls in real time through the FreJun dashboard, satisfying the board-approved Code of Conduct requirement for recovery agent oversight.

See exactly how FreJun maps to your entity’s compliance workflow. The demo covers 1600-series number setup, DLT template management, CRM integration, and the routing segregation audit trail. Most BFSI teams complete the entire review in under 45 minutes.

Frequently Asked Questions

160 series vs 140 series: what is the key legal difference?

The 160 series (1600xxxxxxx) is restricted to service and transactional voice calls only, used exclusively by verified Principal Entities. The 140 series (140xxxxxxx) is restricted to promotional and telemarketing calls only. Using either series for the wrong call type is an independent TCCCPR violation, carrying penalties from Rs 2 lakh to Rs 10 lakh per instance plus potential blacklisting of all telecom resources.

What penalty does an NBFC face for not migrating to 1600 series by the deadline?

After the applicable deadline, TRAI classifies every service or transactional call made from a 10-digit number as Unsolicited Commercial Communication from an Unregistered Telemarketer. The TCCCPR penalty escalates from a warning to a usage cap and finally to disconnection of all telecom resources. Additionally, 5 valid complaints within any 10-day period trigger a blacklist of up to one year across all TSPs.

How does a BFSI entity apply for and get a 1600-series number?

A 160 series BFSI setup requires four steps: confirm sectoral regulatory registration, register as a Principal Entity on the DLT platform, submit all voice templates, then apply to a TSP for number allocation. The TSP verifies eligibility before assigning the number. FreJun manages Steps 2 through 4 end-to-end, with most entities reaching go-live within 5 to 7 business days.

Can a recovery agency use its own number pool for calls on behalf of a bank?

No. A recovery agency or BPO acting on behalf of a regulated BFSI entity must use the Principal Entity’s allocated 1600-series numbers, not its own pool. The Principal Entity carries legal responsibility under TCCCPR and the RBI Fair Practices Code for all calls made by its agents. FreJun’s multi-user architecture routes all agent calls under the Principal Entity’s 1600-series CLI to enforce this requirement.

Is DLT registration required before a 1600-series number can be activated?

Yes. DLT Principal Entity registration is a mandatory prerequisite. A TSP cannot assign a 1600-series number to an entity that has not completed DLT registration. Furthermore, every voice template must be pre-registered on the DLT platform and carry a valid Template ID in call signalling. Calling with an unregistered template is a violation even when the 1600-series number itself is a valid allocation.

How does FreJun handle routing segregation between 140 and 1600 series traffic?

FreJun enforces segregation at the platform architecture level by assigning separate outbound trunk pools to 140-series promotional traffic and 1600-series transactional traffic. The two streams cannot share the same trunk. This structural separation satisfies the TRAI and RBI audit requirement that segregation be technical and not merely stated in a compliance policy document.

What CRMs does FreJun integrate with for BFSI call compliance?

FreJun integrates natively with HubSpot, Zoho CRM, Salesforce, and LeadSquared. FreJun automatically logs every outbound call from a 1600-series number in the connected CRM with the call recording, duration, agent name, and DLT Template ID. AI-generated call summaries reduce manual follow-up time and provide the audit trail that TRAI and RBI inspections require.

Key Takeaways

• TRAI has mandated 1600-series adoption for all RBI-, SEBI-, PFRDA-, and IRDAI-regulated entities, making 160 series BFSI setup a legal requirement. Phase-wise deadlines ran from 1 January 2026 to 15 March 2026 (PRID 2191647; PRID 2205350).
• Furthermore, the 140 series is restricted to promotional calls only; the 1600 series is restricted to service and transactional calls only. Misusing either series is an independent TCCCPR violation.
• DLT registration, voice template pre-registration, and routing segregation between 140 and 1600 series traffic are all mandatory technical steps, not optional enhancements.
• Notably, the one-year blacklist across all TSPs is the most operationally severe enforcement lever TRAI holds; 5 valid complaints in any 10-day window is all it takes to trigger the process.
• Recovery agents and BPOs must use the Principal Entity’s 1600-series numbers; the Principal Entity carries legal responsibility for all agent conduct under TCCCPR and the RBI Fair Practices Code.
• FreJun provisions 1600-series numbers, manages DLT end-to-end, enforces technical routing segregation, and integrates with HubSpot, Zoho, Salesforce, and LeadSquared, handling the compliance plumbing so your team focuses on business outcomes.
• A compliant setup costs materially less than one violation cycle; the penalties, revenue loss from blacklisting, and reputational damage make pre-deadline migration the only rational business decision.

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.

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.