160 Series Outbound Call Setup: Compliance Checklist for Operations Teams

Last updated on July 11th, 2026 at 12:33 am

Key Facts at a Glance

Item	Detail
Regulation	TCCCPR, 2018 (Second Amendment, 12 Feb 2025)
Governing body	TRAI and DoT
Applies to	All RBI, SEBI, PFRDA, and IRDAI-regulated BFSI entities
Number series	160xxxxxxx (service and transactional calls); 1601xxxxxxx for financial entities
First-violation penalty	Rs 2,00,000
Blacklist trigger	5 valid complaints in any rolling 10-day period
Transactional call window	Within 30 minutes of customer-initiated event
Deadline status (Commercial Banks)	1 January 2026 (already passed)
Deadline status (Large NBFCs, Payments Banks, SFBs)	1 February 2026 (already passed)
Deadline status (Remaining NBFCs, Co-op Banks, RRBs)	1 March 2026
Deadline status (SEBI: Mutual Funds and AMCs)	15 February 2026 (already passed)
Deadline status (SEBI: Qualified Stockbrokers)	15 March 2026
Deadline status (PFRDA: CRAs and Pension Fund Managers)	15 February 2026 (already passed)

• The 160 series outbound call setup requires five technical layers: number procurement, DLT registration, dialer segregation, CDR configuration, and consent management.
• TRAI mandated phase-wise deadlines from 1 January 2026 to 15 March 2026 across RBI, SEBI, and PFRDA-regulated entities (TRAI Direction, PRID 2191647).
• Every voice script must be pre-registered as a DLT content template before a single call goes live. Calling with an unregistered template is a violation regardless of whether your 1600 number is validly allocated.
• Recovery agents, BPOs, and outsourced call centres must dial from the Principal Entity’s allocated 1600 number. The Principal Entity carries vicarious liability for every agent call.
• FreJun provisions and manages 1600 series numbers end-to-end, including DLT template registration, call routing segregation, and CDR logging.

Table of Contents

1. What Is 160 Series Outbound Call Setup?
2. Phase-Wise Deadlines: Where Does Your Entity Stand?
3. Step 1: Number Procurement for Your 160 Series Call Setup
4. Step 2: DLT Registration for 160 Series Call Setup Compliance
5. Step 3: Dialer Segregation in Your 160 Series Call Setup
6. Step 4: CDR Logging and Audit Trail Configuration
7. Step 5: Consent Stack and Calling Window Verification
8. Recovery Agents and Outsourced BPOs: The Vicarious Liability Trap
9. What Happens If You Miss a Step?
10. How FreJun Helps Operations Teams Go Live Compliantly
11. Frequently Asked Questions
12. Key Takeaways
13. Compliance Disclaimer
14. References and Sources

Quick Answer: A 160 series outbound call setup requires five layers: obtain a 1600 number from a licensed TSP, register all voice scripts on the DLT platform, segregate your dialer so 1600 traffic never mixes with 140 promotional lines, configure CDR logging for every call, and verify your consent stack matches the TCCCPR Second Amendment rules. Every layer is mandatory before going live.

What Is 160 Series Outbound Call Setup?

The 160 series call setup is the end-to-end technical and compliance process that a BFSI entity must complete before it can legally route service or transactional voice calls from a DoT-allocated 160xxxxxxx number. This 160 series call setup is not a single registration step. Instead, it is a layered sequence of five distinct actions, each governed by a separate regulatory obligation under the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) and its Second Amendment dated 12 February 2025.

In my practice advising telecom-sector clients, I have seen operations teams assume that receiving a 1600 number from a TSP is the finish line. It is not. Instead, the number allocation is only the first step. Calling from that number without completing DLT template registration, dialer segregation, and consent verification is a TCCCPR violation on the very first call.

Get Legal Guidance

Most BFSI operations teams underestimate the DLT template approval window. It typically takes 2 to 3 weeks for first-time registrants. FreJun’s team walks you through every step so your calls go live on schedule, not after your compliance deadline.

Phase-Wise Deadlines: Where Does Your Entity Stand?

The TRAI Direction dated 19 November 2025 (PRID 2191647) set binding phase-wise deadlines for 1600 series adoption across RBI-, SEBI-, and PFRDA-regulated entities. A parallel Direction dated 16 December 2025 (PRID 2205350) brought IRDAI-regulated insurers within the same framework, with specific deadlines to be notified separately. The operative TRAI Direction text confirms the deadlines below.

RBI-Regulated Entities

