How to Get a 160 Series Number in India: Step-by-Step for Banks and NBFCs

Key Facts at a Glance

Item	Detail
Regulation	TCCCPR, 2018 (Second Amendment, 12 Feb 2025)
Governing body	TRAI and DoT, Ministry of Communications
Applies to	All BFSI entities regulated by RBI, SEBI, IRDAI, PFRDA
Number series	160xxxxxxx; sub-prefix 1601xxxxxxx for financial entities
Entities already migrated (Dec 2025)	~570 entities, 3,000+ numbers (TRAI PRID 2205350)
First-violation penalty	₹2,00,000 per instance
Blacklist trigger	5 complaints in any rolling 10-day period
Maximum blacklist duration	1 year across all telecom resources, all TSPs
DLT registration fee	₹5,900 one-time on first platform; free on subsequent TSPs
DLT PE approval time	Up to 7 working days (TRAI direction)
Commercial banks deadline	1 January 2026 (passed)
Large NBFCs (>₹5,000 cr) deadline	1 February 2026 (passed)
Remaining NBFCs / Co-op Banks / RRBs	1 March 2026 (passed)
Mutual Funds and AMCs	15 February 2026 (passed)
Qualified Stockbrokers (QSBs)	15 March 2026 (passed)
IRDAI-regulated insurers	15 February 2026 (TRAI Direction, PRID 2205350, passed)
CRAs and Pension Fund Managers (PFRDA)	15 February 2026 (passed)

• Getting a 160 series number in India is now mandatory, not optional, for every regulated BFSI entity. All phase-wise deadlines under TRAI Direction PRID 2191647 have already passed.
• The process runs in seven sequential steps: confirm eligibility, register on DLT as a Principal Entity, submit TSP documents, register voice templates, apply for number allocation, execute the undertaking, and integrate into your calling infrastructure.
• DLT registration is the unavoidable first step. No TSP will process a 160 series allocation without it. The one-time registration fee is ₹5,900 on your first platform.
• Template inventory preparation is the single biggest determinant of total onboarding time. Map all voice scripts before approaching the DLT portal. This internal step costs nothing and can compress your timeline by up to four weeks.
• Entities still making service calls from 10-digit numbers face classification as Unregistered Telemarketers, escalating penalties up to ₹10,00,000 per instance, and potential one-year disconnection of all telecom resources across all TSPs.

Table of Contents

1. What Is a 160 Series Number in India?
2. Why Did TRAI Create the 160 Series Mandate?
3. Who Is Eligible to Get a 160 Series Number?
4. Phase-Wise Deadlines: Is Your Entity Already in Breach?
5. How to Get a 160 Series Number: Step-by-Step Process
6. DLT Registration: The Non-Negotiable First Step
7. How to Choose the Right TSP for 160 Series Allocation
8. Documents Required for the 160 Series Application
9. Realistic Timeline: How Long Does the Full Process Take?
10. Integrating Your 160 Series Number Into Your Calling Infrastructure
11. Compliance Obligations After Allocation
12. How FreJun Handles 160 Series Provisioning End-to-End
13. Frequently Asked Questions
14. Key Takeaways

Quick Answer: To get a 160 series number in India, a BFSI entity must confirm regulatory eligibility with RBI, SEBI, IRDAI, or PFRDA, register as a Principal Entity on a TSP’s DLT platform for ₹5,900, submit KYC and eligibility documents, register all voice templates, and formally apply to the TSP for 1601 number allocation. The full process typically takes two to four weeks from the date of document submission, provided templates are prepared in advance.

What Is a 160 Series Number in India?

A 160 series number in India is a dedicated telephone prefix — 160xxxxxxx — reserved exclusively for service and transactional voice calls. The Department of Telecommunications (DoT) allocated this series to verified Principal Entities only. The DoT Press Release dated 30 May 2024 (PRID 2022249) formally created this series to give consumers a reliable visual signal that a call is legitimate. When a consumer sees 1601 on their screen, they know the call comes from a regulated financial institution. Specifically, it is not a fraudster pretending to be one.

Specifically, the sub-prefix 1601xxxxxxx applies to financial entities. These include organisations regulated by the Reserve Bank of India (RBI), Securities and Exchange Board of India (SEBI), Insurance Regulatory and Development Authority of India (IRDAI), and Pension Fund Regulatory and Development Authority (PFRDA). Furthermore, the broader 1600xxxxxxx prefix covers other verified service entities and government organisations. In practice, this two-tier structure lets consumers distinguish easily. A government service call starts with 1600; a financial institution call starts with 1601. Specifically, the first four digits tell the story.

What this means for your compliance team: Your entity’s name, as it appears in your sectoral regulator’s records, must match the name on your DLT registration and TSP application exactly. Any discrepancy — even “Pvt. Ltd.” versus “Private Limited” — will cause verification to fail and reset the timeline.

Why Did TRAI Create the 160 Series Mandate?

