160 Series OTP EMI Calls: Which Number Series for OTP, EMI, and Collections in India?

Key Facts at a Glance

Item	Detail
Regulation	TCCCPR, 2018 (Second Amendment, 12 Feb 2025)
Governing body	TRAI / DoT
Applies to	Banks, NBFCs, fintechs, insurers, BPOs, recovery agencies making 160 series OTP EMI calls or collection follow-ups
Correct number series	160xxxxxxx for service/transactional; 1601xxxxxxx for RBI/SEBI/PFRDA/IRDAI-regulated entities
First-violation penalty	₹2,00,000
Blacklist trigger	5 valid complaints in any rolling 10-day period
Deadline status	Phase-wise; Mutual Funds and AMCs by 15 Feb 2026; Qualified Stockbrokers by 15 Mar 2026
Transactional call window	Within 30 minutes of the customer-initiated event

• OTP calls, EMI reminders, and collection follow-ups are service or transactional calls. All three must travel on the 160 series, not the 140 series.
• The 140 series is strictly for promotional and telemarketing calls. Routing 160 series OTP EMI calls through 140 numbers violates TCCCPR and triggers financial penalties.
• BFSI entities regulated by RBI, SEBI, PFRDA, or IRDAI must use the 1601xxxxxxx sub-prefix specifically.
• Every call type needs a pre-registered DLT content template. Calling without a valid template ID is a standalone TCCCPR violation.
• Recovery agents must call using the Principal Entity’s 1601 number. The Principal Entity carries vicarious liability for all agent conduct.
• TRAI’s blacklist power covers up to 1 year across all telecom resources, making non-compliance operationally catastrophic for any BFSI entity.

In this article:

• Key Facts at a Glance
• Quick Answer
• 160 Series OTP EMI Calls: Which Number Series Applies?
• EMI Reminders on the 160 Series: What the Rules Say
• Collection Follow-Ups: 160 or 140 Series?
• 160 Series vs 140 Series: The Core Difference
• DLT Template Registration for Every Call Script
• Recovery Agents: Which Number Must They Use?
• Penalties for Using the Wrong Series
• How FreJun Routes 160 Series OTP EMI Calls Correctly
• Frequently Asked Questions
• Key Takeaways

Quick Answer: 160 Series OTP EMI Calls vs 140 Series

Quick Answer: OTP calls, EMI reminders, and collection follow-ups are service or transactional calls under TCCCPR, 2018. All three must use the 160 series, specifically the 1601 sub-prefix for RBI, SEBI, PFRDA, and IRDAI-regulated entities. The 140 series is reserved for promotional and telemarketing calls only. Routing any of these three call types through 140 numbers is a direct TCCCPR violation.

In practice, compliance teams at banks, NBFCs, fintechs, and BPOs regularly ask whether 160 series OTP EMI calls and collection follow-ups require the 160 series or the 140 series. Specifically, the answer depends entirely on the purpose of the call, not the technology or the sector. This guide maps all three call types to the correct number series, explains the regulatory logic behind each assignment, and shows what happens when entities route service calls through the wrong pool.

Get Legal Guidance

Unsure which number series applies to your specific OTP, EMI, or collection call workflow? FreJun’s compliance team maps each call type to the correct series and handles DLT registration from end to end.

160 Series OTP EMI Calls: Which Number Series Applies?

Specifically, OTP delivery calls must use the 160 series, specifically the 1601 sub-prefix for BFSI entities. DoT’s 30 May 2024 direction (PRID 2022249) created the 160xxxxxxx series exclusively for service and transactional voice calls. An OTP call is a transactional call, triggered within seconds of a customer-initiated login or payment event, and therefore belongs on this series without exception.

Why the 140 Series Is Wrong for OTP Delivery

The 140 series carries a deep consumer association with promotional traffic. Industry reports indicate roughly 147 million spam complaints originated in India in 2024, and a significant share came from 140 numbers. Consumers habitually reject calls from 140 numbers, so routing 160 series OTP EMI calls through 140 numbers fails at two levels: the call likely never reaches the customer, and it violates TCCCPR, 2018 by sending a transactional call through a promotional series.

