Setup guide for BFSI entities to provision 160-series numbers for transactional voice communications in India.
Legal disclaimer: This document is for informational purposes only and does not constitute legal advice. Regulatory requirements for 160-series numbers are governed by the Department of Telecommunications (DoT) and the Telecom Regulatory Authority of India (TRAI). You are responsible for ensuring compliance with all applicable laws and regulations, which may change.
Overview
160-series numbers are ten-digit telephone numbers designated by the Indian Department of Telecommunications for service-related and transactional voice communications. These numbers are subject to strict regulatory oversight by TRAI and are exclusively for service and transactional calls.
Permitted Use Cases
160-series numbers are for transactional or service-related communication only. Do not use them for marketing or promotional purposes.
Acceptable use cases:
- Payment reminders and transaction notifications
- Account statements and balance updates
- Service alerts and system notifications related to subscribed services
Eligibility
160-series numbers are exclusively allocated to BFSI (Banking, Financial Services, and Insurance) entities regulated by the following authorities:
| Regulatory Body | Examples |
|---|
| Reserve Bank of India (RBI) | Commercial banks, cooperative banks, NBFCs |
| Securities and Exchange Board of India (SEBI) | Stock brokers, investment advisors, mutual funds |
| Insurance Regulatory and Development Authority of India (IRDAI) | Life insurance, general insurance, health insurance providers |
| Pension Fund Regulatory and Development Authority (PFRDA) | Pension fund managers, National Pension System intermediaries |
Prerequisites
Before provisioning 160-series numbers, ensure you have:
| Requirement | Details |
|---|
| Plivo account | Active Plivo India account |
| Compliance documents | Approved India compliance documents (Certificate of Incorporation and GST Certificate) |
| Regulatory certificate | Business category certificate issued by applicable regulatory body (RBI, SEBI, IRDAI, or PFRDA) |
| DLT registration | Principal Entity registered on Tata DLT portal (Plivo has partnered with Tata; entities on other DLT platforms are not supported) |
Provisioning Process
All processes outlined below must be completed by the BFSI entity.
Step 1: DLT Portal Registration
Register as a Principal Entity (PE) on the Tata Teleservices DLT portal. This establishes your organization as the authorized entity responsible for all voice communications through allocated 160-series numbers.
After successful registration and approval, a Principal Entity Certificate is issued to your registered email address.
Step 2: Number Allocation
Required Documentation
Submit the following documents to Plivo:
- Principal Entity Certificate (issued by Tata Teleservices)
- Approved India Compliance Application Alias
- Voice Header Registration Declaration (filled and signed)
Plivo’s Allocation Process
Upon receipt of these documents, Plivo will:
- Reserve 160-series numbers to your account
- Provide Plivo’s Telemarketer ID (TM ID)
- Issue a No Objection Certificate (NOC) letter linking the allocated numbers to your PE ID
Register the Voice Header on the Tata DLT portal using the allocated 160-series number under your Principal Entity ID. During registration, select Plivo’s Telemarketer ID as provided in Step 2.
Required Documents for Upload
- Business category certificate from regulatory body (RBI, SEBI, IRDAI, or PFRDA)
- No Objection Certificate (NOC) letter issued by Plivo
Step 4: URN Submission to Plivo
After submitting the Voice Header registration, provide the following to Plivo:
| Required Item | Description |
|---|
| URN | Unique Registration Number (also called Submission ID) |
| Screenshot | Completed submission from DLT portal |
Plivo Review and Approval
Plivo reviews the header registration for completeness and accuracy, then coordinates with Tata by sharing the URN and allocated 160-series number for final regulatory approval.
Step 5: Content Template Registration
After Plivo confirms that the voice header has been approved by Tata Teleservices, register the Voice Content Template on the DLT portal. These templates define the specific messages transmitted using the 160-series number.
Once template registration is complete, the 160-series number is ready for live operations.
Process Overview
Step 1: BFSI Entity
└─ Register as PE on Tata DLT Portal
└─ Receive PE Certificate
Step 2: Plivo
└─ Submit PE Certificate + Compliance Docs
└─ Receive: Reserved Numbers + TM ID + NOC Letter
Step 3: BFSI Entity
└─ Register Voice Header on Tata DLT Portal
└─ Upload Regulatory Certificate + NOC
└─ Select Plivo's TM ID
Step 4: Plivo
└─ Submit URN + Screenshot
└─ Plivo coordinates with Tata for approval
Step 5: BFSI Entity
└─ Register Content Template on DLT Portal
└─ Number ready for live operations
Estimated Timelines
| Step | Duration |
|---|
| DLT registration | 2–3 business days |
| Plivo number allocation | 1–2 business days after document submission |
| Voice Header approval | 3–5 business days |
| Content Template registration | 1–2 business days |
| Total | ~7–14 business days |
Best Practices
- Maintain compliance documentation — Keep all documents (PE Certificate, NOC, regulatory certificates) in a secure, accessible location for audits.
- Monitor DLT portal status — Regularly check the Tata DLT portal for updates, renewal requirements, or compliance notifications.
- Test before go-live — Conduct thorough testing of voice templates and call flows before deploying to production.
- Stay updated on regulations — Monitor TRAI and DoT announcements for changes to 160-series number regulations.
Compliance Checklist
FAQs
No. 160-series numbers are strictly for transactional and service-related communications only. Using them for promotional or marketing purposes violates TRAI regulations and may result in number disconnection and penalties.
Plivo has partnered exclusively with Tata for 160-series provisioning. Entities registered on other DLT platforms (such as Airtel, Vi, or BSNL) are not supported. You need to register as a Principal Entity on the Tata DLT portal.
You receive notification via the DLT portal with the reason for rejection. Common reasons include:
- Incomplete or incorrect documentation
- Mismatch between PE details and submitted documents
- Invalid NOC or regulatory certificate
Review the rejection reason, correct the issue, and resubmit the registration.
Do I need to renew my 160-series numbers?
Yes. Maintain active registration on the Tata DLT portal and ensure all compliance documents remain current. Check with Tata regarding renewal timelines for Principal Entity registration and content templates.