The 160 series mandate did not emerge in a vacuum. It responded directly to a documented crisis in India’s voice communication ecosystem. Understanding the data behind the mandate helps compliance teams explain the urgency to internal stakeholders who may treat the migration as a low-priority technical task.

The Scale of the Spam Call Problem

India ranks among the world’s worst spam call environments. According to the 2025 India Insights Report cited by S.S. Rana & Co., Indian mobile users received approximately 4,168 crore spam calls in a single year. Additionally, TRAI’s own complaint data shows a 128% surge over three years: from 1.362 million complaints in 2023, rising to 1.938 million in 2024, and climbing further to 3.109 million in 2025 (The420.in, April 2026). Furthermore, more than 60% of Indian mobile users report receiving two to three spam calls or messages daily.

Consequently, genuine service calls from legitimate BFSI entities went unanswered. Banks lost contact with customers. NBFCs missed EMI reminders. Insurance companies failed to confirm policy renewals. In each case, the root cause was the same: consumers could not distinguish a real bank call from a scammer using the same 10-digit format.

The Fraud Loophole the 160 Series Closes

Before the 160 series existed, regulated entities routinely used ordinary 10-digit mobile numbers for OTP delivery, EMI reminders, and loan servicing calls. However, fraudsters discovered that they could impersonate banks and NBFCs using identical 10-digit numbers. The DoT Press Release of 30 May 2024 specifically recognised this problem. The 140 series, originally allocated for telemarketing, became overrun with promotional traffic. Consequently, consumers learned to ignore it entirely. As a result, genuine entities drifted to 10-digit numbers — inadvertently creating the same format fraudsters used.

Additionally, between October 2024 and January 2025, India’s DoT reduced spoofed international call volumes by 90% through a dedicated blocking system, blocking 13.5 million spoofed calls within the first 24 hours alone (GASA, May 2025). The 160 series is the domestic equivalent of that intervention. It makes the number itself a trust signal. Consumers no longer need to recognise individual numbers to distinguish legitimate calls.

Moreover, TRAI has now taken action against over 21 lakh fraudulent mobile numbers and one lakh entities over the past year alone (News on AIR, November 2025). The scale of enforcement reflects the scale of the problem. The 160 series mandate transforms the experience. Instead of a reactive complaint, consumers get proactive identification. Every call from 1601 carries the state’s verification behind it.

What this means for your compliance team: The business case for migration is not only regulatory. Connect rate data from early adopters shows that customers answer 1601 calls more reliably than 10-digit calls. Higher connect rates on OTP delivery and collections follow-up translate directly into operational efficiency and reduced NPA risk.

FreJun provisions 160 series numbers end-to-end for banks and NBFCs — from DLT registration to IVR integration. Most clients go live within two weeks. Talk to our team to start your migration today.

Talk to FreJun’s Legal Team

Who Is Eligible to Get a 160 Series Number?

Eligibility for a 160 series number in India restricts eligibility to entities that hold a current, valid registration from one of four sectoral regulators. The DoT imposed a positive obligation on Telecom Service Providers to verify this eligibility before any allocation. Therefore, your entity must confirm its regulatory standing before approaching a TSP.

RBI-Regulated Entities

• Commercial banks — public sector, private sector, and foreign banks operating in India
• Non-Banking Financial Companies (NBFCs) — both large (asset size above ₹5,000 crore) and smaller NBFCs
• Payments banks and small finance banks
• Co-operative banks and regional rural banks
• Any other entity directly regulated by RBI under the Banking Regulation Act, 1949 or the RBI Act, 1934

SEBI-Regulated Entities

• Mutual funds and Asset Management Companies (AMCs)
• Qualified Stockbrokers (QSBs), as identified annually by stock exchanges
• Other SEBI-registered intermediaries (voluntary migration currently permitted; mandatory phase expected)

IRDAI and PFRDA Entities

• Life insurance, general insurance, and health insurance companies regulated by IRDAI
• Insurance brokers and intermediaries holding an IRDAI licence
• Central Recordkeeping Agencies (CRAs) registered with PFRDA
• Pension Fund Managers and Points of Presence (PoPs) under PFRDA

Importantly, third-party recovery agencies, BPOs, and telemarketers are not eligible to hold 160 series numbers in their own name. However, they may make service and transactional calls on behalf of a BFSI Principal Entity using that entity’s allocated 1601 number. The Principal Entity remains fully and vicariously liable for every call made from its number by any agent or partner. Furthermore, the CLI on every call must display the PE’s 1601 number, not the agency’s own number pool.

What this means for your compliance team: Verify your entity’s current regulatory registration status at the SARAL SANCHAR portal (saralsanchar.gov.in) before beginning the application process. A lapsed or suspended registration blocks allocation until the sectoral regulator confirms reinstatement.

Phase-Wise Deadlines: Is Your Entity Already in Breach?

The TRAI Direction of 19 November 2025 (PRID 2191647) set binding phase-wise deadlines for RBI-, SEBI-, and PFRDA-regulated entities. Subsequently, the TRAI Direction of 16 December 2025 (PRID 2205350) extended the mandate to IRDAI-regulated insurers, setting 15 February 2026 as their adoption date. As of the publication date of this article, every deadline in the table below has already passed.