• Commercial Banks (Public Sector, Private Sector, Foreign Banks): 1 January 2026 (deadline passed)
• Large NBFCs (asset size above Rs 5,000 crore), Payments Banks, Small Finance Banks: 1 February 2026 (deadline passed)
• Remaining NBFCs, Co-operative Banks, Regional Rural Banks, and smaller entities: 1 March 2026

SEBI-Regulated Entities

• Mutual Funds and Asset Management Companies: 15 February 2026 (deadline passed)
• Qualified Stockbrokers (QSBs): 15 March 2026
• Other SEBI-registered intermediaries: Voluntary migration permitted after verification of registration details

PFRDA-Regulated Entities

• Central Recordkeeping Agencies (CRAs) and Pension Fund Managers: 15 February 2026 (deadline passed)

What this means for your compliance team: if your entity’s deadline has passed and you have not yet migrated, every service or transactional call made from a standard 10-digit mobile number is already classified as Unsolicited Commercial Communication from an Unregistered Telemarketer (UTM). Consequently, the enforcement progression for UTMs begins with a warning and escalates to full disconnection of all telecom resources. Additionally, 485 entities adopted the series voluntarily before the mandates, covering over 2,800 numbers (TRAI, PRID 2191647, 19 November 2025). Therefore, your competitors likely already have their 1600 numbers live and operational.

Step 1: Number Procurement for Your 160 Series Call Setup

The first step in any 160 series call setup is obtaining a 1600xxxxxxx number from a Telecom Service Provider (TSP) that holds a valid Unified Licence (UL) or UL-VNO authorisation from DoT. This step is not optional. A 1600 number cannot be self-allocated. The TSP must verify the Principal Entity’s eligibility before assigning any number from the series.

160 Series Call Setup Checklist: Number Procurement

• Confirm your TSP holds a valid UL or UL-VNO authorisation. Verify through the SARAL SANCHAR portal at saralsanchar.gov.in.
• Prepare your entity’s registration proof with the relevant sectoral regulator (RBI Certificate of Registration, SEBI registration certificate, IRDAI licence, or PFRDA authorisation).
• Submit the eligibility declaration to the TSP. The declaration is a contractual undertaking that the number will be used only for service and transactional calls under TCCCPR, 2018.
• Confirm the number falls within the 1601xxxxxxx sub-prefix range if your entity is regulated by RBI, SEBI, PFRDA, or IRDAI.
• Obtain written confirmation from the TSP of the allocated number and its activation date. Retain this as an audit document.
• If you use a cloud telephony provider such as FreJun, confirm that the provider sources numbers through a licensed UL or UL-VNO holder, not through a chain of sub-allocations.

In practice, most BFSI entities find that the TSP verification step takes 5 to 10 business days if documentation is complete on submission. Notably, incomplete regulatory certificates are the most common cause of delay. Therefore, prepare all documents before approaching the TSP.

Step 2: DLT Registration for 160 Series Call Setup Compliance

Your team must pre-register every voice script that your 1600 number will carry as a content template on the Distributed Ledger Technology (DLT) platform operated by a licensed access provider. This is the step that most operations teams underestimate. The DLT requirement applies to every IVR opener, agent introduction script, EMI reminder, OTP delivery flow, and collection follow-up message.

160 Series Call Setup Checklist: DLT Registration

• Register your entity as a Principal Entity (PE) on the DLT platform of a licensed access provider. Registration requires the same regulatory certificates used for TSP onboarding.
• Register your entity header, which is the caller identification string that will appear on the DLT record for every outbound call.
• Draft and submit every voice script your team will use. Each script becomes a separate template and receives a separate Template ID upon approval.
• Ensure each template correctly identifies the call category: service call or transactional call. The category affects the consent basis required to place the call.
• Do not use variable fields in templates beyond what the DLT platform permits. Variable fields outside approved parameters invalidate the template registration.
• Retain a copy of every Template ID. The Template ID must be passed in call signalling. Calling with an unregistered, outdated, or blacklisted template is a violation regardless of whether your 1600 number is validly allocated.
• Allow 2 to 3 weeks for first-time template approval. Build this buffer into your go-live timeline.
• If you modify any script after approval, submit the modified version as a new template. The old Template ID does not cover the modified script.

What this means for your compliance team: DLT template registration is not a one-time exercise. Consequently, every time your collections or customer service team updates a calling script, your team must submit a new template registration. Therefore, build a template change management process into your standard operating procedures before going live.

