Full Report
The Indian government has directed telecom service providers (TSPs) in the country to mandatorily display callers' registered names along with their numbers for incoming calls starting November 1, 2026, in an effort to help people identify calls from unknown numbers and tackle spam or fraudulent calls. To that end, the Department of Telecommunications has issued a circular urging service
Analysis Summary
# Regulation/Compliance: Calling Name Presentation (CNAP) Mandate
## Overview
This regulation mandates that all Telecom Service Providers (TSPs) in India display the registered name of a caller (as per subscriber records) on the recipient's device. The initiative aims to enhance transparency, reduce the efficacy of spam and fraudulent calls, and allow citizens to identify unknown callers without third-party applications.
## Key Details
- **Issuing Authority:** Department of Telecommunications (DoT), Ministry of Communications, Government of India.
- **Effective Date:** November 1, 2026.
- **Jurisdiction:** India / Telecommunications Industry.
- **Status:** Final (Circular issued).
## Requirements
### Mandatory Requirements
1. **Registered Name Display:** TSPs must display the caller's name as recorded in the subscriber data record (SDR).
2. **Database Maintenance:** Every originating TSP must establish and maintain a database mapping subscriber names to numbers.
3. **Cross-Operator Queries:** Terminating TSPs must query the originating operator's database to retrieve and present the caller's identity.
4. **International Labeling:** Calls originating outside of India must be clearly labeled as "International Call."
5. **Business Name Validation:** For business/bulk connections, the "preferred name" must be verified against official Trademark or GST records.
6. **2nd Field Display:** The calling name must be displayed in a specific second field if the number is not already saved in the recipient’s contact list.
### Recommended Practices
1. **Secure-by-Design:** Implement the CNAP system with built-in security to prevent data leaks.
2. **Privacy Protections:** Ensure the calling name identity is not retained/stored by the receiving TSP or device after the call is completed.
## Affected Organizations
- **Industries:** Telecommunications (Wireless TSPs).
- **Organization Size:** All TSPs operating 4G and higher generation technologies.
- **Geographic Scope:** All licensed operators within the territory of India.
## Compliance Timeline
- **October 13, 2026:** Official circular issued by the Ministry of Communications.
- **November 1, 2026:** Final deadline for full implementation and mandatory display for 4G/5G networks.
- **TBD:** Future rollout for 2G, 3G, and Public Switched Telephone Networks (PSTN).
## Implementation Guidance
### Assessment Phase
- Audit existing Subscriber Data Records (SDR) for accuracy and completeness.
- Evaluate current 4G/5G network infrastructure for compatibility with Calling Line Identification (CLI) extensions.
### Implementation Phase
- Develop/provision high-speed databases for real-time name-to-number mapping.
- Establish inter-operator query mechanisms to allow name retrieval across different networks.
- Update Customer Application Forms (CAF) for new connections to capture "preferred names" for businesses.
### Validation Phase
- Verify that name queries do not introduce significant latency in call setup.
- Ensure the Calling Line Identification Restriction (CLIR) feature correctly masks names for users who opt for privacy.
## Technical Requirements
- **Technology Stack:** Implementation is currently limited to 4G and higher generation technologies.
- **Data Privacy:** TSPs must ensure that the name identity is transient and not cached permanently on the receiver's end post-call.
- **Authentication:** For business names, TSPs must verify original Trademark or GST certificates and attach true copies to the subscriber's file.
## Penalties & Enforcement
- **Fines:** While specific monetary penalties were not detailed in the summary, non-compliance with DoT circulars typically results in significant financial penalties under the Telecom License Agreement.
- **Enforcement:** The Department of Telecommunications (DoT) will monitor implementation via Quality of Service (QoS) audits.
## Related Standards
- **TRAI Recommendations:** Aligns with Telecom Regulatory Authority of India (TRAI) frameworks regarding spam reduction.
- **GST & IP Law:** Integration with the Trade Marks Registry and GST portal for business identity verification.
## Resources
- **Official Documentation:** [h-t-t-p-s://www.dot.gov.in/documents/orders-and-notices] (Defanged)
- **Official Circular:** [h-t-t-p-s://www.dot.gov.in/static/uploads/2026/10/d86da4092d50f052becd6113de83d37e.pdf] (Defanged)
## Practical Recommendations
- **TSPs:** Optimize database query latency to prevent "post-dial delay" which could degrade user experience.
- **Enterprise Users:** Ensure your registered Trademark or GST names match your intended "Preferred Name" to avoid being flagged as unknown or generic callers.
- **Security Officers:** Review data transit security to ensure caller names are not intercepted during the inter-operator query process.