Complete Phase-Wise Deadline Schedule

Entity Type	Regulator	Mandatory Deadline	Status
Commercial banks (public, private, foreign)	RBI	1 January 2026	Passed
Large NBFCs (asset >₹5,000 cr), payments banks, small finance banks	RBI	1 February 2026	Passed
Remaining NBFCs, co-operative banks, RRBs, smaller entities	RBI	1 March 2026	Passed
Mutual funds and AMCs	SEBI	15 February 2026	Passed
Qualified Stockbrokers (QSBs)	SEBI	15 March 2026	Passed
Other SEBI-registered intermediaries	SEBI	Voluntary (no hard deadline yet)	Voluntary
CRAs and Pension Fund Managers	PFRDA	15 February 2026	Passed
IRDAI-regulated insurers	IRDAI	15 February 2026	Passed

What Happens After a Missed Deadline

An entity that continues using 10-digit numbers after its deadline is automatically classified as an Unregistered Telemarketer (UTM) under TCCCPR. Importantly, the reclassification is immediate and automatic. The enforcement progression is staged but moves quickly. First, TRAI issues a warning. Second, a usage cap of 20 outgoing voice calls per day for six months applies. Third — and most disruptively — all telecom resources of the entity are disconnected for up to one year across all TSPs. For a bank or NBFC, that outcome is operationally catastrophic: OTPs stop, collections cease, and customer service calls cannot be made.

Additionally, sectoral regulators can act independently of TRAI. Under Section 35A of the Banking Regulation Act, 1949, RBI can issue supervisory directions. SEBI can impose penalties under Section 15HB of the SEBI Act, 1992. IRDAI can act under Sections 102 to 105B of the Insurance Act, 1938. These penalties stack on top of TRAI’s financial disincentives, not instead of them.

Furthermore, the blacklist trigger has tightened under the TCCCPR Second Amendment of 12 February 2025. Entities now face disconnection risk after just 5 valid complaints in any rolling 10-day period. The earlier threshold was 10 complaints in 7 days. In practice, a single dissatisfied customer can generate 5 complaints faster than most compliance teams detect the issue. Consequently, the new threshold leaves very little margin.

What this means for your compliance team: If your entity has missed its deadline, migration is urgent, not optional. The fastest path back to compliance is a guided, managed migration — not a self-managed process that risks further delays. For a full breakdown of the penalty framework, see our comprehensive BFSI Communication Compliance Guide 2026.

How to Get a 160 Series Number: Step-by-Step Process

The 160 series number application process follows a defined, sequential workflow. No step can be skipped, and each one is a prerequisite for the next. Below is the complete seven-step process. It draws from the TRAI Direction (PRID 2191647, 19 November 2025), the DoT Press Release (PRID 2022249, 30 May 2024), and the TCCCPR Second Amendment of 12 February 2025.

Step 1: Confirm Regulatory Eligibility

Before contacting any TSP, confirm your entity holds a current, active registration with RBI, SEBI, IRDAI, or PFRDA. Collect the following documents in advance:

• Certificate of Registration or Licence from your sectoral regulator, current and unrevoked
• Entity name exactly as it appears in the regulator’s public records
• Registration or licence number and expiry date, if applicable
• GSTIN and CIN (Company Identification Number) of the legal entity

Notably, subsidiaries and group companies require separate eligibility verification and separate number allocations. Sub-allocation across a corporate group is not permitted without formal re-verification at the TSP level.

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

DLT registration is the foundational prerequisite for 160 series allocation. Select a TSP that operates a TRAI-approved DLT platform. All four major Indian TSPs — Jio, Airtel, Vodafone Idea (Vi), and BSNL — run their own DLT portals. The one-time registration fee is ₹5,900 (inclusive of GST) on the first platform. Subsequent registrations on other TSP platforms carry no additional fee.

According to TRAI’s direction on TCCCPR implementation, the DLT Principal Entity registration review takes a maximum of 7 working days. This clock starts from the submission of all required documents. After PE approval, the TSP assigns your Header (Sender ID) within a maximum of 2 additional working days. Therefore, plan for 9 to 12 working days for the combined DLT registration and header assignment process. However, this estimate assumes complete and consistent documents on first submission.

Step 3: Submit Eligibility Documents to the TSP

Separately from DLT registration, submit your 160 series eligibility package directly to the TSP’s enterprise or business team. This package must include your regulatory registration, KYC documents, and board authorisation. The TSP’s compliance team verifies your sectoral regulator status either directly or through the regulator’s public-facing database. Specifically, the DoT Press Release of 30 May 2024 imposes a positive verification obligation on TSPs. They cannot allocate a 160 series number without independently confirming your eligibility. Consequently, do not expect instant processing; the TSP’s review team needs time to complete its verification workflow.

Step 4: Register Voice Call Templates on the DLT Platform

