Quick answer: Yes, on TRAI’s terms. Under India’s TCCCPR 2018 a fully autonomous AI voice agent is a “robo-call”, and a sales call needs a registered sender, a 140xx number, a recipient who has not blocked it or gave registered consent, and written notice to your operator. Unregistered callers found sending unsolicited calls after complaints have every telecom connection barred for 15 days, then cut for a year on repeat.
Is AI cold calling legal in India?
AI cold calling means an unsolicited sales call in which the voice the other person hears is generated by software. In India the call is governed by the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR), made by the Telecom Regulatory Authority of India (TRAI) and enforced in the first instance by the licensed operators the regulations call access providers. The personal data behind the call falls under the Digital Personal Data Protection Act, 2023 (DPDP Act), whose consent provisions are not yet in force.
So “is AI cold calling illegal in India?” and “is cold calling illegal in India?” get the same answer: no, but the TCCCPR bans selling by phone outside its registration, number-series and preference system. Regulation 3(2) says no sender not registered with an access provider “shall make any commercial communication”, regulation 32 repeats it for any business or legal entity, and the definition of unsolicited commercial communication (UCC) catches every commercial call from an unregistered sender, whatever the recipient wanted.
That makes India unusual in this series. In the UK, Germany and Canada no regulator has said whether an AI agent counts as an automated call. India’s regulations answer it in a definition, so what remains is routing. Sources were all opened on 4 October 2026; this is not legal advice.
Does an AI voice agent count as a robo-call under TRAI rules?
On the text, yes. Regulation 2(bc) of the TCCCPR defines robo-calls as “any call made to any customer using an artificial or prerecorded voice to interactively deliver a voice message without the involvement of human being on calling side for participating in the dialogue”. That definition has three parts, and a fully autonomous AI sales agent meets all three:
- “an artificial or prerecorded voice”: a synthesised voice is artificial; “or” means it need not be recorded.
- “to interactively deliver a voice message”: the definition expects a conversation, which is what an AI agent holds.
- “without the involvement of human being on calling side for participating in the dialogue”: no one on your side is speaking.
Compare the UK, where the live-speech question is still open (see whether AI cold calling is legal in the UK under PECR regulation 19), or Canada, where the question is whether an agent is an automatic dialing-announcing device (see AI cold calling under the CRTC rules in Canada). TRAI wrote “artificial” and “interactively” into its definition.
The regulations also define an auto dialer call: initiated automatically by equipment following stored instructions, to stored numbers or an auto-generated list, which once answered plays a recorded message or connects to a live person. An AI dialler meets the first two parts; whether generated speech “plays a recorded message” is less clear, so the robo-call definition is the one that settles the AI question.
The limb that cuts the other way is the third. If a person on your side takes part in the dialogue, say an AI agent qualifies and a salesperson then speaks, the call arguably stops being a robo-call. It is still a promotional voice call if it sells, so consent and number series do not change. And for the pending A2P definition, TRAI rejected requests to exclude calls with a live human agent, saying it is “technically not feasible” for operators to tell which calls have one.
In one sentence: an AI agent that sells by phone in India is a promotional robo-call.
Promotional, service or transactional: which call is your AI agent making?
The TCCCPR classifies calls by content, not technology. A “commercial communication” is any call or message whose primary purpose is to inform about, advertise or solicit business for (A) goods or services, (B) a supplier or prospective supplier of them, (C) a business or investment opportunity, or (D) a provider or prospective provider of one. It does not matter whether the offer exists or is lawful, and purpose can be inferred from the content, its presentation, and what a recipient hears on calling back or opening a link from the call.
- Promotional voice call: any commercial call containing promotional material or advertisement. Mix promotion into any other commercial call and the whole call is promotional. Deliverable only to subscribers who have not blocked the relevant category in the preference register, or who have consent in the consent register; explicit digital consent overrides category preferences.
- Service call: (i) to your own customer about a product or service they have (warranty, recall, software upgrade, safety or security, periodic balance alerts, delivery), no explicit consent needed; or (ii) to a recipient to facilitate or complete their ongoing purchase or use, with explicit consent valid for seven days or as TRAI directs. Neither may promote.
- Transactional voice call: to your customer, in response to a transaction they started, within thirty minutes (OTPs, alerts, confirmations, refunds). No explicit consent, no promotion.
UCC is commercial communication that matches neither the recipient’s consent nor their registered preferences. Four kinds are excluded: transactional calls, service calls, government or constitutional-body calls in the public interest, and calls by or on the direction of TRAI or its authorised agency. Two provisos pull calls back in: anything from an unregistered sender, and any call made to deceive. “Consent” here can be explicit or inferred, and inferred consent can rest on a relationship such as a recent purchase, inquiry or application; but the promotional voice call definition delivers only to numbers that have not blocked the category or that hold registered consent, so do not treat a relationship alone as permission to call a number that has blocked promotions.
For AI agents the mixed-content rule is the trap: a service call that ends “while I have you, can I tell you about our upgrade?” is promotional. An agent with a free-form sales objective cannot safely run on a service-call number.
The India Call-Route Matrix: which number, which consent, which risk
Find what your AI agent does and read across. The series are as stated in TRAI’s explanatory memorandum to the Third Amendment: 140xx for promotional calls by registered senders and telemarketers; 1600xx for service and transactional calls by banking, financial services and insurance (BFSI) entities and for government-to-citizen communications; and 1601xx, a separate series for service and transactional calls by other sectors. TRAI “plans to introduce this series in a phased manner and has issued a Direction on 10th August, 2026 for first phase of its operationalisation, covering Utilities, Logistics and Courier services” (memorandum, item 6, B.ii). Within BFSI, TRAI says “it may not be desirable to mandate 1600 series numbers for all the entities in the BFSI sector”, records the suggestion that small players dealing only with a few existing customers be exempted from mandatory 1600 use, with the option to use 1600 numbers and action against them as unregistered telemarketers if they misuse the exemption (B.iii), and notes that the Third Amendment’s new proviso to regulation 3(1) lets it classify senders and set different criteria for each class, including exempting certain classes of senders if it deems that necessary (B.iv).
Corrected 10 October 2026: this paragraph, row C of the matrix and step 3 of the checklist previously said 1601xx covers service and transactional calls in all other sectors and left out TRAI’s view that not every BFSI entity need use 1600xx. TRAI’s memorandum says 1601xx is being introduced in phases, starting with utilities, logistics and courier services, and that small BFSI players may be exempted from mandatory 1600xx use. We have updated each of them and the sources table.
| Row | What the AI agent does | TCCCPR category | Number series | Gate before the call | AI-specific duty | If it goes wrong |
|---|---|---|---|---|---|---|
| A | Sells to a number that has given you no consent | Promotional voice call; robo-call | 140xx | Recipient must not have blocked all commercial communications (FULLY BLOCK), the relevant content category (BLOCK PROMO or categories 1–8), all modes (preference 10) or the robo-call mode (preference 15), the time band or the day type; bands before 10:00 and after 21:00 are off by default | Written advance notice to your originating operator of robo-call use and its objective (regulation 4) | Complaint within 7 days; operator checks whether scrubbing pre-checks were run, then acts under the regulations |
| B | Sells to a recipient who gave explicit consent through the operator’s consent register | Promotional voice call; robo-call | 140xx | Explicit consent verified directly from the recipient and recorded by the consent registrar (OTP-authenticated, sought from a 127xxx short code); delivered irrespective of category preferences, though the scrubbing rule still lists time-band and day-type checks | As row A | Revoked consent cannot be re-sought for 90 days |
| C | Calls your own customer about their warranty, recall, delivery or account | Service call (i) | 1600xx (BFSI, government; TRAI may exempt small BFSI players) or 1601xx (other sectors, phased in; first phase: utilities, logistics and courier services) | None; must contain no promotion | As row A if automated | Any upsell makes it promotional on the wrong series; today, complaints from 5 unique recipients in 10 days about promotional calls from a service series trigger the same suspension, 15-day bar and 1-year disconnection as row F (regulation 25(4)) |
| D | Helps a non-customer complete a purchase they are in the middle of | Service call (ii) | 1600xx or 1601xx | Explicit consent, valid 7 days | As row C | As row C |
| E | Confirms a transaction the customer just made | Transactional voice call | 1600xx or 1601xx | Within 30 minutes of the customer-initiated transaction | As row C | As row C |
| F | Sells from an ordinary 10-digit mobile, landline or SIP number with no sender registration | UCC by definition (unregistered sender) | None lawful | No gate makes it lawful | Not applicable | 5 complaints from unique recipients in 10 days: all resources suspended; first violation: barred 15 days; repeat: disconnected and blacklisted for 1 year |
| G | A salesperson speaks; AI only transcribes or prompts silently | Promotional voice call; not a robo-call | 140xx | As row A, with the voice-call mode (preference 11), or the auto dialer live-agent mode (preference 14) if software dials, in place of robo-calls | Regulation 4 notice if an auto dialer places the call; after the Third Amendment, an A2P declaration for any software-dialled call, live agent or not | As row A |
The matrix in one sentence: in India the question is never “is the AI allowed?” but “is this call on the right series, from a registered sender, to someone who has not blocked it?”, and only rows A, B and G may carry a sales pitch.
Two cells need care. The 10:00 to 21:00 default is Schedule-II, item 3, Note-1, which sets the bands before 10:00 and after 21:00 to off for every customer unless they switch them on. And row B’s consent override applies, in the regulations’ words, to preferences “under the applicable category”; Schedule-I’s scrubbing rule says consent overrides the recipient’s “choice of preference(s)” but still lists the time-band and day-type checks, so do not schedule consented calls into a switched-off band; the regulations do not say expressly how consent interacts with a block on the robo-call mode.
Planning AI outbound into India? Zian AI runs phone, SMS, email and WhatsApp sales agents in 30+ languages, with SmartReach AI™ orchestrating message, channel and timing by country, industry and profile. Zian is in partnership-application beta.
What happens if an AI calling campaign breaks the TCCCPR?
The sanctions fall mainly on your telecom connections, through your operator. A recipient complains to their own operator (the TRAI DND app, the operator’s app or portal, or a call or SMS to 1909) within seven days of the call, and the operator that supplied your number examines the call records.
For an unregistered telemarketer, regulation 25(5) and (6), as amended in 2025, apply. Complaints from five or more unique recipients in ten days trigger suspension of the outgoing services of all your telecom resources and a notice to represent. If the operator concludes you sent UCC:
- First violation: outgoing services of every resource allotted to you, including PRI and SIP trunks and SIMs, barred by all access providers for fifteen days, whether or not each was used.
- Later violations: all resources disconnected for one year, a place on the blacklist so no operator may give you new ones, and the devices used blocked for a year. You may keep one number with outgoing calls barred.
The operator must decide a representation within seven business days, with a further route to TRAI under regulation 29. Registered senders face a parallel complaint track and header and template sanctions; a registered sender making promotional calls from a service or transactional series faces the same five-complaint suspension, fifteen-day bar and one-year disconnection (regulation 25(4)); and operators may impose financial disincentives on registered senders and telemarketers, forfeit their security deposits, or suspend or blacklist them, where a violation is attributable to their failure to discharge their functions. For an AI calling stack, the phrase that matters is “all telecom resources”: one campaign’s breach can bar the SIP trunk your support line runs on. The Telecommunications Act, 2023 has its own penalty schedule, which we could not open from our network on 4 October 2026, so it is not summarised here.
What changes when the TCCCPR Third Amendment 2026 takes effect?
TRAI notified the Third Amendment Regulations, 2026 (5 of 2026) on 18 September 2026. They take effect thirty days after Gazette publication, except four provisions, including the A2P declaration and A2P termination charge, at sixty days, and the annexure’s complaint-handling items (the consumer appeal, corroborating complaints with AI-flag data, and blacklisting content templates registered in the wrong category) at ninety. TRAI’s copy does not show the publication date, but it cannot precede the notification, so as at 4 October 2026 none of it is in force, and none of it can take effect before 18 October 2026, or before 17 November 2026 for the A2P rules; the exact dates depend on the Gazette publication date, which we could not confirm.
- A defined A2P call. New regulation 2(ea): a voice call “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”.
- Declare before you dial. New regulation 4: every sender declares A2P calling and its CLI (caller line identification) ranges to its originating operator in advance, recorded on the DLT platform. An undeclared call “shall be treated as Unsolicited commercial communication”. It covers all A2P calls, not only commercial ones, which TRAI said prevents UCC “in the garb of transaction or service calling”.
- A per-minute charge. New regulation 35A: up to ₹0.05 a minute between operators for A2P calls, except from the 140xx, 1600xx, 1601xx or other designated series, and calls by or for TRAI or its authorised agencies.
- Faster triggers. Action against an unregistered sender at three complaints in ten days if any of its numbers is also flagged by an operator’s AI/ML system as a “Suspected high probability UCC CLI”, or five without the flag. Five flagged numbers of one sender in ten days start graded action, from KYC re-verification up to the one-year measures.
- Narrower relationships. An inquiry supports a relationship for seven days, and only if written or digital and kept verifiably; the twelve-month purchase and social-reasons limbs are gone, though TRAI says existing customers remain covered by inferred consent for the duration of their contract. An application still counts for three months.
- Legacy consents and restoration. Consent obtained by verifiable means outside the consent framework counts once registered. TRAI’s existing power to order barred resources restored at ₹5,000 each (each DID on a SIP or PRI trunk counts separately), capped at ₹5 lakh, stays; the amendment extends it to telemarketers, makes restoration subject to feasibility, and sets a floor of half the full charge for partial restoration.
TRAI’s reason, from its explanatory memorandum: in April 2026, 15,736 of 20,591 disconnections for these violations (approximately 75%, in TRAI’s words) were SIP or PRI connections used for A2P calling. It also conceded the network “may not be able to differentiate” between “voice of an actual human interacting on call and a pre-recorded or artificially generated human voice”, so the A2P regime rests on the sender’s own declaration. An undeclared AI calling stack is the exposed one.
Does the DPDP Act apply to AI cold calling in India?
In scope, yes; in force for the parts that matter, not yet. Section 3(b) extends the DPDP Act to processing outside India “in connection with any activity related to offering of goods or services to Data Principals within the territory of India”, so a lead list processed abroad for Indian prospects is covered. Section 3(c)(ii) excludes personal data made publicly available by the person themselves or by someone legally obliged to publish it.
Notification G.S.R. 843(E), in the Gazette of 13 November 2025, commences sections 3 to 5, section 6 except sub-section (9), and sections 7 to 17 (grounds, notice, consent, legitimate uses) eighteen months later, on 13 May 2027. The DPDP Rules, 2025 (G.S.R. 846(E)) match: rule 3 on notices at eighteen months, rule 4 on consent managers at one year.
From 13 May 2027, section 4 allows processing only with consent or for a section 7 legitimate use, and section 6(1) requires consent to be “free, specific, informed, unconditional and unambiguous with a clear affirmative action”. Section 7(a) covers data a person voluntarily provided for a specified purpose; it does not obviously cover a purchased list. Penalties reach ₹250 crore for security-safeguard failures and ₹50 crore for breaches not specifically listed.
TCCCPR consent and DPDP consent are different things: the Third Amendment, once in force, limits TCCCPR “consent” to permission to open a channel for commercial communications and says nothing in the regulations exempts a sender from the DPDP Act. A scrubbed 140xx call can be lawful under the TCCCPR and, from May 2027, still need a DPDP basis. For the Spam Act, TCPA and GDPR equivalents, see our AI outreach compliance overview across Australia, the US and the UK.
Status as at 4 October 2026: what is in force and what is coming
| Instrument | Made | Status as at 4 October 2026 | What it means for an AI calling plan |
|---|---|---|---|
| TCCCPR 2018 (6 of 2018), consolidated by TRAI on 21 May 2026 | 19 July 2018 | In force | Sender registration, 140xx/1600xx/1601xx routing, preference register, consent register, robo-call definition |
| TCCCPR (Second Amendment) Regulations, 2025 (1 of 2025) | 12 February 2025 | In force (30 days after Gazette publication; some parts 60 days) | Written advance notice of auto dialer or robo-call use; 15-day bar and 1-year disconnection for unregistered senders; 7-day complaint window |
| TCCCPR (Third Amendment) Regulations, 2026 (5 of 2026) | 18 September 2026 | Notified, not yet in force: 30 days after Gazette publication; A2P rules 60 days; annexure complaint items 90 days | A2P definition naming artificial voice; declaration of CLI ranges; ₹0.05 a minute off-series charge; AI/ML-flag triggers; 7-day inquiry window |
| DPDP Act, 2023: Board and definitions (sections 1(2), 2, 18 to 26, 35, 38 to 43, 44(1) and (3)) | 11 August 2023; G.S.R. 843(E), 13 November 2025 | In force since 13 November 2025 | Data Protection Board provisions in force; no new obligation on callers yet |
| DPDP Act: consent managers (section 6(9), 27(1)(d)); DPDP Rules rule 4 | 13 November 2025 | Commences 13 November 2026 | Consent-manager registration opens |
| DPDP Act: sections 3 to 5, 6 (except (9)), 7 to 17, 27 (except (1)(d)), 28 to 34, 36, 37, 44(2); DPDP Rules rules 3, 5 to 16, 22, 23 | 13 November 2025 | Commences 13 May 2027 | Consent or legitimate use for lead data; notice rules; penalties |
In sequence: the telecom rules bind every AI sales call today, the Third Amendment tightens them for A2P traffic from late 2026, and data protection arrives in May 2027.
How to check an AI calling plan against India’s rules
- Classify each call type. Any promotion of a product, service, supplier or opportunity makes it promotional.
- Register as a sender with an access provider on its DLT platform, and check any outside platform placing calls for you is a registered telemarketer (regulations 3 and 32).
- Get the right numbers: 140xx for promotion; 1600xx (BFSI, government; TRAI may exempt small BFSI players) or 1601xx (other sectors, being phased in from utilities, logistics and courier services) for service and transactional calls. Never sell from 10-digit numbers or ordinary SIP DIDs.
- Notify robo-call use to your originating operator in writing, in advance, with its objective; after the Third Amendment commences, declare A2P calling and CLI ranges.
- Scrub every list against the preference register for full blocks, category, mode (all modes or robo-calls), time band and day type, or hold explicit consent in the consent register.
- Constrain the agent. Agents on 1600xx or 1601xx numbers must not pitch; put that in the prompt and the test set.
- Record your data basis for each lead, ready for 13 May 2027.
The do-it-yourself cost is administrative, not technical: registration, series allocation, the declaration and a scrub before every campaign. At volume it is the scrubbing and complaint handling, because a 7-day complaint window and a 10-day counting window mean one badly targeted list can trip the threshold inside a single campaign. If you also call the US, see whether AI cold calling is legal in the US under the TCPA.
Frequently asked questions about AI cold calling in India
Is AI cold calling illegal in India?
No, but it is legal only inside TRAI’s Telecom Commercial Communications Customer Preference Regulations, 2018. An AI sales call is a promotional voice call and, by the regulations’ own definition, a robo-call: it needs a registered sender, a 140xx number, a recipient who has not blocked it or gave explicit registered consent, and advance written notice to your operator. See TRAI’s consolidated TCCCPR text of 21 May 2026.
Is cold calling illegal in India for human salespeople too?
Not illegal, but the same rules apply. Regulation 3 allows commercial calls only from registered headers or the special commercial number series, and an unregistered sender may not make commercial calls at all. A seller on a personal 10-digit mobile is an unregistered telemarketer, AI or not.
Does an AI voice agent count as a robo-call under TRAI rules?
On the text, yes. Regulation 2(bc) defines robo-calls as calls using “an artificial or prerecorded voice to interactively deliver a voice message without the involvement of human being on calling side for participating in the dialogue”. A fully autonomous agent meets all three parts. If a person on your side joins the dialogue, it arguably is not one, but it is still promotional if it sells.
Can my AI agent call business numbers in India without consent?
The regulations’ definitions of commercial communication and recipient turn on the telephone number and the content, not on whether the person is a business, and we found no business-to-business exemption in them. Treat an office mobile like any other number: 140xx series, preference scrubbing, or explicit consent.
Does the DPDP Act stop AI cold calling in India today?
Not yet. As at 4 October 2026, its consent and notice provisions, sections 4 to 7, commence on 13 May 2027 under notification G.S.R. 843(E) of 13 November 2025. From then, using a lead’s personal data needs consent or a section 7 legitimate use, and fines for breaches not specifically listed reach ₹50 crore.
What changes for AI calls under the TCCCPR Third Amendment 2026?
Notified on 18 September 2026, it defines A2P calls to include artificial voice technology, requires senders to declare A2P calling and CLI ranges to their operator in advance, treats undeclared A2P calls as unsolicited, and allows a charge of up to ₹0.05 a minute outside the designated series. None of it is in force as at 4 October 2026. See TRAI press release 119 of 2026.
Running AI sales across several countries? Zian AI’s phone, SMS, email and WhatsApp agents work in 30+ languages and integrate with HubSpot, Salesforce, HighLevel and Zapier. Zian is in partnership-application beta.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Robo-call and auto dialer call definitions; commercial communication (4 limbs); promotional, service (7-day explicit consent), transactional (30 minutes) and UCC definitions; regulations 3, 4, 9, 32 | TRAI, consolidated TCCCPR 2018 (as at 21 May 2026) | trai.gov.in CA_21052026.pdf | 4 October 2026 |
| Default-off time bands (00:00–10:00, 21:00–24:00); robo-call mode preference 15; categories 1–8; 90-day wait to re-seek revoked consent; 127xxx consent short code | TRAI, consolidated TCCCPR 2018, Schedules I and II | trai.gov.in CA_21052026.pdf | 4 October 2026 |
| 7-day complaint window; 5 complaints in 10 days; 15-day bar; 1-year disconnection and blacklist; 7 business days for representations; 12-month and 3-month relationship windows; ₹5,000 per resource restoration charge, ₹5 lakh cap; promotional calls from a service series (regulation 25(4)) | TRAI, TCCCPR (Second Amendment) Regulations, 2025, and consolidated text | trai.gov.in Regulation_12022025.pdf | 4 October 2026 |
| Third Amendment dated 18 September 2026; 30/60/90-day commencement; A2P definition; ₹0.05 a minute; 3 complaints plus AI flag; 5 flagged numbers in 10 days; 7-day inquiry window; half-charge floor for partial restoration | TRAI, TCCCPR (Third Amendment) Regulations, 2026 | trai.gov.in Regulation_18092026.pdf | 4 October 2026 |
| 1601xx phased in, first phase utilities, logistics and courier services under a Direction of 10 August 2026; 1600xx need not be mandated for all BFSI entities; regulation 3(1) proviso (classes of senders) | TRAI, explanatory memorandum to the Third Amendment, item 6, B.ii–B.iv | trai.gov.in Regulation_18092026.pdf | 10 October 2026 |
| 140xx, 1600xx and 1601xx series allocation; 15,736 of 20,591 disconnections (approximately 75%) in April 2026; live-agent exclusion rejected | TRAI, explanatory memorandum to the Third Amendment | trai.gov.in Regulation_18092026.pdf | 4 October 2026 |
| 1909 and DND app complaint routes; draft of 13 March 2026 | TRAI, Press Release No. 119 of 2026 | trai.gov.in PR_No119of2026.pdf | 4 October 2026 |
| DPDP Act sections 3, 4, 6(1), 7(a); Schedule penalties ₹250 crore and ₹50 crore; enacted 11 August 2023 | Parliament of India, via India Code | indiacode.nic.in a2023-22.pdf | 4 October 2026 |
| DPDP commencement: 13 November 2025, 13 November 2026, 13 May 2027 (G.S.R. 843(E)) | Ministry of Electronics and IT, Gazette of India No. 757 (eGazette CG-DL-E-14112025-267647) | egazette.gov.in 267647.pdf | 4 October 2026 |
| DPDP Rules commencement (rules 3 and 4; G.S.R. 846(E), 13 November 2025) | Ministry of Electronics and IT, Gazette of India No. 760 | meity.gov.in DPDP Rules Gazette | 4 October 2026 |
General information as read on 4 October 2026, not legal advice; for a specific campaign, ask an Indian telecom or privacy lawyer.