TRAI and DLT rules for AI voice calls in India: a compliance guide

The framework: TCCCPR 2018 and the DLT platform

The rules governing commercial calling and messaging in India come from the Telecom Commercial Communications Customer Preference Regulations, 2018, known as TCCCPR, along with its subsequent amendments. TRAI enforces this framework through a Distributed Ledger Technology, or DLT, platform, which is a shared, blockchain-based registry that telecom operators use to verify that a call or message comes from a registered, legitimate business rather than an unregistered source.

Six DLT platforms are TRAI-approved, run by the major telecom operators and a small number of dedicated providers. A business does not need to register on all of them, but it does need to register on at least one before it can legally place commercial calls or send commercial messages at scale in India.

What registration actually involves

There are three separate registration steps, and skipping any one of them is what puts a business in violation, even if the other two are done correctly.

• Principal Entity (PE) registration: the business itself registers as the entity responsible for the calls or messages it sends.
• Telemarketer registration: the entity actually placing the calls, whether that is the business itself or a third-party calling service, registers as the telemarketer.
• Header and template registration: for calls, this includes registering the specific numbering series used; for messages, it includes registering the sender header and the approved message templates.

The numbering series: 140 for promotional, 160 for transactional

India assigns different phone number series based on call type, and using the wrong series is itself a compliance failure independent of anything else being correct. Promotional or marketing voice calls must originate from numbers in the 140 series. Transactional or service calls, meaning calls tied to a transaction the customer already initiated, such as a delivery confirmation or an OTP call, use the 160 series.

This distinction matters for AI voice agents specifically, because an AI system that places outbound calls needs to be configured to originate from the correct series for the type of call it is making, and that configuration has to match what was registered on the DLT platform for that use case.

DND scrubbing and consent

Numbers on the National Do Not Disturb registry must be excluded from promotional calling and messaging. This scrubbing has to happen before a campaign runs, not as an afterthought, and it applies regardless of whether the call is placed by a human agent or an AI system.

Industry guidance for 2026 also points toward disclosing that a call involves AI and capturing consent that can be revoked, though this specific guidance is advisory rather than a confirmed statutory requirement as of this writing. Treat it as good practice regardless: an AI voice call that does not identify itself as AI when asked is a trust problem even where it is not yet a strict legal one.

Enforcement has escalated in 2026

TRAI has moved from largely manual enforcement to automated, AI and machine-learning-based detection of Unregistered Telemarketers. Reported figures put disconnections in the tens of thousands in a single quarter of 2026 alone, which signals that enforcement is active and fast, not a slow bureaucratic process that gives a business time to fix problems after the fact.

The practical takeaway is that registering after launch, or treating registration as something to handle once volume justifies it, is a materially riskier posture in 2026 than it might have been a few years earlier.

The distinction that matters most: outbound calling versus a website voice agent

This is the point businesses evaluating an AI voice agent get wrong most often. A voice agent embedded on your website, where a visitor clicks a button to start a conversation, is not outbound telemarketing. The visitor initiated the interaction, no phone number was dialled, and no DLT registration, numbering series, or DND scrubbing applies, because none of the regulated activity, which is placing a call to a phone number, actually happened.

The regime described in this guide applies specifically to dialling Indian phone numbers, whether for promotional or transactional purposes. If your AI voice use case is inbound or browser-based, meaning a person chooses to talk to it rather than being called, you are generally outside TCCCPR's scope. The moment a system starts placing outbound calls to phone numbers, even for a seemingly benign purpose like an appointment reminder, the full registration regime applies.

Checklist before any outbound AI calling

Work through this before placing a single outbound AI call to an Indian number.

• Principal Entity registration completed on a TRAI-approved DLT platform.
• Telemarketer registration completed for whoever is actually placing the calls.
• Correct numbering series secured and configured: 140 series for promotional, 160 series for transactional.
• Call scripts and templates registered and approved where required.
• Numbers scrubbed against the National DND registry before any promotional campaign runs.
• A clear disclosure and consent approach in place for AI-originated calls.
• Confirmed that a browser-based, user-initiated voice agent is not being treated as if it needs this registration, since it is a different regulatory situation entirely.