Step 3: Dialer Segregation in Your 160 Series Call Setup

Routing logic must enforce segregation at the system level. The same dialer instance cannot route both 140 promotional traffic and 1600 transactional traffic through the same number pool. This is one of the most operationally significant requirements in the 160 series outbound call setup, and it is also one of the most commonly overlooked.

Auditors and regulators have been clear that a written policy without enforced routing logic does not amount to adequate compliance. Moreover, marketing campaigns and OTP delivery must never share the same outbound SIP trunk or PRI. Consequently, your IT team must enforce the boundary at the system configuration level, not just in a policy document.

160 Series Call Setup Checklist: Dialer and IVR Segregation

• Verify that your dialer platform supports independent outbound trunk configuration. The 1600 series trunk must be a separate logical or physical path from the 140 series trunk.
• Configure your IVR routing rules to prevent any promotional campaign from accessing the 1600 series number pool. This configuration must be enforced at the system level, not merely documented in policy.
• If your entity uses a shared BPO or outsourced call centre platform, verify that the vendor’s infrastructure can enforce trunk segregation for your specific entity’s numbers. A shared infrastructure that commingles 140 and 1600 traffic creates a cross-use violation.
• Test the segregation with a pilot batch of 10 to 20 calls before going live at full volume. Confirm that the CLI (Calling Line Identification) presented to the recipient matches your allocated 1600 number exactly.
• Implement CLI spoofing prevention controls. Section 42 of the Telecommunications Act, 2023 criminalises tampering with telecommunication identifiers. Additionally, TRAI’s TCCCPR requires the originating number to be the actual allocated number, with no masking or overlay.
• Document the segregation configuration in a technical architecture diagram. Retain this as evidence for regulatory audits.

In practice, cloud telephony platforms that natively support 1600 series numbers simplify segregation significantly. For example, a platform such as FreJun configures separate call routing paths for 1600 and 140 numbers at the infrastructure layer, removing the need for your IT team to manage trunk segregation manually.

Talk to FreJun’s Legal Team

FreJun’s platform enforces 1600 and 140 series segregation at the infrastructure layer automatically. Your IT team does not need to configure separate SIP trunks manually. Book a walkthrough to see exactly how the routing works for your use case.

Step 4: CDR Logging and Audit Trail Configuration

Call Detail Records (CDRs) are not an optional reporting feature. Therefore, the Principal Entity must retain full CDRs in auditable form, mapped to the Template ID invoked for each call. Notably, the TCCCPR, RBI fair practices requirements, and the Digital Personal Data Protection Act, 2023 (DPDP Act) all place independent retention obligations on the entity.

Checklist: CDR Logging

• Confirm your telephony platform generates CDRs for every outbound call, including calls that were unanswered or disconnected before answer.
• Each CDR must record: the originating 1600 number, the destination number, call timestamp, call duration, the Template ID used, and the agent or IVR identifier that placed the call.
• Map each CDR to the consent record for the called number. If consent was the legal basis for the call, the consent record must be retrievable alongside the CDR.
• Retain CDRs for the minimum period specified in your TSP’s licence conditions. Note that RBI and other sectoral regulators often impose longer retention requirements. Verify the applicable retention period for your entity category.
• Store call recordings, where your workflow involves recording, in a format that can be produced in response to a regulatory inquiry or consumer complaint.
• Maintain a complaint log and the related resolution trail. The DPDP Act, 2023 requires the entity, as a Data Fiduciary, to demonstrate lawful basis, purpose limitation, and retention controls on demand from the Data Protection Board.
• Confirm that your entity must host call data and recordings for Indian customers on servers located in India. The RBI Storage of Payment System Data circular dated 6 April 2018 requires payment-related data to be stored only in India. CDRs that contain payment transaction references fall within this requirement.

What this means for your compliance team: CDR mapping to Template IDs is the single strongest evidence of TCCCPR compliance. Specifically, an entity that can produce a CDR with the correct Template ID for every call made over the past year is materially better positioned in a regulatory inquiry than one that cannot. Therefore, configure this logging before your first live call.

Step 5: Consent Stack and Calling Window Verification

The Second Amendment to TCCCPR, dated 12 February 2025, significantly tightened consent rules for BFSI users of 1600 series numbers. As a result, operations teams must verify the consent basis for every number in their outbound list before the first call. Moreover, using an incorrect or expired consent basis is a violation independent of whether the calling script is properly registered.

Consent Rules Under TCCCPR Second Amendment, 2025