Every voice script your 1601 number will carry must be pre-registered as a DLT content template with a unique Template ID. This includes OTP delivery, EMI reminders, loan disbursement alerts, insurance renewal notices, and collections follow-ups. That Template ID must also appear in the call signalling at the moment of each outgoing call. Calling with an unregistered, outdated, or blacklisted template is a separate violation, even if the originating number is validly allocated.

Furthermore, as of 1 October 2024, TRAI requires all variables in DLT templates to be pre-tagged to their specific purpose. For example: {OTP}, {amount}, {date}, {customer_name}. Generic untagged variables are no longer accepted. Each template must also match the category of its registered Header: transactional templates cannot include promotional content. During the initial 2021 DLT rollout for SMS, around 40% of all traffic was dropped because entities had not pre-registered their templates (TALK-Q, 2025). Some banks saw OTP failure rates above 25%. Voice template registration under the 160 series carries the same risk of service disruption if preparation is inadequate.

Step 5: Apply for 160 Series Number Allocation

Once DLT registration is active and templates are approved, formally apply to the TSP for allocation of a 1601xxxxxxx number. The TSP confirms the applicable sub-prefix — 1601 for all RBI, SEBI, IRDAI, PFRDA entities. It then allocates the number and configures the Caller Line Identification (CLI) presentation. Specifically, the 1601 number — not any underlying SIP trunk number — must appear on the recipient’s handset for every outbound call.

Step 6: Execute the TCCCPR Undertaking

At the point of allocation, your entity must sign a formal undertaking to the TSP. Specifically, the undertaking confirms that the 160 series number will be used only for service and transactional calls under TCCCPR, 2018. This undertaking is contractual and has direct legal consequence. Specifically, sending even one promotional call from a 160 series number breaches the undertaking. It also independently triggers TCCCPR penalty provisions. Therefore, have your legal team review the TSP’s draft undertaking before signing — the wording matters.

Step 7: Integrate Into Your Calling Infrastructure

After allocation, configure the 1601 number as the outbound CLI in your dialer, EPABX, IVR, or cloud telephony platform. Additionally, test CLI presentation across all major telecom circles — Airtel, Jio, Vodafone Idea, and BSNL — before going live. Also enforce technical segregation from any 140 promotional traffic. Log all CDRs with Template ID mapping from day one.

What this means for your compliance team: Steps 2 through 5 are technically sequential but can run partially in parallel with specialist support. FreJun manages DLT registration, template registration, TSP coordination, and CLI configuration simultaneously, reducing total onboarding time from eight weeks (self-managed) to approximately two weeks.

DLT Registration: The Non-Negotiable First Step

DLT registration is the one step no entity can work around. Without it, no TSP will process a 160 series number request. Understanding how the DLT system works — and where entities consistently get it wrong — saves significant time and prevents avoidable compliance failures.

How to Choose Your DLT Platform

Register on the DLT platform of the TSP you intend to use as your primary service provider for 160 series calls. Notably, the first registration costs ₹5,900 inclusive of GST. Subsequent registrations on other TSP portals are free. In practice, most BFSI entities start with their existing TSP relationship, then extend to secondary providers as calling volume grows.

Critically, Importantly, DLT registration is entity-level, not number-level. Once your entity holds a PE registration, you can add multiple 160 series numbers, headers, and templates under the same entity record. This design also means future growth is simple. If your entity adds a collections line alongside an OTP line, you add templates to the same PE record. Additionally, no re-registration of the entity is needed.

The Template Inventory: Where Most Entities Lose Time

Template registration is consistently the most time-consuming phase of the DLT process for BFSI entities. A typical commercial bank runs 30 to 60 distinct voice scripts. These cover retail loans, credit cards, savings accounts, fixed deposits, insurance co-branded products, and collections. Each script requires its own registered template with a unique Template ID and correctly tagged variables. Therefore, map all templates before beginning the DLT process — not after. This is the single most effective preparation step any compliance team can take.

Moreover, each template must contain the brand name in the content field, per DLT guidelines. Templates also cannot contain more than 30% variable content relative to total message length. Consecutive untagged variables are rejected. Each template category — transactional or service — must match the category of its registered Header. Getting these rules wrong triggers rejection, which resets the template review clock. In practice, first-time BFSI DLT registrants take two to three weeks longer than experienced ones. They discover the tagging and category constraints mid-process rather than anticipating them.

What this means for your compliance team: Before contacting any TSP or portal, assign one team member to audit all current outbound voice scripts, classify each as transactional or service, identify all variable fields, and tag each variable to its purpose. This internal preparation step costs no money and compresses the entire DLT timeline by two to four weeks.

How to Choose the Right TSP for 160 Series Allocation

Not all TSPs process 160 series allocations at the same speed or with equal BFSI compliance expertise. Selecting the wrong TSP is a costly mistake. Switching providers mid-process resets the eligibility verification timeline entirely. Therefore, evaluate TSPs against the three criteria below before making any commitment.

Criterion 1: Verify UL or UL-VNO Licence Status