Furthermore, TCCCPR’s Second Amendment of 12 February 2025 tightened the transactional call window to within 30 minutes of the triggering customer event. An OTP call made after that window reclassifies as a service call and requires the corresponding consent stack. In practice, your dialer must fire the OTP call immediately and never queue it beyond 30 minutes.

The 1601 Sub-Prefix: Who Must Use It for OTP Calls?

Notably, financial entities regulated by RBI, SEBI, PFRDA, and IRDAI must use the 1601xxxxxxx sub-prefix, as DoT’s press release directed. This sub-prefix signals to the consumer that the call originates from a verified, regulated financial institution. For instance, banks making OTP calls, NBFCs sending account-alert calls, and insurers confirming policy activations all fall within this requirement. Entities outside the BFSI sector may use the broader 160 series, but every BFSI entity must use the 1601 designation specifically.

What this means for your compliance team: Audit your current OTP delivery channel today. Specifically, if your dialer routes calls through a 140 number or a standard 10-digit mobile number, that is a live compliance violation. Therefore, migration to a 1601 number, including TSP verification and DLT template registration, must complete before any further OTP calls go out on the old channel.

EMI Reminders on the 160 Series: What the Rules Say

Importantly, EMI reminder calls are service calls under TCCCPR, 2018, and they must use the 160 series. They are not promotional, because they relate to a contractual obligation the customer has already accepted. They are not purely transactional either, because the customer did not initiate a specific event within the 30-minute window. Consequently, they fall squarely in the service category that the DoT created the 160 series to accommodate.

Defining the Boundary: Service vs Transactional for EMI Calls

The TCCCPR defines a transactional call as one made within 30 minutes of a customer-initiated event. Specifically, an EMI reminder is bank-initiated. In other words, the bank decides when to call; the customer has not pressed any trigger. Therefore, this distinction makes EMI reminders service calls, not transactional ones. Consequently, service calls require consent that aligns with the underlying contract, and that consent remains valid for the duration of the lending arrangement. Once the loan closes, however, the implicit consent lapses automatically.

Additionally, the RBI Fair Practices Code restricts outbound recovery and collection contact to 08:00 to 19:00 IST only. This restriction applies directly to EMI reminder calls, so platforms must configure time-gates accordingly. Calling outside those hours, even from a correctly assigned 1601 number, therefore creates a separate RBI violation. Therefore, most EMI reminder platforms must enforce a hard time-gate at the dialer level, not merely at the policy level.

Consent Rules for EMI Reminder Calls on the 160 Series

TCCCPR’s Second Amendment tightened consent rules considerably. Specifically for EMI calls, implicit consent from the customer’s loan agreement is valid for the duration of that contract. However, the entity must register every call script as a DLT content template before use. Specifically, the template ID must travel in the call signalling. Notably, calling with an unregistered or outdated template is a violation regardless of whether the originating 1601 number is correctly assigned.

Moreover, if a customer opts out of EMI reminder calls, the lender may not contact them again on the same purpose for 90 days from the opt-out date. The Second Amendment also prohibits soliciting fresh consent from any subscriber who has opted out within that 90-day window.

What this means for your compliance team: Confirm with your TSP that your EMI reminder dialer runs on your entity’s 1601 number pool. Verify that every EMI reminder script carries a valid, current DLT template ID. Additionally, set time-gate enforcement at 08:00 and 19:00 IST in the dialer configuration, not just in the call centre policy.

Collection Follow-Ups: 160 Series or 140 Series?

Critically, collection follow-up calls are service calls and must use the 160 series. This is one of the most misapplied rules in the BFSI industry, because collections teams often inherit 140 numbers from legacy telemarketing infrastructure. Consequently, continuing to use those 140 numbers after the 160 series took effect is a clear TCCCPR violation.

Why Collections Teams Cannot Route Calls Through 140 Numbers

The 140 series covers promotional and telemarketing calls only. A collection call, by contrast, relates directly to a specific contractual obligation. Indeed, it is not a sales pitch. Instead, it informs or reminds the borrower about an existing financial liability, which classifies it as a service call under TCCCPR. Therefore, routing a collection call through a 140 number mixes the series, violates the purpose restriction, and exposes the entity to both TRAI enforcement and RBI supervisory action simultaneously.