• 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 for transactions where there is no continuing contractual relationship is valid for only 7 days from the date your team captured the consent.
• Opt-out lockout: a sender cannot contact a customer who has opted out until 90 days have elapsed from the opt-out date, on the same purpose for which opt-out was exercised.
• Auto-dialer and robo-call disclosure: if your outbound calls use an auto-dialer or pre-recorded message, you must disclose this at the start of the call.
• Digital Consent Acquisition (DCA): consent capture must align with the DCA framework on the DLT platform. Consent captured outside the DCA framework does not satisfy the TCCCPR consent requirement.

Calling Window Rules

• Transactional calls may only be made within 30 minutes of the customer-initiated event that triggered them. An OTP call made 35 minutes after the customer’s login attempt is outside the permitted window and is treated as a service call requiring the corresponding consent stack.
• Collection and recovery calls from the BFSI side must be made only between 08:00 and 19:00 IST. This restriction comes from the RBI Fair Practices Code and the RBI Responsible Lending Conduct directions. Customers may initiate contact outside those hours, but the entity must not make outbound contact outside the 08:00 to 19:00 IST window.

Checklist: Consent Stack Verification

• Audit your existing customer contact list. Categorise each record by consent type: implicit (existing customer with active contract), explicit (with expiry date captured), or no consent (do not call).
• Remove from your outbound list every number where explicit consent has expired or where the customer has opted out within the past 90 days.
• Configure your dialer to enforce the 30-minute transactional call window automatically. Any call placed outside the window must be re-classified as a service call and checked against the applicable consent basis before dialling.
• Configure your dialer to block outbound calls to any number outside the 08:00 to 19:00 IST window for collection and recovery campaigns.
• Implement the DCA framework on your DLT registration. Consent records must be retrievable by customer number and purpose category.
• Verify that your consent capture process for new customers creates a DCA-compliant record at the point of onboarding, not retrospectively.

Additionally, the use of customer data for calling intersects with Section 7 of the DPDP Act, 2023, which requires data processing to rest on either consent or a specified legitimate use. A service or transactional call to your own customer typically falls under the legitimate-use basis, but the lawful basis must be documented in your privacy notice and processing register.

Recovery Agents and Outsourced BPOs: The Vicarious Liability Trap

DoT allocates the 1600 series number to the Principal Entity: the bank, NBFC, insurer, or other regulated entity. It is not allocated to the recovery agency, BPO, or outsourced call centre that places calls on behalf of the entity. This is the most misunderstood area in BFSI outbound compliance, and it is the source of the majority of TCCCPR violations I encounter in practice.

The Correct Legal Position

• A recovery agency, telemarketer, or BPO acting on behalf of the Principal Entity must place calls from the Principal Entity’s allocated 1600 number, not from its own number pool.
• The Principal Entity carries vicarious liability for every call placed by its agent under TCCCPR, the RBI Fair Practices Code, and the RBI Master Direction on Outsourcing of Information Technology Services dated 10 April 2023.
• Individual recovery agents must hold a valid IIBF certification obtained after the prescribed 100-hour training programme.
• The Principal Entity must maintain a board-approved Code of Conduct for recovery agents.
• If a BPO places a collection call from its own 10-digit number on behalf of your entity, that call is already a TCCCPR violation attributed to your entity. The entity cannot contract out its liability to the BPO.

Checklist: Third-Party Vendor Compliance

• Audit every third-party vendor that places outbound calls on your behalf. Confirm that each vendor routes calls from your allocated 1600 number, not from a number pool held in the vendor’s own name.
• Include contractual representations in all BPO and recovery agency agreements requiring the vendor to use only your allocated 1600 numbers for calls on your behalf.
• Require your BPO vendor to provide call logs with CLI data confirming that your 1600 number was the originating number for every call placed under your contract.
• Verify that individual recovery agents engaged by your BPO hold current IIBF certifications. Retain copies of certification records.
• Confirm your board-approved Code of Conduct for recovery agents is current and includes the 1600 series number usage requirement.

What this means for your compliance team: the moment you sign a BPO or recovery agency contract, your entity’s TCCCPR compliance depends on that vendor’s calling infrastructure. Therefore, conduct a technical due diligence review of every vendor’s dialer setup before the contract goes live. Specifically, verify that the vendor can route calls from your allocated 1600 number, not their own pool.

What Happens If You Miss a Step?