First, confirm that your TSP holds a valid Unified Licence (UL) or UL-VNO authorisation from DoT. Verify this independently through the SARAL SANCHAR portal (saralsanchar.gov.in) or the DoT eServices page at eservices.dot.gov.in. Do not accept self-certification. A TSP without a valid UL cannot legally allocate 160 series numbers, and any number it purports to allocate would be invalid. Additionally, any CPaaS platform recommending itself for 160 series allocation should hold a valid VNO authorisation. Verify this before signing any service agreement.

Criterion 2: BFSI Onboarding Experience

Second, assess whether the TSP has previously onboarded BFSI entities for 160 series migration. This matters because the verification process is sector-specific. Verifying an NBFC certificate differs from verifying an IRDAI licence or a SEBI intermediary registration. TSPs with prior BFSI experience have established verification checklists and know which regulatory databases to cross-reference. Consequently, experienced TSPs resolve queries in hours; inexperienced ones take days, during which your application sits idle.

Criterion 3: Integration Capability With Your Existing Stack

Third, evaluate whether the TSP or its cloud telephony partner supports integration with your existing CRM and dialer. The 160 series number must be configured as the outbound CLI within your CRM’s calling module. Furthermore, Call Detail Records must be logged and retained with Template ID mapping for regulatory audit purposes. Platforms like FreJun integrate natively with HubSpot, Zoho CRM, Salesforce, and LeadSquared. CDR logging and Template ID mapping come built in as default features. Therefore, no separate middleware or manual logging is required.

What this means for your compliance team: Issue a short written questionnaire to any TSP you are evaluating: “Do you hold a valid UL or UL-VNO?” “How many BFSI entities have you onboarded for 160 series allocation?” “Does your platform support direct CRM integration and CDR export?” A TSP that cannot answer all three questions clearly is not the right provider for a regulated BFSI entity.

Documents Required for the 160 Series Application

The document set for a 160 series number application covers three layers: entity identification, regulatory eligibility, and formal authorisation. Having all documents ready before initiating DLT registration prevents the most common delay. Specifically, mismatched entity names and missing board resolutions are the two most frequent mid-process blockers.

Layer 1: Entity Identification Documents

• PAN Card — Company PAN, mandatory for all entity types
• Certificate of Incorporation — issued by the Registrar of Companies under the Companies Act, 2013
GST Registration Certificate — must be current and match the legal entity name precisely
• Memorandum and Articles of Association (MOA/AOA) — for companies incorporated under the Companies Act
• Authorised Signatory KYC — PAN and Aadhaar of the designated signatory for the DLT application

Layer 2: Regulatory Eligibility Documents

• RBI Certificate of Registration (for NBFCs) or Banking Licence (for banks) — must be current and unrevoked
• SEBI Registration Certificate (for AMCs, QSBs, or other registered intermediaries)
• IRDAI Licence (for life, general, or health insurers and brokers)
• PFRDA Registration (for CRAs, PFMs, and PoPs)
• Latest regulatory compliance acknowledgement, annual return, or fit-and-proper certificate from the applicable regulator

Layer 3: Authorisation and Undertaking Documents

• Board Resolution authorising the 160 series number application and naming the authorised signatory
• Letter of Authorisation in the TSP’s prescribed format, signed by the authorised signatory
• TCCCPR Undertaking — the TSP provides the draft; your legal team must review the wording before any director or authorised signatory signs

One consistency rule applies across all documents. The legal entity name on the PAN must exactly match the name on the regulatory registration, which must also match the DLT application. Even minor formatting differences — “&” versus “and”, “Limited” versus “Ltd” — trigger verification failure. Resolve all name discrepancies before submission, not after.

What this means for your compliance team: Assign one team member to assemble, cross-check, and certify this document set before any external application starts. A 30-minute internal document audit prevents a two-week external delay.

Realistic Timeline: How Long Does the Full Process Take?

The total 160 series number application timeline depends on one factor above all others: how well-prepared your entity is before it contacts any external party. Below is a stage-by-stage breakdown based on TRAI’s published direction guidelines and typical BFSI onboarding experience.

Stage	Activity	If Prepared	If Unprepared
1	Document assembly and internal audit	2–3 working days	5–10 working days
2	DLT Principal Entity registration (TSP review)	Up to 7 working days	Up to 7 working days
3	Header (Sender ID) assignment after PE approval	Up to 2 working days	Up to 2 working days
4	Voice template inventory, tagging, and submission	5–7 working days	15–25 working days
5	160 series number allocation by TSP	3–7 working days	3–7 working days
6	Technical CLI configuration and cross-circle testing	3–5 working days	5–10 working days
Total	Full process	2–4 weeks	6–10 weeks

Why Template Preparation Dominates the Timeline

In my practice advising telecom-sector clients, template preparation consistently accounts for the largest share of delay in 160 series onboarding. A typical commercial bank runs 30 to 60 voice scripts. A large NBFC typically runs 15 to 25. Each script requires a separately submitted, reviewed, and approved DLT template. Additionally, rejection of even one template requires correction and resubmission, resetting that template’s review clock. Therefore, entities that conduct a thorough internal template inventory before approaching the DLT portal complete Stage 4 in 5 to 7 working days. Without that preparation, the same stage takes three to five weeks.

