# TRAI's new rules for AI and automated calls: what your business needs to change > TRAI's September 2026 amendment brings AI voice agents and robocalls under a declare-first regime. Here is what changed, when it applies and a checklist for businesses that call customers. - Page: https://www.brandbakery.tech/pulse/trai-ai-call-rules-2026 - Last updated: 2026-10-21 Breadcrumb: [Home](https://www.brandbakery.tech/) > [Pulse](https://www.brandbakery.tech/pulse) > TRAI's new rules for AI and automated calls: what your business needs to change - **By:** Abhishek - **Published:** 2026-10-21 - **Reading time:** 7 min - **Topics:** AI & Tech If your business uses software to call customers, the ground moved on 18 September 2026. That day TRAI finalised the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, which change how automated calls, AI voice agents and follow-up calls after an enquiry are treated in India. Most of the coverage so far has been about spam and Truecaller. That is the consumer side. This piece is for the other side: the clinic that wants an AI receptionist to call back missed calls, the coaching centre that phones every new lead, the D2C brand that confirms cash-on-delivery orders by voice. This is a plain-language reading of public documents, checked on 20 October 2026. It is not legal advice, and your telecom provider will have its own onboarding steps. ## What actually changed TRAI’s [press note on the amendment](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf) amends the TCCCPR 2018, the rulebook behind DND and commercial-call registration. The parts that matter to a business calling customers: **Automated calls now have a legal name and a duty attached.** The regulations treat an application-to-person (A2P) call as a voice call started by an application, software system or automated platform without a person dialling it. That covers robocalls, pre-recorded calls and AI voice agents. Senders have to declare A2P use to their telecom provider in advance, along with the numbers they will call from. An A2P call made without that declaration is treated as unsolicited commercial communication, which is the regulatory term for spam. **Automated calls can cost more.** The terminating operator can charge up to 5 paise a minute for A2P calls. Small per call, but it adds up if you run large outbound campaigns. **An enquiry gives you a seven-day window.** When a customer enquires in writing or through a digital channel, you may send commercial communication in response for seven days from that enquiry. You must keep the enquiry in a verifiable form. A website form submission with a timestamp, or a WhatsApp message, is the kind of record that helps here. A vague “they called us once” is not. **Old consent can count, if you can prove it.** Consent collected before or outside the operators’ consent registration system is recognised when it was obtained through verifiable means and registered. If your lead list came from a form three years ago and nobody kept the record, treat it as unusable. **Spam detection gets automated, and so does enforcement.** Operators must use AI and machine learning tools to flag suspected spam numbers. [MediaNama’s reading of the final text](https://www.medianama.com/2026/09/223-trai-truecaller-140-1600-calls-spam-rules/) says five or more spam flags within 10 days pushes the originating operator to re-verify the sender’s KYC, carry out physical verification and disconnect if misuse continues. The complaint threshold for action also drops from five complaints to three when the number has been AI-flagged in the same period. **Call-blocking apps can’t blanket-tag the regulated series.** Numbers in the 140xx, 1600xx and 1601xx series cannot be tagged as suspected spam by call-management apps. Customers can still block calls on their own phones. ## When it applies The provisions roll out in steps from notification. According to MediaNama’s summary of the final text: - **30 days:** AI-based spam detection, A2P pre-declaration, the consumer appeal process, recognition of legacy consent, and the rules on call-blocking apps. - **60 days:** the A2P termination charge and the seven-day enquiry window. - **90 days:** the lower complaint threshold. Counting from 18 September, the first group is already in force or about to be, and the rest lands by mid-December 2026. Check the exact dates against the [gazette text on TRAI’s site](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) or with your operator. TRAI’s site was intermittently unavailable when we checked, so keep a saved copy once you get it. ## 140, 1600 or 1601: which series is yours? This is where most small businesses get confused. - **140xx** is for promotional calls from any sector. If your AI agent is calling to sell, offer a discount or invite people to a webinar, this is the lane. - **1600xx** is for service and transactional calls from entities regulated by RBI, SEBI, IRDAI and PFRDA, and for government-to-citizen calls. A bank, NBFC or insurer reminding you of a payment due sits here. - **1601xx** is a further designated series that vendors describe as covering transactional calls for sectors such as utilities and logistics. Eligibility is set by the regulator and allocated after verification, so ask your operator before you plan around it. A regular 10-digit mobile number is not where automated commercial calls should come from. Many small businesses do exactly this today with a dialler app and a SIM. Under the new rules that is the fastest way to collect spam flags and lose the number. ## Inbound is different from outbound A customer calling your number and reaching an AI receptionist is not the business calling them, so the outbound declaration rules are not the main concern there. The DPDP rules on personal data still apply to what the agent records, and good practice is to say at the start that the caller is speaking with an AI assistant. Outbound is where the new rules bite. A few common cases: - **Calling back a missed call within minutes.** The customer reached out first, and that is usually the safest kind of outbound call. If it is automated, it still needs to be declared and made from a declared number. - **Calling every form lead the same evening.** Covered by the seven-day enquiry window if you have the form record. After day seven, you need registered consent. - **Calling a purchased database.** Do not. There is no verifiable consent, no enquiry, and every call is a candidate for a spam flag. - **Reminder calls for appointments, deliveries or payments.** These are service calls in spirit, but the right series depends on your sector. Confirm with your operator rather than assuming. ## A checklist before your AI agent makes another call 1. **List every way your business places automated calls.** Dialler apps, a CRM’s auto-dial feature, a voice AI vendor, an IVR that calls back. Many owners don’t know their agency or vendor is placing calls on their behalf. 2. **Get the declaration done.** Ask your telecom provider (or your voice AI vendor, if they provide the numbers) how they handle A2P pre-declaration and which numbers are declared. Get the answer in writing. 3. **Move promotional calling to a 140 header.** Registration runs through the operators’ DLT platforms, the same system used for SMS headers and templates. 4. **Store the proof of every enquiry.** Timestamp, channel, what the person asked for. If your website form sends an email and nothing else, fix that first. Our article on [testing your contact form](https://www.brandbakery.tech/pulse/test-your-contact-form) covers the basics. 5. **Write the seven-day rule into your follow-up logic.** The agent should stop calling on day eight unless the customer has given registered consent or has replied. 6. **Make the agent introduce itself honestly.** First sentence: who is calling, from which business, and that it is an AI assistant. Offer a human callback. This is also what keeps complaints down. 7. **Watch your complaint and flag signals.** If customers keep hanging up in the first five seconds or complaining, your list or your timing is wrong. Fix that before the operator’s thresholds do it for you. 8. **Keep logs.** Who was called, when, from which number, under which consent or enquiry, and what was said. You will need the same records for DPDP compliance anyway. ## What this means if you are buying an AI calling agent Ask any vendor, including us, three questions before you sign: - Which numbers will the calls come from, and who declares them to the operator? - How does the system store consent and enquiry records, and can I export them? - What happens on day eight, or when someone says “don’t call me again”? A vendor who answers with “our AI sounds very human” has not answered the question. At Brand Bakery we build [AI employees](https://www.brandbakery.tech/ai-employees) that answer and make calls, and the rules above are part of the build, not an afterthought. An [AI receptionist](https://www.brandbakery.tech/ai-employees/receptionist) mostly handles inbound calls and WhatsApp. An [AI sales executive](https://www.brandbakery.tech/ai-employees/sales-executive) calls new enquiries quickly, inside the enquiry window, from declared numbers, and hands the conversation to your team when a person should take over. The new rules are stricter, but they are not hostile to automation. They are hostile to anonymous, undeclared, unconsented calling. A business that already calls only people who asked to hear from it will find the changes mostly paperwork. ## Keep reading - [More from Pulse](https://www.brandbakery.tech/pulse) - Start a project: https://www.brandbakery.tech/contact --- Brand Bakery is a design-first digital studio in New Delhi. Start an enquiry at https://www.brandbakery.tech/contact or email support@brandbakery.tech. This is the Markdown copy of https://www.brandbakery.tech/pulse/trai-ai-call-rules-2026; the site index for language models is https://www.brandbakery.tech/llms.txt.