AI voice agents went from demo to daily use in Indian commerce this year. They confirm cash-on-delivery orders, remind customers about a pending payment, call back a missed call, and nudge an abandoned cart. Most were set up quickly, on whatever numbers the provider had.
TRAI has now drawn a line around them. Its latest amendment to the spam-call rules defines a new category, the A2P call, and AI voice agents are inside it. From around 17 November 2026, a business has to declare these calls to its telecom operator in advance. If it does not, TRAI's text is blunt: the calls "shall be treated as Unsolicited commercial communication".
I read the regulation and TRAI's explanatory memorandum, because most of the coverage mixes this up with a different TRAI announcement about AI agents in telecom support. Here is what applies to a business, and what does not.
What did TRAI change?
The rule is the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, notified on 18 September 2026. It defines an Application-to-Person (A2P) call as:
"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"
An outbound AI voice agent is software dialling a customer. It is an A2P call. TRAI also declined requests to exclude calls where a human joins after the system dials, saying there was "no necessity of any change".
The rule covers service and transactional calls too, not only promotions. TRAI's stated reason is to stop "misuse of A2P calling for sending UCC in the garb of transaction or service calling".
When does it apply?
The amendment comes into force in stages, counted from its publication in the Gazette on 18 September:
| Stage | Roughly | What starts |
|---|---|---|
| 30 days | 18 October 2026 | Most of the amendment, including the consent and service-call changes |
| 60 days | 17 November 2026 | The duty to declare A2P calls, the header-misuse rule and the inter-operator call charge |
| 90 days | 17 December 2026 | The items in the annexure, including the appeal process and AI-flag corroboration of complaints |
The dates are counted from the Gazette issue date. Some trackers count from a later date, so confirm the exact day with your operator. Either way, the declaration duty starts this month.
What does a business have to do?
Declare automated calling to your operator. Regulation 4 says 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". In plain terms: the telecom company that provides your calling numbers must know which numbers place automated calls. If your AI voice provider places the calls on its numbers, it must declare them, and you should have that in writing.
Use the right number series. TRAI's framework separates calls by purpose:
- 140xx for promotional calls.
- 1600xx for service and transactional calls from banks, financial entities and government.
- 1601xx for service and transactional calls from other sectors. The first phase covers utilities, courier and logistics. E-commerce is not designated yet, though TRAI says it may add sectors "from time to time".
So for most D2C brands today, promotional AI calls belong on 140xx numbers through a registered telemarketer, and service calls go on declared numbers.
Know which calls need consent. The amended definition of a service call has two parts:
- Calls to an existing customer about something they have bought, such as delivery information, are service calls and "do not require Explicit Consent". COD confirmation and delivery updates fit here, as long as the call does not slip in an offer.
- Calls that help complete a purchase in progress need explicit consent, valid for 7 days unless renewed or revoked. Consent can now be taken "through any verifiable means" and then registered.
An abandoned-cart call is the grey area. If it carries a discount or offer, treat it as promotional. If it only helps a customer finish a purchase they started, it is likely the second kind and needs recorded consent. TRAI has not ruled on this case specifically.
What happens if you get it wrong?
The enforcement is aimed at senders, and it is not limited to the number that misbehaved.
- Operators' systems flag numbers as suspected spam. Three or more complaints plus an AI flag, or five complaints, within 10 days can trigger suspension and an investigation.
- On a first violation, outgoing calls are barred on all of the sender's telecom resources, "including PRI/SIP trunks, SIMs etc.", for 15 days.
- Later violations can mean disconnection of everything for a year and blacklisting.
That first point is the real risk. A badly configured cart-recovery bot could take your support line and your COD confirmation line down with it.
The amendment also allows an inter-operator charge of up to ₹0.05 a minute on A2P calls from ordinary numbers, with 140xx, 1600xx and 1601xx numbers exempt. Ask your provider whether it will show up in your calling rates.
What about the TRAI rule on AI agents in customer support?
That is a separate amendment, notified on 2 November 2026, to the telecom complaint redressal rules. It lets telecom operators run complaint centres round the clock with "human representatives or automated systems or AI agents", requires a human for at least sixteen hours a day, and says a consumer "shall get a notification that he is communicating with an AI Agent".
It applies to telecom and internet providers, not to a D2C brand. But it is a clear signal of how an Indian regulator thinks AI support should work: disclosed, supervised, with a human reachable. Copying those three habits costs almost nothing.
A checklist for this week
- List every automated call you make: COD confirmation, delivery, payment reminders, missed-call callbacks, cart recovery, reorder nudges. Mark each as service or promotional.
- Ask your voice provider in writing: whose numbers are used, whether they are declared to the operator as A2P, and who carries the risk if they are flagged. TRAI's memorandum says action can be taken against an intermediary's resources "without prejudice to any other regulatory action that may be taken against the PE".
- Strip offers out of service calls. A COD confirmation that ends with a discount is no longer a service call.
- Record consent for purchase-in-progress calls in a verifiable form, with the date, so the 7-day window can be checked.
- Keep promotional calls separate, on 140xx through a registered telemarketer, respecting DND preferences.
- Watch complaints. Track how often customers mark your calls as spam. A handful in a week is enough to trigger action.
- Say it is an AI, and offer a human. Not legally required for your calls, but it lowers complaints, which is what triggers enforcement.
The rules do not exempt anyone from data protection either. TRAI's text notes that the Sender remains bound by the DPDP Act, 2023, which I covered in the DPDP checklist for online stores.
Where we help
At INovaBeing we build AI voice agents for order confirmation, COD verification, missed-call recovery and support under Voice AI. The calling setup is part of the build: declared numbers, service and promotional calls kept apart, consent recorded, and a human handoff when the customer asks.
If you are weighing whether a voice agent is worth it at your volume, I wrote about recovering missed calls with an AI voice agent and about the cost of building versus buying one.
What I take from this
TRAI has not banned AI calling. It has made it visible. A business that declares its automated calls, keeps service calls free of offers and records consent will barely notice the change.
The businesses at risk are the ones that do not know which numbers their bot calls from. Find out before the declaration duty starts, not after a 15-day block on every line you own.
TRAI's amendment and its explanatory memorandum are on trai.gov.in. Send the link to whoever runs your calling setup.