In my practice advising telecom-sector clients, I have consistently found that the collections compliance gap represents the largest single source of regulatory exposure for NBFCs and recovery agencies. Many assume that because the 140 series historically served all commercial calls, it continues to cover all outbound call types. However, that assumption became invalid on 30 May 2024, when DoT published PRID 2022249 and created the 160 series as a hard segregation between promotional and service traffic.

RBI Collection Call Hours and the 160 Series Requirement

The RBI Fair Practices Code restricts all outbound collection contact to 08:00 to 19:00 IST. Importantly, this rule applies regardless of the number series in use. However, running collection calls from a correctly assigned 1601 number adds a second layer of protection: the consumer can visually confirm the call originates from a regulated institution, which raises pickup rates and reduces spam flag risk.

Practically, collections teams should configure both the 1601 number routing and the 08:00-19:00 time gate as system-level constraints, not policy-level guidelines. TRAI’s blacklist trigger stands at 5 valid complaints in any rolling 10-day period. A single day of after-hours collection calls generating complaints can push an entity to the blacklist threshold rapidly.

What this means for your compliance team: If your collections team currently uses 140 numbers or standard 10-digit mobile numbers, migrate to your entity’s 1601 allocation immediately. Contact your TSP, complete the eligibility verification, register your collection call templates on DLT, and then configure time-gate enforcement at the dialer level.

160 Series vs 140 Series: The Core Difference

Ultimately, the core difference between the two series is purpose. Specifically, the 160 series covers service and transactional voice calls exclusively. The 140 series covers promotional and telemarketing calls only. Indeed, these are not interchangeable categories, and TCCCPR prohibits mixing the series for any reason.

Use Case Matrix: Which Series for Which Call Type?

Call Type	Correct Series	Why
OTP delivery	160 (1601 for BFSI)	Transactional; triggered by customer event within 30 minutes
EMI reminder	160 (1601 for BFSI)	Service call; relates to existing contractual obligation
Collection follow-up	160 (1601 for BFSI)	Service call; not promotional, relates to existing debt
Loan offer or upsell	140	Promotional; subject to DND and consent rules
Insurance premium renewal reminder	160 (1601 for IRDAI entities)	Service call; relates to existing policy
New product announcement	140	Promotional; telemarketing classification
KYC update request	160 (1601 for BFSI)	Service call; regulatory compliance obligation of the entity
Credit card activation	160 (1601 for BFSI)	Service call; relates to an account the customer holds
Cold outreach for new accounts	140	Promotional; prospecting call unrelated to existing relationship

How Consumers Identify a 160 Series Call vs a 140 Series Call

A call from 160xxxxxxx signals a legitimate service or transactional call from a verified Principal Entity. Numbers starting with 140xxxxxxx, by contrast, signal a promotional or telemarketing call, legal if registered but subject to DND opt-out. Standard 10-digit mobile numbers claiming to be from a bank or insurer should be treated as suspicious. This is precisely the fraud gap DoT sought to close when it created the 160 series in May 2024.

Additionally, TRAI’s Calling Name Presentation (CNAP) regime mandates accurate caller identity disclosure on the recipient’s handset. Post-migration, an entity’s 1601 number displays the registered entity name, giving consumers a visual trust signal that neither a 140 number nor a 10-digit mobile number can provide.

What this means for your compliance team: Review every outbound call workflow in your organisation. For each call type, ask whether it relates to an existing relationship or obligation. If yes, classify it as a service or transactional call and assign it to the 160 series. If it is outreach to a prospect or an upsell, classify it as promotional and assign it to the 140 series with the appropriate DND and consent framework in place.

DLT Template Registration for Every Call Script

Specifically, every voice script used for 160 series OTP EMI calls and collection follow-ups must be pre-registered as a content template on the Distributed Ledger Technology (DLT) platform before the first call goes out. Subsequently, the DLT platform assigns a unique Template ID. That ID must then travel with every outbound call in the signalling layer, without exception.

What Happens When You Call Without a Valid DLT Template ID?

