TRAI Rules for AI Calling in India: The Compliance Guide Every Business Needs

Here is the one-line summary before the detail: AI calling is legal in India — spam is not, and the rules don't care whether a human or a machine dialled the number.

The Telecom Regulatory Authority of India (TRAI) regulates all commercial voice communication under its commercial-communications framework (the TCCCPR and its subsequent amendments). If your business makes outbound calls or runs promotional campaigns — with human telecallers or AI — these rules apply to you. Getting them wrong risks number disconnection, blacklisting of your business across operators, and financial penalties. Getting them right, on the other hand, is a genuine competitive advantage, because most of your competitors haven't bothered.

This guide covers what the framework actually requires, translated from regulatory language into operating decisions.

The two categories every call falls into

TRAI's framework distinguishes between two kinds of commercial communication, and everything downstream depends on which one your call is:

Transactional / service calls relate to an existing relationship or a transaction the customer initiated: appointment confirmations, order and delivery updates, payment reminders on an active account, responses to an enquiry the customer submitted. These are permitted to customers regardless of DND status, because the customer's own action created the context.

Promotional calls attempt to sell something to someone who hasn't asked: offers, upsells, new-product pitches. These are heavily restricted. They cannot be made to numbers registered on the DND (Do Not Disturb) registry, and even to non-DND numbers they must follow registration and timing norms.

The single most important compliance decision for an AI telecalling program is being honest about which bucket each campaign belongs to. A "payment reminder" that pivots into pitching a new plan is a promotional call wearing a transactional costume — and regulators treat it as such.

The number series: why your caller ID matters

TRAI has pushed businesses onto dedicated numbering series so that customers can identify who's calling before they answer:

• The 140 series is designated for telemarketing/promotional calls.
• The 160 series has been allocated for transactional and service calls from entities like banks, financial institutions, and other registered businesses.

Calling customers from a random 10-digit mobile number for business purposes is exactly the pattern TRAI has been cracking down on. A compliant AI calling setup uses properly assigned series numbers, which also improves answer rates over time — customers learn that 160-series calls are legitimate service calls, not spam.

DLT registration: the non-negotiable foundation

Before any commercial communication, your business must be registered as a Principal Entity on the DLT (Distributed Ledger Technology) platforms run by telecom operators, with your headers and content templates registered and approved. This applies to voice campaigns and the SMS/WhatsApp follow-ups that accompany them. It's a one-time process with modest fees, and we've written a step-by-step DLT registration guide covering it.

If a vendor offers to get you calling "today, no paperwork" — that's not a shortcut, it's a liability transfer. The penalties land on the entity in whose name the calls are made.

Consent: the line that separates outreach from spam

The direction of TRAI's amendments over the past two years is unambiguous: explicit, verifiable, digitally-recorded consent is becoming the standard for promotional communication. Practically, this means:

• Do call leads who filled your form, messaged your WhatsApp, clicked your ad, or gave you their number at your counter. Their action is the consent context — and call them fast, while the context is fresh.
• Do call your existing customers for service matters connected to what they bought.
• Don't buy databases. Don't scrape directories. Don't call "leads" whose origin you can't document. If you can't show where the number came from and why you're entitled to call it, don't dial it — with AI or without.

This is why a compliant AI telecaller is best deployed on warm workflows: speed-to-lead callbacks, confirmations, follow-ups, reminders. That's also where the ROI is highest, so compliance and profit point the same direction.

Timing, disclosure, and opt-out

Promotional calls are restricted to daytime hours (avoid early morning and night calling entirely — as a working rule, keep campaigns between 10 am and 9 pm, and tighter is safer). Every call should identify the business clearly at the start. AI-assisted calls should disclose that the caller is an AI agent — an honest open is emerging as regulatory expectation and it measurably reduces hang-ups compared to an AI pretending to be human and failing. And every customer must have a working way to opt out; that preference must be honoured immediately and permanently across your systems.

What enforcement looks like now

TRAI has tightened enforcement significantly, pushing telecom operators to act against unregistered telemarketers, disconnect numbers used for unsolicited commercial communication, and apply graded financial disincentives. Repeat violators face blacklisting that follows the business across all operators. Customer complaints via the 1909 DND service feed directly into this machinery. In short: the era of consequence-free spam calling in India is closing, which is precisely why building compliant from day one is cheaper than retrofitting later.

A practical compliance checklist for AI calling

1. Register as a Principal Entity on DLT; register headers and templates.
2. Use the correct number series for the call type (140 promotional / 160 transactional where applicable).
3. Classify every campaign honestly as transactional or promotional.
4. Scrub promotional lists against DND before every campaign — not once, every time.
5. Only call numbers with a documented consent trail.
6. Disclose AI, identify your business, offer opt-out on every call.
7. Keep call recordings and consent records — which brings data-protection duties under the DPDP Act; see our DPDP guide for call recordings.