Is AI calling legal in India? What TRAI changed
Yes, AI calling is legal in India. What changed on 18 September 2026 is narrower and more concrete: TRAI now defines "A2P calls" to explicitly include autodialled, robocall and artificial-voice calls, and requires the business sending them to declare that use to its telecom provider in advance. An undeclared A2P call, whatever it says, is treated as spam.
The short answer
Nothing in TRAI’s Third Amendment to the Telecom Commercial Communications Customer Preference Regulations, 2018, gazetted 18 September 2026, makes AI voice calling illegal in India. It does something more specific, and more useful to know before you sign a contract: it names the category an AI voice agent’s outbound calls fall into, and attaches a duty to it.
What changed
Two changes matter for anyone buying or running outbound voice AI in India.
First, a new definition. The amendment inserts clause (ea) into the principal regulations:
“Application-to-Person call or A2P call” refers to a voice call that is initiated by an application, software system, or automated platform without direct human dialling and delivered to an individual telecom subscriber; including using autodialling, robo-calls and/or pre-recorded/artificial voice technologies.
That is not a vague aside; it is the operative definition the rest of the amendment hangs on, and it was written to be technology-neutral: an autodialer working a list, a recorded robocall, and a voice AI agent conducting a live conversation are all “without direct human dialling,” so all three land in the same category. Read what the category covers in full in A2P call.
Second, a declaration duty. Regulation 4 is replaced with this:
Every Sender shall declare to the Originating Access Provider (OAP), in advance, about the use of Application-to-Person (A2P) calls, along with the details such as Calling Line Identification (CLI) ranges to be used for making A2P calls… Provided that any such call made by a Sender without prior declaration to the OAP, shall be treated as Unsolicited commercial communication.
Read plainly: before a business places A2P calls, it tells its telecom provider which numbers it will call from, and that gets recorded on the industry’s shared DLT platform. Skip the declaration and the calls are treated as spam, not because of anything said on the call but because the paperwork was never filed.
The enforcement side: AI now watches for AI
The amendment also inserts a new regulation 21A, requiring every terminating carrier to run an AI/ML-based detection system that flags Calling Line Identifications with a high probability of sending unsolicited commercial communication, and share the flag with the originating carrier within two hours. It is the mirror image of the declaration duty: one side of the rule tells you to identify yourself before you call at scale, the other side is the machinery that goes looking for the numbers that did not.
When it takes effect
The regulations are staged from the 18 September 2026 gazette date: most provisions in thirty days, the declaration duty in regulation 4 among a smaller set that takes sixty days, and a further batch of amendments (including a termination charge on A2P calls) at ninety days. A business running outbound voice AI calls into India has a window measured in weeks, not months, to have this conversation with its telecom provider and its vendor.
What to ask before you sign
Three questions, on top of the nine questions to ask a voice AI vendor:
- Who is the “Sender” on our calls, us or you? The declaration duty falls on the Sender, and if that is the vendor’s own number resources rather than yours, you need to know whose declaration you are relying on.
- Has that declaration been filed, or is it a plan for later? TRAI’s language treats an undeclared call as spam from the first call, not from some grace period.
- What happens to our calls if the declaration lapses or a number gets flagged under the new AI/ML detection in regulation 21A? A vendor who has not thought about this has not read the amendment.
This is a paperwork question with a real consequence: a call that never gets answered because it was treated as spam before anyone picked up. It belongs in the same conversation as the technical questions in nine questions to ask a voice AI vendor, next to where the vendor’s servers physically sit.
Questions this raises
Is AI calling legal in India?
Yes. TRAI's Third Amendment does not ban automated or AI voice calls. It puts them, by name, inside a defined category — "A2P calls" — and requires the business sending them to declare that use to its telecom provider in advance. An undeclared A2P call is treated as unsolicited commercial communication, whatever it says.
Does TRAI require an AI voice call to announce itself as AI?
No. The Third Amendment does not add an in-call spoken-disclosure requirement. What it adds is paperwork before the fact: the Sender declares the numbers it will use for A2P calling to its Originating Access Provider, and that declaration is recorded on the industry's shared DLT platform.
What counts as an A2P call under the new rule?
TRAI's own words: a voice call "initiated by an application, software system, or automated platform without direct human dialling," including autodialling, robo-calls, and calls using pre-recorded or artificial-voice technology. An outbound voice AI agent is squarely inside that definition.
What happens if a business skips the declaration?
The regulation says the call "shall be treated as Unsolicited commercial communication," which puts it on the receiving end of the same detection and blocking rules built for spam — including the new AI/ML-based flagging TRAI requires terminating carriers to run.