Furthermore, template preparation requires no external contact, no portal access, and no fees. It is entirely an internal activity. Consequently, it can begin today, regardless of where your entity is in the DLT or TSP process. Starting template preparation now, in parallel with document assembly, is the highest-value action available. It accelerates onboarding without incurring any external cost.

What this means for your compliance team: Compress your total timeline by starting Stages 1 and 4 simultaneously. Assign one person to document assembly and another to template inventory today. The two tracks converge at the DLT submission step. Running them in parallel cuts total elapsed time by up to 50%.

Integrating Your 160 Series Number Into Your Calling Infrastructure

Number allocation is not the finish line — it is the start of the technical integration phase. This section explains the key integration requirements. It also covers what TRAI mandates at the architecture level for 160 series service calls.

CLI Presentation and Anti-Spoofing

Under Section 42 of the Telecommunications Act, 2023, and TRAI’s TCCCPR, the CLI on every outbound call must be the actual allocated 160 series number. Notably, no exceptions apply. No masking, no overlay, and no virtual number routing over the 1601 number is permitted. Additionally, DoT’s Calling Name Presentation (CNAP) framework requires accurate caller identity disclosure. The consumer sees both the 1601 number and the entity name on their handset. Therefore, if your entity uses a SIP trunk or PRI line from a cloud telephony provider, specify this requirement explicitly. The provider must route outbound calls with the 1601 number as the CLI, not their own network CLI. Specify this requirement explicitly in your service agreement and validate it during testing.

Mandatory Routing Segregation: 160 and 140 Cannot Share a Trunk

TRAI’s Cross-Use and Segregation requirement is unambiguous. The same dialer instance cannot route both 140 promotional traffic and 1601 service traffic through the same number pool. The segregation must be enforced at the technical routing level, not merely stated in a written policy. Auditors and regulators have consistently held that a written compliance policy without enforced routing logic is insufficient. Consequently, if your entity runs both promotional and transactional calling, these must use separate dialer instances or SIP trunks. Physical or logical separation is required — a written policy alone is not sufficient.

CRM Integration and CDR Logging

Most BFSI entities manage outbound service calls through a CRM — HubSpot, Zoho CRM, Salesforce, or LeadSquared are the most common in India. The 1601 number must be configured as the outbound CLI within the CRM’s calling module. Furthermore, TRAI and sectoral regulators require full Call Detail Records (CDRs). Each CDR must map to the Template ID invoked and the consent record applicable to that call. Under the Digital Personal Data Protection Act, 2023, the entity acts as a Data Fiduciary. Furthermore, it must demonstrate lawful basis, purpose limitation, and retention controls to the Data Protection Board on demand.

In practice, maintaining these records manually is unsustainable at BFSI call volumes. Therefore, use a platform that logs CDRs, template IDs, and consent data automatically with each call event. FreJun’s platform natively integrates with all four major CRMs and generates compliant CDR export reports for regulatory inspection.

Cross-Circle CLI Testing: A Step Most Entities Skip

Before going live, test CLI presentation across all major telecom circles: Airtel, Jio, Vodafone Idea, and BSNL. A call that displays the correct 1601 CLI on Airtel may show an unknown number on Jio if the SIP routing is misconfigured. This is a compliance failure, not a cosmetic issue. This is not a cosmetic problem — it is a compliance failure under TRAI’s anti-spoofing rules. Additionally, test inbound connectivity: your 1601 number must be reachable for customers who call back after receiving a service call. Missing inbound routing on a 160 series number generates customer complaints. It also undermines the trust the series was designed to build.

What this means for your compliance team: Integration and testing is the stage where specialist support pays the greatest dividend. DIY integration typically takes five to ten working days and carries high risk of CLI misconfiguration. A managed migration through a platform like FreJun completes this stage in three to five working days with cross-circle validation included.

Compliance Obligations After Allocation

Receiving a 1601 number opens a continuous compliance obligation. The following rules apply for the entire period your entity holds the number. Treat them as standing operating requirements, not one-time setup tasks.

Purpose Restriction: Service and Transactional Calls Only

Moreover, the 1601 number carries a hard purpose restriction. It may only originate service and transactional calls. Specifically, a transactional call must be made within 30 minutes of the customer-initiated event that triggered it. Examples include an OTP request, a transaction confirmation, or a loan application submission. Any call made more than 30 minutes after the trigger event is treated as a service call and requires documented consent. Moreover, promotional calls — product pitches, upselling, cross-selling — must never originate from a 160 series number. They belong exclusively on 140 series numbers with their own consent stack.

Consent Management Under the 2025 Amendment

The TCCCPR Second Amendment of 12 February 2025 (trai.gov.in) significantly tightened the consent regime. Implicit consent for transactional or service calls is valid only for the duration of the underlying contractual relationship. Explicit consent where no continuing contractual relationship exists is valid for only 7 days from the date of grant. Once a customer opts out, your entity cannot contact them again for the same stated purpose for 90 days. All consent records must be captured and stored on the DLT platform’s Digital Consent Acquisition (DCA) framework. These obligations also intersect with Section 7 of the Digital Personal Data Protection Act, 2023. That section requires a documented lawful basis for every data-processing event — including the act of making a call.

