Other A2P SMS regulations

India Adds AI-Based UCC Screening

For messaging operators, CPaaS providers, marketers, and compliance teams sending OTPs, transaction alerts, customer notifications, or automated calls to India, TRAI’s Third Amendment issued on September 18, 2026 moves commercial communications toward AI-assisted spam detection and stronger sender accountability. A sender linked to five or more flagged CLIs within ten days may face KYC re-verification, physical verification, outbound barring, or disconnection. The practical priority is now evidence-ready traffic governance, not template approval alone.

Published:10/29/2026 Updated:10/29/2026

1. Regulatory focus

On September 18, 2026, TRAI issued the Telecom Commercial Communications Customer Preference Third Amendment Regulations. The framework brings AI and machine-learning based suspected-UCC detection, complaint-triggered action, sender and telemarketer accountability, and misuse of headers and content templates into one enforcement model. Where five or more CLIs associated with a sender are flagged within ten days, the access provider may initiate KYC re-verification, physical verification, outbound barring, and, for repeated misuse, disconnection of telecom resources.

2. Business impact

The exposure is not limited to promotional SMS classified as UCC. OTPs, account alerts, and automated customer callbacks can also be affected when number pools, shared CLIs, or reseller traffic concentrate complaint signals under one sender. If a business cannot quickly produce sender KYC, consent records, template versions, message detail records, and complaint-handling evidence, traffic may be throttled or suspended before the operator completes a deeper review. Channel architecture therefore becomes part of regulatory risk control.

3. Operating recommendations

Build an auditable mapping between each sender, CLI, template, consent record, and delivery route; do not let unrelated brands or business lines share one sender identity. Retain the consent source, timestamp, template version, communication purpose, delivery outcome, and complaint disposition for every campaign. Add a rolling ten-day dashboard for flagged CLIs. If activity approaches the five-CLI threshold, pause high-risk traffic, isolate reseller-originated volume, and prepare an evidence package for the operator.

Frequently Asked Questions

Can Indian OTP traffic also be affected by AI-based UCC screening?
Yes. The framework targets commercial communication traffic and sender behavior, not only advertising copy. OTP traffic normally has a legitimate trigger, but it can still be flagged if the sender, CLI, template, or complaint history cannot be reconciled. Keep the authentication event, customer relationship, template version, and delivery logs for each OTP flow, and separate authentication traffic from marketing traffic at the sender level.
Why can shared number pools increase compliance risk in India?
Operators may evaluate complaints and suspected abuse across a sender and its associated CLIs. When several brands share the same pool, poor-quality traffic can be aggregated and attributed to the same sender. Segment CLIs by brand, use case, and reseller, and maintain a mapping from each number to its template, customer flow, and route. This allows the business to isolate the source instead of losing the entire account.
What should a team do when it approaches the five-CLI threshold?
First pause new high-risk marketing or automated-call traffic and review every flagged CLI across the ten-day window, including brand, template, volume, complaint source, and reseller. Move essential OTP and transaction traffic to a verified dedicated sender where possible. Then prepare KYC documents, consent evidence, message detail records, and a remediation timeline for operator review before the threshold triggers broader restrictions.
This article is for informational purposes only and does not constitute legal advice.

Need compliance guidance?

Contact us for guidance on target markets, message scenarios, and sending routes.

Get in Touch
Privacy Policy