AI voice agents in India: TCCCPR, DLT, the 140 and 1600 series and the DPDP Act

Market shape

India is where voice agents meet the most structured commercial-calling regime in the world and the most code-switched callers. A clinic or a real-estate developer buys an AI calling agent or voicebot; a bank or a lender buys conversational AI for collections or voice automation. Both buy under TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), which decide the number series a call may use, the registration behind it, the hours it may be made and, since 18 September 2026, whether an automated caller has been declared at all.

Five facts. First, the domestic vendor base is growing fast: Tracxn's database lists 32 voice AI startups in India, 19 of them funded, with USD 458 million raised in total and USD 339 million raised in 2026 through August against USD 12.9 million in the same period of 2025 (page updated 31 August 2026, reported). Second, the use case that pays is collections and loan servicing, and the regulator for those callers is the RBI as much as TRAI. Third, the only analyst figure available is regional: MarketsandMarkets estimates Asia Pacific at USD 650 million in 2025 rising to USD 8.2 billion by 2032 (report page as retrieved 1 October 2026). Fourth, Hinglish is the default register, not an edge case. Fifth, the data-protection regime is arriving in phases through May 2027, so contracts signed now need a path to the consent-manager framework.

Regulatory quick card

The compliance matrix row is india. The rule as published, informational rather than advice:

• Registration and series (TCCCPR 2018). Senders and telemarketers register on the Distributed Ledger Technology (DLT) platform run by the access providers. Promotional calls go out on the 140xx series; transactional and service calls on the 1600xx and 1601xx series. Recipients' Do Not Disturb (DND) preferences must be scrubbed before promotional calls.
• Calling hours. Promotional calls only between 9 a.m. and 9 p.m.; DND-registered numbers must not receive promotional calls.
• September 2026 amendments. TRAI's press release of 18 September 2026 announces the Third Amendment Regulations, 2026. It defines application-to-person (A2P) calls as voice calls initiated by an application or automated platform without direct human dialling, including autodialling, robocalls and pre-recorded or artificial-voice technologies. Every entity using A2P calls must pre-declare that use to its telecom provider together with the CLIs to be used; undeclared A2P calls are treated as unsolicited commercial communication, and a termination charge of up to INR 0.05 per minute applies, with the designated series exempt. A new Regulation 21A mandates AI/ML-based detection of suspected spam CLIs and inter-operator sharing; action is triggered on three unique complaints in ten days when the CLI is also flagged. Commercial communication based on a customer inquiry is allowed for seven days if the inquiry is in writing or digital and verifiable. Misused headers are suspended within six hours; telemarketer misuse brings one-year disconnection and blacklisting. Call-management apps may not blanket-block the 140 and 1600 series. A secondary report describes a 30, 60 and 90 day commencement schedule; we could not confirm those dates in the release and the gazette text is the authority.
• AI disclosure. A requirement to declare a synthetic voice at the start of a call has been reported in draft form; treat disclosure as required by default.
• Data protection. The Digital Personal Data Protection Act, 2023 treats recordings as personal data needing notice and a lawful purpose. The Rules were notified on 13 November 2025 (reported); the consent-manager framework applies from 13 November 2026 and the substantive duties from 13 May 2027.
• Payment data. RBI's direction of 6 April 2018 requires the entire data relating to payment systems to be stored only in India.
• Collections overlay. RBI fair-practice and digital-lending directions require collections calls to avoid harassment, respect hours and identify the lender and the recovery agent.

Telephony and numbering

Consumers have ten-digit mobile numbers and almost no landlines. Businesses that call them in bulk must do so from the designated series through DLT-registered identities; a voice agent dialling from an ordinary ten-digit number at scale is the pattern the September 2026 amendments were written to catch. The practical sequence for a buyer: register the sender on DLT, register headers and content templates, pre-declare the A2P use and the CLIs, separate promotional (140) from transactional (1600) traffic by template, and scrub DND before every promotional dial. The upside of the series is that call-management apps may not spam-tag them, which protects answer rates for legitimate reminders.

Language and accent gates

Hinglish is the median call: English nouns, amounts and dates inside Hindi grammar, switching mid-sentence. A monolingual Hindi or monolingual English agent fails it. Beyond Hindi, the languages in this page's data each carry their own switching pattern with English. Gates to test with recorded callers: a mobile number and a rupee amount read in mixed languages; a name spelled in a regional script and read back; a caller who answers in Tamil to a Hindi greeting; and a fast speaker on a low-bitrate mobile connection. Ask which languages are production-tested and which are listed; the two are different.

Data residency and hosting

The DPDP Act allows cross-border transfers except to countries the government restricts, so the law alone does not require Indian hosting. Two things do in practice: RBI's payment-data localisation direction, which puts any agent that hears or writes payment data inside the Indian storage perimeter, and the procurement norms of banks and lenders, which commonly demand in-country or on-premises deployment for the whole audio path. Ask for the hosting region of each component and a sub-processor list.

Buyer landscape

Banks, non-bank lenders and fintechs lead with collections, EMI reminders and KYC follow-up. Insurers run renewals and claims intake. Hospitals and diagnostics chains run appointment lines. Developers and portals run lead qualification under the 140 series. Staffing firms run high-volume screening in regional languages. Many enterprises buy through their telecom provider's enterprise arm or a CPaaS partner, who hold the DLT relationships.

Vendor landscape

The vendor list in this page's data is alphabetical and typed, not ranked. Local specialists are Indian-headquartered platforms built around Indian languages and the DLT regime. Global platforms are international agent builders used in India, usually through a local telephony partner. CCaaS incumbents bundle the agent into an existing contact centre. Fifteen names appear; any of them can pass or fail your demo. The acceptance test is a Hinglish call from one of your own recorded customers that ends with a promise-to-pay or an appointment written into your system, placed from a declared 1600-series CLI.

Questions to ask vendors in this market

The six questions in this page's data, in order: which DLT registrations and CLIs the calls run under and whether the A2P use is pre-declared; how DND scrubbing and the 9 a.m. to 9 p.m. window are enforced and how transactional traffic stays off the 140 series; where recordings and payment data are stored; a live Hinglish call with mixed-language numbers; how the DPDP notice is given per language and how consent records will meet the November 2026 and May 2027 milestones; and the all-in cost per connected minute in rupees, per language.