India has redrawn its spam rules. On September 18, the Telecom Regulatory Authority of India (TRAI) notified amendments to curb unsolicited commercial communication. Automated calls now need pre‑declaration, telecom firms must use artificial intelligence for detection, and caller‑ID apps face tighter data sharing and tagging controls. The update resets product, legal and operations playbooks across startups and BPOs.
For students and founders building AI voice agents, the biggest shift is definition and cost. Application‑to‑person calls cover auto‑diallers, robocalls and synthetic voices. If not pre‑declared, carriers can treat them as spam and levy up to five paise per minute on the originating network, with designated 140, 1600 and 1601 series exempt.
TRAI anti‑spam rules: what changed on September 18 #
TRAI has mandated AI and machine learning systems to flag suspected spam, and share intelligence across operators. Action triggers shrink when three unique complaints match an AI flag within ten days. If five numbers tied to one sender are flagged in ten days, telcos must escalate from KYC checks to disconnection. Appeals are now available.
Automated AI calls: disclosure and termination charges #
Entities using automated calling must pre‑declare use and the specific calling line identifications to their provider. Undeclared traffic is treated as unsolicited communication. Termination charges of up to five paise per minute now apply to such automated traffic, deterring grey‑route dialling. Exemptions cover regulated commercial series and authority‑authorised calls to keep essential services flowing.
Caller‑ID apps and tagging: what must change now #
Call‑management apps cannot blanket tag or block calls from designated 140, 1600 and 1601 series. They may offer spam reporting only if they relay each report to the industry DLT platform. Users can still block numbers locally. Expect engineering work for reporting pipelines and clearer in‑app consent flows. Truecaller has already flagged concerns.
Compliance timelines and penalties you cannot miss #
The Gazette text sets staggered commencement: most provisions in 30 days, specified clauses in 60 days, and annexed amendments in 90 days from publication on September 18, 2026. Misused headers or templates must be suspended within six hours; repeat telemarketer abuse invites one‑year disconnection and blacklisting. Plan sprints against these clocks.
Day‑one checklist for product, legal and ops #
Map every outbound flow that uses software dialling; register CLIs and declare A2P. Integrate spam‑report relays to DLT if you provide reporting. Digitise and register legacy consents. Enable audit trails for seven‑day inquiry contacts. Update contracts to reflect essential terms. Resource trust and safety, telephony compliance and AI operations teams before grace windows close.
The takeaway is clear. Mark September 18, 2026 as the reset date, then work back from 30, 60 and 90‑day milestones. Builders should prioritise A2P disclosure, DLT integrations and consent hygiene. Job seekers can target trust and safety, regulatory tech and telecom compliance roles that these rules make business critical.