Missing any single step in the 160 series call setup exposes your entity to a multi-layered penalty response. Specifically, a non-compliant calling pattern can simultaneously attract action under telecom law, sectoral regulation, data protection law, and, in aggravated cases, criminal law.

TCCCPR Financial Disincentives

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

Service Suspension and Blacklisting

The blacklist trigger is only 5 valid complaints in any rolling 10-day period. Consequently, the action that follows is materially more disruptive than the financial penalty. A first violation of the regulatory complaint threshold triggers a 15-day bar on outgoing services across all the sender’s telecom resources. Subsequent violations result in full disconnection of all telecom resources across all access providers for up to one year, and TRAI blacklists the entity entirely.

Furthermore, a one-year blacklist is operationally catastrophic for a BFSI entity. OTPs cannot be delivered, customer service calls stop entirely, and collections cease. Therefore, the business case for completing the 160 series call setup correctly the first time is not just regulatory risk management. It is a business continuity imperative.

Treatment as Unregistered Telemarketer

If your entity has passed its applicable phase-wise deadline and continues to make service or transactional calls from standard 10-digit mobile numbers, TRAI classifies those calls as Unsolicited Commercial Communication from an Unregistered Telemarketer. Furthermore, the enforcement progression begins with a warning, then a usage cap of 20 outgoing voice calls per day imposed for six months, and finally disconnection of all telecom resources.

Sectoral Regulator Action

Non-compliance with the 1600 series mandate also exposes your entity to action by its sectoral regulator. Notably, TRAI issued the Direction after Joint Committee of Regulators (JCoR) consultations involving RBI, SEBI, IRDAI, and PFRDA. Indicative statutory provisions include Section 35A of the Banking Regulation Act, 1949 (RBI), Sections 102 to 105B of the Insurance Act, 1938 (IRDAI), Section 15HB of the SEBI Act, 1992 (SEBI), and Section 28 of the PFRDA Act, 2013. Importantly, sectoral regulator penalties apply independently of any TRAI penalty for the same underlying conduct.

How FreJun Helps Operations Teams Go Live Compliantly

FreJun is a cloud telephony platform built specifically for BFSI compliance. Furthermore, the platform provisions and manages 1600 series and 140 series numbers for regulated entities, handling the technical compliance layer so your operations team can follow this 160 series call setup checklist without needing a separate engineering team to configure each step from scratch.

What FreJun Handles for You

• Number procurement: FreJun sources 1600 series numbers through licensed TSP partners and manages the entity verification and allocation process.
• DLT template management: The platform integrates with the DLT infrastructure. Your team submits scripts through the FreJun dashboard, and FreJun manages the template registration, Template ID assignment, and call signalling linkage.
• Dialer segregation: FreJun enforces separate call routing paths for 1600 and 140 series numbers at the infrastructure layer. The segregation is a platform default, not a configuration option your team must activate.
• CDR logging: Every call record is logged automatically with the originating 1600 number, destination, timestamp, duration, and Template ID. Logs are exportable for audit production.
• CRM integration: FreJun integrates with HubSpot, Zoho, Salesforce, and LeadSquared. Consent records and CDRs can be linked to customer profiles in your existing CRM, simplifying the consent stack audit.
• Data residency: FreJun hosts Indian customer call data on Indian servers, meeting the RBI data localisation requirement.

FreJun is not a Telecom Service Provider and does not offer legal advice. However, the platform is built specifically for the BFSI compliance stack. Therefore, your legal team can focus on the substantive obligations rather than the technical plumbing of the 160 series call setup.

Talk to FreJun’s Legal Team

See how FreJun’s end-to-end 1600 series setup works for a BFSI operations team. From number procurement to CDR logging, the demo walks through every checklist item live. Most teams are fully configured within 10 to 15 business days of first contact.

Frequently Asked Questions

What is the difference between 160 series and 140 series numbers in India?

DoT reserves the 160 series exclusively for service and transactional voice calls by verified BFSI and other regulated entities. DoT reserves the 140 series exclusively for promotional and telemarketing calls. The two series cannot be used interchangeably. A 1600 number must never carry a promotional message, and a 140 number must never carry a service or transactional call after the 160 series mandate came into effect.

What is the penalty for using a 10-digit number for transactional calls after the deadline?

After your entity’s applicable phase-wise deadline, every service or transactional call made from a standard 10-digit mobile number is classified as Unsolicited Commercial Communication from an Unregistered Telemarketer. Financial disincentives under TCCCPR start at Rs 2,00,000 for the first violation and reach Rs 10,00,000 for the third and subsequent violations. Blacklisting of all telecom resources for up to one year is also possible after 5 valid complaints in 10 days.