Collection Call Hours: RBI Fair Practices Code

The RBI Fair Practices Code restricts outbound collection and recovery contact to 08:00 to 19:00 IST. This restriction applies regardless of which number series originates the call. No collection or recovery call may originate outside this window, regardless of which number series it uses. Therefore, your dialer must enforce this window at the system level, not merely as a policy instruction to agents. Additionally, use of auto-dialers and robo-calls must be disclosed at the start of each call, per the 2025 TCCCPR Amendment.

Recovery Agent Obligations

If your entity uses third-party recovery agencies, those agents must use your entity’s allocated 1601 number for all calls. They cannot use numbers from their own pool. Furthermore, individual recovery agents must hold a valid IIBF certification after completing the prescribed 100-hour training programme. Your entity must maintain a board-approved Code of Conduct for recovery agents. Vicarious liability under TCCCPR and the RBI Fair Practices Code remains non-delegable. Non-compliance by an agent counts as non-compliance by your entity directly.

Record-Keeping and Audit Trail

Additionally, your entity must retain full CDRs, Template IDs, consent records, call recordings (where applicable), and complaint logs. Furthermore, all records must be in auditable form. Retention periods are set by your TSP’s licence conditions and by your sectoral regulator — whichever prescribes the longer period applies. Under the DPDP Act, 2023, your entity must also demonstrate purpose limitation and retention controls. The Data Protection Board can request this evidence at any time. Quarterly internal compliance audits are the most cost-effective way to catch violations early. Review CDRs for calls outside the 30-minute transactional window, calls outside permitted hours, and calls without registered Template IDs. Catching these issues internally costs nothing. For the complete penalty framework that applies post-deadline, read our detailed article on TCCCPR 2018 compliance and the comparison of 160 series versus 140 series obligations.

What this means for your compliance team: Build compliance audits into your quarterly operating calendar. Catching a Template ID mismatch or an out-of-hours call internally costs nothing. The same violation found by a regulator costs a minimum of ₹2,00,000 for the first instance. Third and subsequent instances cost up to ₹10,00,000 each.

Your entity’s compliance deadline has passed. The fastest path back to a clean regulatory position is a managed migration, not a self-managed one. Book a call with FreJun’s team to map your current infrastructure, identify your exposure, and set a live date within two weeks.

Book a Call

How FreJun Handles 160 Series Provisioning End-to-End

FreJun is India’s cloud telephony platform built specifically for BFSI compliance. For banks, NBFCs, fintechs, insurers, and pension entities, FreJun manages the entire 160 series provisioning and integration chain. Consequently, your legal and compliance team focuses on substantive regulatory obligations rather than technical plumbing.

What FreJun Covers

• DLT registration support — FreJun guides your entity through Principal Entity registration on the applicable TSP DLT platform, with pre-verified document checklists for each regulated entity type (RBI, SEBI, IRDAI, PFRDA).
• Template inventory and registration — FreJun’s compliance team assists with mapping, classifying, tagging, and submitting all voice templates, including full compliance with TRAI’s variable tagging rules effective 1 October 2024.
• TSP coordination and number allocation — FreJun coordinates directly with TSP partners to process the 160 series number allocation request, following up on eligibility verification on your behalf.
• CLI configuration and cross-circle testing — FreJun configures outbound CLI presentation on its platform so your 1601 number appears correctly across all telecom circles, then runs validation tests before go-live.
• CRM integration — FreJun integrates natively with HubSpot, Zoho CRM, Salesforce, and LeadSquared, ensuring the 1601 number is the outbound CLI in every CRM-triggered call without middleware.
• CDR logging and audit trail — FreJun logs full Call Detail Records with Template ID mapping, consent record linkage, and exportable audit reports designed for TSP licence compliance and sectoral regulator inspection.
• Routing segregation — FreJun enforces technical separation between 140 promotional trunks and 1601 service trunks at the platform architecture level, satisfying TRAI’s cross-use prohibition by design rather than policy.

FreJun is not a Telecom Service Provider. It does not provide legal advice. FreJun is the technical compliance layer between your entity and your TSP. It handles the operational complexity of migration and ongoing calling. Your regulatory team focuses on governance, not infrastructure. The result is a faster, lower-risk path to 160 series compliance. The compliance architecture is embedded in the platform from day one.

Frequently Asked Questions

How do I get a 160 series number in India as an NBFC?

An NBFC must first register as a Principal Entity on a TSP’s DLT platform. It submits its RBI Certificate of Registration, PAN, GST certificate, and board resolution. After DLT approval, the entity submits eligibility documents to the TSP. It registers all voice templates with correct variable tagging and applies for 1601 number allocation. The TSP allocates the number after independently verifying RBI registration status. Total time with adequate preparation: two to four weeks.