Calling without a valid, current DLT template ID violates TCCCPR, even when the originating number is a correctly assigned 1601 allocation. Importantly, TRAI treats this violation independently of any issue with the number itself. In practice, an entity can therefore face a penalty for using the wrong number series and a separate penalty for using an unregistered template, both arising from the same call.

Furthermore, once DLT blacklists a template, typically because it generated excessive complaints, the entity cannot reuse it even with a current registration. Instead, the entity must file a new template and wait for TSP approval before resuming those calls. For time-sensitive workflows like OTP delivery, therefore, this approval gap can disrupt customer authentication entirely.

Practical DLT Registration Timeline for 160 Series OTP EMI Calls

First-time DLT registrants typically complete the process in 2 to 3 weeks, covering three sequential steps: Principal Entity registration, Header registration, and Template registration. Each step, specifically, requires TSP verification. Therefore, entities preparing for OTP or collection call migration should build this timeline into their project plan. Starting DLT registration the week before the migration deadline is, consequently, too late and creates a compliance gap.

What this means for your compliance team: Maintain a DLT template register that lists every active template, its ID, registration date, and renewal status. Assign ownership for template review to a named team member. Moreover, schedule a quarterly calendar review to catch templates approaching expiry or flagged for complaints before DLT blacklists them.

Recovery Agents: Which Number Must They Use?

Recovery agents making collection calls on behalf of a bank or NBFC must use the Principal Entity’s 1601 number, not a number from the agency’s own pool. Indeed, this is one of the most widely misunderstood rules in the collections space, and non-compliance remains common even among large recovery operations.

Vicarious Liability: The Principal Entity Carries Full Responsibility

TCCCPR holds the Principal Entity, meaning the bank, NBFC, or insurer, vicariously liable for the conduct of its agents. However, the Principal Entity cannot disclaim responsibility by pointing to the BPO or recovery agency. Consequently, if the recovery agent calls from an incorrect number, the Principal Entity faces the penalty. Additionally, the RBI Fair Practices Code and the RBI Master Direction on Outsourcing of IT Services (10 April 2023) require the Principal Entity to maintain a board-approved Code of Conduct for recovery agents and to audit agent compliance regularly.

Individual recovery agents must also hold a valid IIBF certification obtained after the prescribed 100-hour training programme. Furthermore, deploying uncertified agents is a separate RBI compliance risk, layered on top of the TRAI number-series violation. Together, therefore, these requirements mean that a Principal Entity’s compliance exposure from a single non-compliant agent can span three separate regulatory bodies simultaneously.

Technical Segregation at the Dialer Level

The Principal Entity’s 1601 numbers must undergo technical segregation from any 140 promotional numbers in the same dialer infrastructure. Specifically, TRAI and sectoral regulators have been explicit that a written policy without enforced routing logic does not constitute adequate compliance. Therefore, the dialer must physically prevent a recovery agent from originating a call from a 140 number or a 10-digit mobile number. Additionally, configuration and audit logs should record this segregation for any regulatory inspection.

What this means for your compliance team: Provide your recovery agency partners with access to your entity’s 1601 SIP trunk or PRI allocation specifically. Audit their dialer configuration to confirm the segregation. Contractually require the agency to maintain CDRs and to make them available for your audit. Document this arrangement as part of your TCCCPR compliance record.

Penalties for Using the Wrong Series

The penalty structure for misrouting 160 series OTP EMI calls or collection follow-ups through the 140 series is multi-layered and escalates rapidly. Specifically, a single non-compliant calling pattern can simultaneously attract action under telecom law, sectoral regulation, and data protection law.

TCCCPR Financial Penalties

Under the Second Amendment, 2025, graded financial disincentives apply per instance of violation. The first violation carries a penalty of ₹2,00,000. The second violation rises to ₹5,00,000. Third and subsequent violations attract ₹10,00,000 per instance. Notably, these penalties apply separately for each violation and are in addition to any penalty for invalid complaint handling or failure to meet other TCCCPR obligations.

Service Suspension and the One-Year Blacklist

However, the operationally severe consequence is not the financial penalty. Instead, it is the disconnection power. A first violation reaching the regulatory complaint threshold results in outgoing services barred for 15 days on all the entity’s telecom resources. Subsequent violations result in complete disconnection of all telecom resources across all TSPs for up to one year, with the entity blacklisted across the entire telecom ecosystem.

