India Orders Caller-ID Apps to Share Spam Reports With Carriers
India's Telecom Regulatory Authority of India (TRAI) now requires caller-ID and call-management apps that allow spam flagging to share those user reports with telecom operators.
Under the change, the apps must feed reports into a blockchain-based ledger maintained by operators — a shared record used to track business communications and enforce anti-spam rules — according to TechCrunch. TRAI said the goal is to widen the pool of reports operators can act on. The numbers involved run into the billions.
The amendments also limit independent action by the apps. They may not broadly block, filter or label as spam calls from designated number series, meaning prefixes set aside for promotional, service and transactional traffic. That keeps those ranges usable as labeled business traffic and removes one layer of app-level blocking.
The dispute centers on Truecaller, for which India is the largest market. The company draws well over 350 million of its more than 500 million monthly active users from India. Truecaller said users in India received about 42 billion spam calls in 2025 and said it blocked nearly 12 billion of them.
Truecaller described the data-sharing demand as a "one-way exchange" that is "anti-competitive". It said the rule hands commercially valuable data from app makers to carriers. User-submitted spam reports serve two purposes. They flag abuse and they help train systems that decide what looks like spam.
The amendments follow steps reported in July. TRAI had proposed that call-management platforms share spam reports with the operators' Do Not Disturb (DND) registry, a list meant to shield users who opt out of marketing contacts, according to MediaNama. In the same cycle, TRAI sought powers under India's IT Act, the country's main law for electronic communications and online conduct, to take action against Truecaller and other call-management apps. Truecaller may challenge the mandate in court, according to Light Reading.
In my view, the technical dispute cannot be separated from the business one. Voice-spam control depends on broad signals such as user reports, calling patterns and numbering information, while actual enforcement depends on carriers, with line disconnections, business registries and financial penalties. Feeding app reports into the operator system closes that gap. If spam data becomes a common regulatory input, caller-ID apps will have to compete more on speed, accurate name lookup, clear call reasons, fraud scores and business onboarding rather than on owning reports alone. For carriers, more incoming signals can make action against Unsolicited Commercial Communication more precise if intake, deduplication and handling of mistaken flags work well. For users, the long-term upside is fewer unwanted calls and more consistent treatment across networks and apps.