What is the difference between a 160 series number and a 140 series number?

Specifically, the 140 series is strictly for promotional and telemarketing calls. The 160 series — specifically 1601xxxxxxx for financial entities — is strictly for service and transactional calls only. These two series are legally non-interchangeable under TCCCPR, 2018. A BFSI entity that uses a 140 number for collections violates TCCCPR independently. Using a 160 number for a product pitch is an equally separate violation. Both risk disconnection of all telecom resources for up to one year.

What penalties apply if a bank or NBFC misses the 160 series deadline?

An entity continuing to use 10-digit numbers for service or transactional calls after its deadline is classified as an Unregistered Telemarketer. First violation: warning. Second violation: 20-call-per-day usage cap for six months. Third violation: disconnection of all telecom resources for up to one year across all TSPs. Financial disincentives under TCCCPR apply separately: ₹2,00,000 for the first instance, ₹5,00,000 for the second, ₹10,00,000 for third and subsequent instances. Sectoral regulators can also act independently.

Can a recovery agency or BPO apply for a 160 series number?

No. The 1601 number is allocated exclusively to the Principal Entity — the regulated BFSI entity itself. Recovery agencies and BPOs make service calls using the PE’s allocated 1601 number, not a number held in their own name. The Principal Entity is vicariously liable under TCCCPR and the RBI Fair Practices Code for every agent call. Indeed, this liability exists regardless of direct supervision.

How long does DLT registration take for a 160 series application?

Per TRAI’s direction, DLT Principal Entity registration takes a maximum of 7 working days from submission of all required information. Header assignment after PE approval takes a maximum of 2 additional working days. Voice template registration varies by template count. A well-prepared entity completes this in 5 to 7 working days. An unprepared entity may take three to five weeks. Total DLT-side process with preparation: 10 to 16 working days.

Do small NBFCs and co-operative banks also need to migrate to the 160 series?

Yes. TRAI Direction PRID 2191647 (19 November 2025) covers all RBI-regulated entities, including remaining NBFCs, co-operative banks, and regional rural banks, with a mandatory deadline of 1 March 2026. That deadline has now passed. Any entity in this category still using standard 10-digit numbers for service or transactional calls is in breach and faces the full Unregistered Telemarketer enforcement sequence, including potential one-year disconnection of all telecom resources.

Is a call from a 1601 number safe to answer?

Yes. A call from 1601xxxxxxx is a legitimate service or transactional call. A TSP has verified and registered the originating BFSI entity under the 160 series mandate. The TSP has confirmed the entity’s RBI, SEBI, IRDAI, or PFRDA registration before allocating the number. By contrast, treat a standard 10-digit mobile number claiming to be from a bank with caution. Regulated financial institutions now use 1601 numbers for all service communications.

How many entities have adopted the 1600 series so far?

As of December 2025, approximately 570 entities had adopted 1600 series numbers. Together they subscribed to more than 3,000 numbers, per TRAI Direction PRID 2205350 (16 December 2025). Before the December Direction, the figure stood at 485 entities and over 2,800 numbers as of November 2025. These numbers reflect voluntary and early-compliance adopters. The full mandatory migration across all BFSI categories was still in progress at that point.

Key Takeaways

• Getting a 160 series number in India is mandatory for all regulated BFSI entities — all phase-wise deadlines under TRAI Direction PRID 2191647 and PRID 2205350 have now passed.
• The process runs in seven sequential steps: confirm eligibility, register on DLT, submit TSP documents, register voice templates, apply for allocation, execute the TCCCPR undertaking, and integrate into your infrastructure.
• DLT Principal Entity registration is the unavoidable gateway step — no TSP will process a 160 series request without it. The one-time fee is ₹5,900.
• Template inventory preparation is the highest-leverage internal action any compliance team can take today. A thorough template audit compresses total onboarding time by up to four weeks at zero cost.
• 570 entities had already adopted the 1600 series by December 2025, subscribing to 3,000+ numbers. Entities still outside the mandate now face active enforcement risk, not just future deadline pressure.
• Compliance obligations continue after allocation: the 30-minute transactional call window, 08:00 to 19:00 IST collection hours, 7-day explicit consent validity, 90-day opt-out lockout, and quarterly CDR audits must all be built into operating practice.
• FreJun manages the complete provisioning chain — DLT registration, template registration, TSP coordination, CLI configuration, CRM integration, and CDR logging — for banks and NBFCs that want a managed migration rather than a DIY process.

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 (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/tcccpr
• SARAL SANCHAR Portal — saralsanchar.gov.in
• RBI IT Outsourcing Master Direction, 10 Apr 2023 — rbi.org.in
• DPDP Act, 2023 — meity.gov.in
• S.S. Rana & Co. on TRAI Spam Crackdown — ssrana.in (March 2026)
• GASA: How India Cut Spoofed Fraud Calls by 90% — gasa.org (May 2025)
• TALK-Q India SMS Regulation Guide 2026 — talk-q.com
• TRAI DLT Government Entities Page — trai.gov.in