For a BFSI entity, therefore, a one-year blacklist is operationally catastrophic. Specifically, OTP calls cannot go out, meaning customers cannot authenticate. Additionally, EMI reminders stop entirely. Consequently, collection calls cease. Moreover, the entity’s CRM-linked voice channels go dark. No workaround exists during the blacklist period, because it covers all telecom resources with all TSPs simultaneously.

The Blacklist Trigger: Only 5 Complaints in 10 Days

TRAI’s Second Amendment tightened the complaint threshold significantly. The blacklist trigger is now 5 valid complaints in any rolling 10-day period, reduced from the earlier threshold of 10 complaints in 7 days. Moreover, consumers can now file complaints without prior DND preference registration, which broadens the complaint intake considerably. For high-volume outbound callers like BPOs and recovery agencies, therefore, 5 complaints can accumulate in a single morning of non-compliant calling.

Sectoral Regulator Action: Independent of TRAI

Sectoral regulators act independently of TRAI. Specifically, TRAI’s action under TCCCPR does not preclude RBI from imposing supervisory action under Section 35A of the Banking Regulation Act, 1949. Similarly, SEBI may impose penalties under Section 15HB of the SEBI Act, 1992, for the same underlying non-compliance. Both can proceed in parallel with TRAI enforcement, which means a single series-misuse event can generate three separate regulatory proceedings.

What this means for your compliance team: Treat the risk of a one-year telecom blacklist as a board-level concern, not an operational matter. The cost of a single violation cycle, including operational disruption, regulatory penalties, and reputational damage, far exceeds the cost of a properly managed 160-series migration and DLT registration programme.

How FreJun Routes 160 Series OTP EMI Calls Correctly

FreJun provisions and manages 160-series and 140-series numbers for BFSI entities, fintechs, BPOs, and recovery agencies. The platform handles the full compliance stack so your legal and IT teams do not need to manage it manually or risk misconfiguration.

End-to-End 1601 Provisioning

FreJun works directly with TSPs to complete entity verification and allocate 1601 numbers to your organisation. Specifically, this covers the TSP eligibility check, the entity undertaking, and the number assignment, all through FreJun’s provisioning workflow. As a result, your team receives a configured 1601 SIP trunk or PRI allocation, ready for use on day one.

DLT Integration and Template Management for OTP, EMI, and Collection Calls

FreJun’s platform integrates directly with the DLT infrastructure. Specifically, template registration for OTP scripts, EMI reminder scripts, and collection call scripts all happens within the platform. As a result, the system attaches the correct Template ID to every outbound call automatically, eliminating the risk of calling with an unregistered or expired template. Template status undergoes real-time monitoring, with alerts before any template approaches blacklist risk.

Routing Segregation Enforced at the System Level

FreJun’s routing engine enforces hard segregation between 1601 service call traffic and 140 promotional call traffic. Specifically, the same dialer instance cannot mix the two pools. Moreover, this segregation is technical and auditable, satisfying TRAI’s requirement that compliance live in routing logic, not merely in written policy. CRM integrations with HubSpot, Zoho, Salesforce, and Leadsquared allow call workflows to trigger on the correct number pool automatically based on call type and customer record.

For more on how BFSI entities structure their overall voice compliance programme, see our BFSI Communication Compliance Guide 2026 and our detailed breakdown of 160 series vs 140 series obligations. For the complete TCCCPR regulatory framework, see our TCCCPR 2018 compliance guide.

Talk to FreJun’s Legal Team

FreJun handles 1601 provisioning, DLT template registration, and routing segregation in a single workflow. Most BFSI teams complete setup within two weeks. Book a session with the legal team to map your specific OTP, EMI, and collection call workflows to the correct number series.

Frequently Asked Questions

160 series vs 140 series: what is the fundamental difference?

The 160 series covers service and transactional voice calls exclusively, originating from verified Principal Entities. By contrast, the 140 series covers promotional and telemarketing calls only. Neither series can lawfully serve the other’s purpose. Notably, DoT created this hard segregation on 30 May 2024 through Press Release PRID 2022249, specifically so consumers could distinguish legitimate service calls from spam and fraud.

