Documentation Index
Fetch the complete documentation index at: https://plivo.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
- 160-series numbers are TRAI-regulated and used only for transactional and service voice calls by BFSI entities in India
- Register on Tata DLT as PE (and TM if Partner-Managed), submit the BFSI Customer Application Form and the Aggregator Telemarketer Declaration to Plivo, then complete Voice Header and Voice Template registration. ~7–14 business days total
- Using a 160-series number for promotional or marketing calls leads to number disconnection and penalties
Overview
160-series numbers are ten-digit telephone numbers designated by the Indian Department of Telecommunications for transactional and service voice communications by regulated BFSI entities.
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
- Authentication, alerts, customer support, regulatory communication, and service calls
Eligibility
160-series numbers are allocated only to BFSI (Banking, Financial Services, and Insurance) entities that hold a valid licence or registration from a recognized financial regulator. You declare the regulator and licence number on the BFSI Customer Application Form.
| Entity Type | Governing regulator | Examples |
|---|
| Bank | RBI | Commercial banks, cooperative banks, small finance banks |
| NBFC | RBI | Non-banking financial companies |
| Insurance | IRDAI | Life, general, and health insurance providers |
| Mutual Fund / Asset Manager | SEBI | Asset management companies, mutual fund distributors |
| Payment Aggregator | RBI | Payment service providers and aggregators authorized under the PA/PG framework |
| Pension Fund | PFRDA | Pension fund managers, NPS intermediaries |
| Fintech | RBI / SEBI / IRDAI (as applicable) | Regulated financial technology businesses |
| Other BFSI | Specify regulator on the form | Other regulated financial entities (specify in the BFSI Customer Application Form) |
Roles in 160-Series Provisioning
| Role | Who it is | Responsibilities |
|---|
| Access Service Provider (VNO) | Plivo | Allocates the 160-series number and issues the NOC to the TM. Plivo is neither the PE nor the TM |
| Principal Entity (PE) | The BFSI business | Holds the regulatory licence, registers as PE on Tata DLT, owns the content templates, signs the BFSI Customer Application Form |
| Telemarketer (TM) | The entity placing the call | Holds the Tata DLT TM ID, signs the Aggregator Telemarketer Declaration, approves the Voice Header in Partner-Managed setups |
Self-Managed vs Partner-Managed
There are two possibilities depending on who places the calls:
| Setup | Description | Example |
|---|
| Self-Managed | The PE and TM are the same legal entity. The BFSI business that owns the campaign also makes the calls | A bank running its own transactional alerts and OTP calls |
| Partner-Managed | The PE and TM are different entities. A third party makes calls on behalf of the BFSI business | A contact-center provider placing OTP and reminder calls on behalf of a bank |
TM registration location. Plivo currently accepts 160-series provisioning only when the TM entity is registered in Mumbai or Karnataka. Entities registered elsewhere are not supported today.
DLT operator support. Plivo currently provisions 140 and 160-series numbers exclusively through Tata Teleservices and is in the process of onboarding additional service providers. Entities registered on other DLT platforms (Airtel, Vi, BSNL) are not supported today.
Prerequisites
| Requirement | Details |
|---|
| Plivo account | Active Plivo India account |
| Regulatory licence | Valid licence or registration number from your governing regulator (RBI, SEBI, IRDAI, PFRDA, or equivalent) |
| Tata DLT registration | PE registered on the Tata DLT portal. In Partner-Managed, the TM is registered separately; in Self-Managed, the same entity registers as both PE and TM |
Provisioning Process
Step 1: Tata DLT Registration
Who: PE (and TM, if different)
Register on the Tata Teleservices DLT portal:
| Setup | What to register |
|---|
| Self-Managed | Register the same legal entity as both PE and TM |
| Partner-Managed | PE registers as PE; TM registers separately as TM |
- Download the BFSI Customer Application Form and the Aggregator Telemarketer Declaration.
- Fill in all fields. The BFSI form captures the PE’s regulatory category, governing regulator, licence number, DLT registration ID, and chosen setup (Self-Managed or Partner-Managed). The TM declaration captures the TM’s PAN, CIN, Tata DLT TM ID, and the PE relationship.
- The PE signs and seals the BFSI form; the TM signs and seals the TM Declaration. In Self-Managed, the same legal entity signs both forms in its respective PE and TM capacities.
- Submit both forms to Plivo by emailing them to your Account Manager or raising a Plivo Support ticket with the forms attached.
Step 3: Plivo Allocates the Number and Issues the NOC
Who: Plivo
After Plivo validates both forms:
- Plivo allocates a 160-series number to your account.
- Plivo issues a No Objection Certificate (NOC) to the TM by replying to the same email or support ticket where the forms were shared. Plivo issues a separate NOC for each number procured.
Who: PE (always — in Self-Managed, log in with your PE persona on Tata DLT)
The PE logs into the Tata DLT portal and submits the Voice Header registration with these fields:
| Field | Value |
|---|
| Entity ID | Your PE ID |
| Header CLI | The 160-series number allocated by Plivo |
| Business Category | The BFSI category that matches your business on the Tata DLT portal |
| Supporting documents | Upload your business-category certificate from the governing regulator and the Plivo NOC for this number |
| Remarks and Purpose | State the transactional or service purpose of the calls |
| Setup | What to select |
|---|
| Self-Managed (PE = TM) | Select PE and TM are the same |
| Partner-Managed (PE ≠ TM) | Select PE and TM are different and enter the TM’s Entity ID |
Who: TM — skip this step in Self-Managed
In Self-Managed, the Voice Header proceeds directly to Tata review. In Partner-Managed, the TM logs into the Tata DLT portal, opens the pending Voice Header using the URN shared by the PE, and approves it.
The TM goes to Voice Header Registration List For TM and reviews the pending request.
The TM then accepts or rejects the request.
Tata’s DLT team reviews and approves the Voice Header within 3–5 business days. You receive an email once the header is approved.
Step 6: Voice Template Registration
Who: PE
The PE logs into the Tata DLT portal and goes to Voice > Voice Template Registration by PE. Register a Voice Content Template for each message type you intend to send (for example, payment reminders, OTP delivery, transaction confirmations).
Each template defines the exact messages transmitted using the 160-series number. Once templates are approved, the number is ready for live operations.
Estimated Timelines
| Step | Duration |
|---|
| Tata DLT registration | 2–3 business days |
| Plivo number allocation and NOC issuance | 1–2 business days after form submission |
| Voice Header approval by Tata | 3–5 business days |
| Voice Template approval by Tata | 1–2 business days |
| Total | ~7–14 business days |
Best Practices
- Maintain compliance documentation — Keep all documents (PE Certificate, TM Certificate where applicable, signed forms, NOCs, regulatory certificates) in a secure, accessible location for audits.
- Monitor DLT portal status — Check the Tata DLT portal regularly for renewal requirements and compliance notifications.
- Test before go-live — Validate Voice Templates and call flows in a test environment before production.
- Stay updated on regulations — Monitor TRAI and DoT announcements for changes to 160-series number regulations.
FAQs
No. 160-series numbers are strictly for transactional and service communications. Using them for promotional or marketing purposes violates TRAI regulations and can result in number disconnection and penalties.
Do I need to submit a new NOC for every 160-series number?
Yes. Plivo issues a separate NOC for each number procured. Upload the relevant NOC during Voice Header registration on the Tata DLT portal.
Plivo currently provisions 160-series numbers exclusively through Tata Teleservices. Register as a Principal Entity on the Tata DLT portal.
You receive notification via the DLT portal with the reason for rejection. Common reasons:
- Incomplete or incorrect documentation
- Mismatch between PE or TM details and submitted documents
- Invalid NOC or regulatory certificate
Review the reason, correct the issue, and resubmit.
Do I need to renew my 160-series numbers?
Yes. Maintain active PE registration (and TM registration where applicable) on the Tata DLT portal and keep all compliance documents current. Check with Tata for renewal timelines on PE registration and content templates.