How does an entity apply for a 1600 series number?

An entity begins the 160 series call setup by applying for a 1600 series number through a TSP holding a valid Unified Licence or UL-VNO authorisation from DoT. The TSP verifies eligibility using the entity’s sectoral regulator registration certificate. The entity then submits a declaration undertaking that the number will be used only for service and transactional calls under TCCCPR, 2018. Additionally, number activation typically takes 5 to 10 business days after documentation is complete.

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

No. A recovery agency, BPO, or outsourced call centre acting on behalf of a Principal Entity must place calls from the Principal Entity’s allocated 1600 number. Using the vendor’s own number pool is a TCCCPR violation attributed to the Principal Entity, not the vendor. The Principal Entity carries vicarious liability for every call placed by its agents under TCCCPR and the RBI Fair Practices Code.

What are the DLT template registration requirements for 160 series outbound calls?

Every voice script your 1600 number will carry must be pre-registered as a content template on the DLT platform operated by a licensed access provider. Each approved script receives a unique Template ID, which must be passed in call signalling. Calling with an unregistered, outdated, or blacklisted template is a TCCCPR violation regardless of whether the 1600 number itself is validly allocated. Template approval typically takes 2 to 3 weeks for first-time registrants.

What is the transactional call window for 1600 series numbers?

A transactional call from a 1600 series number may only be placed within 30 minutes of the customer-initiated event that triggered it, such as a login, a payment, or a form submission. Your team must re-classify any call placed after the 30-minute window as a service call and checked against the applicable service-call consent basis before dialling. This rule comes from the TCCCPR Second Amendment dated 12 February 2025.

Is a cloud telephony platform enough for 160 series compliance, or does the entity need a licensed TSP?

A cloud telephony platform alone is not sufficient. The 1600 number must be allocated through a TSP holding a valid Unified Licence or UL-VNO authorisation from DoT. However, a cloud telephony platform such as FreJun that sources numbers through a licensed TSP and manages DLT integration, call routing segregation, and CDR logging can handle the technical compliance layer on behalf of the entity, significantly reducing setup complexity and time to go-live.

Key Takeaways

• The 160 series outbound call setup has five mandatory layers: number procurement, DLT registration, dialer segregation, CDR logging, and consent stack verification. Every layer is a separate compliance obligation.
• Phase-wise deadlines under the TRAI Direction of 19 November 2025 (PRID 2191647) ran from 1 January 2026 for commercial banks to 15 March 2026 for Qualified Stockbrokers. Entities that have passed their deadline and have not migrated are already in violation.
• DLT template registration is not a one-time exercise. Every updated calling script requires a new template submission and approval before use. Build a template change management process into your SOPs.
• Recovery agents and BPOs must dial from your entity’s allocated 1600 number. Your entity carries vicarious liability for every agent call under TCCCPR and the RBI Fair Practices Code.
• The blacklist trigger is only 5 valid complaints in 10 days, and the maximum blacklist is one year across all telecom resources. For BFSI entities, this means total loss of OTP delivery, customer service calls, and collections for up to a year.
• The DPDP Act, 2023 adds a data-processing compliance layer on top of the TCCCPR requirements. Consent records, CDRs, and call recordings must be retained with documented lawful basis and purpose limitation controls.
• A cloud telephony platform that natively supports 1600 series compliance, such as FreJun, reduces setup time materially and automates the technical layers of the checklist, including DLT integration, segregated routing, and CDR logging.

Read our BFSI communication compliance guide for 2026 for the broader regulatory framework. Additionally, our 160 series vs 140 series comparison covers the key differences in depth. You can also explore our TCCCPR 2018 compliance guide for detailed regulatory obligations.

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 Nov 2025 (PRID 2191647) – pib.gov.in
• TRAI Direction, 16 Dec 2025 (PRID 2205350) – pib.gov.in
• TCCCPR Second Amendment, 12 Feb 2025 – 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.gov.in
• SARAL SANCHAR Portal (TSP licence verification) – saralsanchar.gov.in
• Mondaq Analysis: TRAI 1600 Series Mandate for BFSI – mondaq.com

For Any Questions Reach Out to Our Legal Team

You have seen the full five-step setup checklist. If any item is unclear or your entity has a non-standard setup involving multiple BPOs or CRMs, FreJun’s legal team can walk through your specific architecture and confirm which steps apply to you.

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