Are 160 series OTP EMI calls classified as transactional or promotional?

Specifically, OTP calls are transactional calls. A customer-initiated event such as a login or payment triggers them, and TCCCPR’s Second Amendment of 12 February 2025 requires the call to go out within 30 minutes of that event. EMI reminder calls are service calls, not transactional ones, because the bank initiates them independently of a customer action. Both call types must use the 160 series, specifically 1601xxxxxxx for BFSI entities.

What is the penalty for routing EMI reminder calls through 140 numbers?

Routing EMI reminder calls through 140 numbers violates TCCCPR, 2018 because these calls are service calls, not promotional ones. The first violation attracts a penalty of Rs 2,00,000. The second violation is Rs 5,00,000. Third and subsequent violations are Rs 10,00,000 per instance. Additionally, 5 valid complaints in any rolling 10-day period can trigger a telecom blacklist of up to one year across all TSPs.

How does a bank or NBFC apply for a 1601 number?

A BFSI entity applies for a 1601 number through a licensed Telecom Service Provider. The TSP verifies the entity’s registration with RBI, SEBI, PFRDA, or IRDAI before allocating a number. The entity must also undertake to use the number only for service and transactional calls as required by TCCCPR, 2018. DLT registration for content templates follows the number allocation. FreJun manages this provisioning process end to end.

Can recovery agents use their own phone numbers for collection calls?

No. Recovery agents must use the Principal Entity’s allocated 1601 number, not numbers from the agency’s own pool. TCCCPR and the RBI Fair Practices Code hold the Principal Entity vicariously liable for the agent’s conduct. Specifically, the correct number pool must reach the agency through a configured SIP trunk or PRI allocation. Using 10-digit mobile numbers or agency-owned 140 numbers for collection calls is a direct TCCCPR violation.

Does the 30-minute transactional call window apply to EMI reminders?

No. The 30-minute window applies to transactional calls, which a specific customer-initiated event triggers. By contrast, EMI reminders are bank-initiated service calls and do not depend on a customer event trigger. They therefore fall under the service call category. Instead, service calls require consent aligned with the underlying contract for its duration, rather than the 30-minute trigger rule that governs transactional calls.

What are the RBI timing rules for collection calls?

The RBI Fair Practices Code restricts outbound recovery and collection contact to between 08:00 hours and 19:00 hours IST only. Customer-initiated contact outside those hours is permitted; however, outbound calls from the lender or its agents are not. This restriction applies in addition to TCCCPR number-series requirements and must be enforced at the dialer configuration level, not just through internal policy guidelines.

Key Takeaways

• OTP calls, EMI reminders, and collection follow-ups are all service or transactional calls. All three must travel on the 160 series, specifically 1601 for BFSI entities regulated by RBI, SEBI, PFRDA, or IRDAI.
• The 140 series is strictly promotional. Routing 160 series OTP EMI calls or collection follow-ups through 140 numbers is a live TCCCPR violation with immediate penalty exposure.
• Every call script must have a pre-registered DLT Template ID. Template registration takes 2 to 3 weeks for first-time registrants; plan accordingly and do not start the week before any migration deadline.
• Recovery agents must use the Principal Entity’s 1601 number. TCCCPR and the RBI Fair Practices Code hold the Principal Entity vicariously liable for all agent conduct.
• 5 complaints in 10 days triggers TRAI’s blacklist power. A one-year telecom blacklist covering all resources with all TSPs is the most operationally severe enforcement tool available under TCCCPR.
• The 30-minute transactional window applies to OTP calls. EMI reminders and collection calls follow the consent-for-duration-of-contract rule instead.
• RBI limits outbound collection calls to 08:00 to 19:00 IST. Enforce this at the dialer level, not merely in written policy.

For Any Questions Reach Out to Our Legal Team

You have seen how the OTP, EMI, and collection call rules work across both series. FreJun’s legal team can walk through your specific call workflows, confirm the correct series assignment for each, and map the DLT template requirements before your next compliance audit.

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 April 2023 — rbi.org.in
• DPDP Act, 2023 — meity.gov.in

About the Author

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