What Is the TCCCPR Third Amendment in 2026?
The Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 is TRAI's amendment to the TCCCPR, 2018, introduced on 18 September 2026. It changes how unsolicited commercial communication is detected and acted on: complaint-based action now requires corroboration from operator AI systems, application-driven calls are defined and regulated for the first time, inquiry-based messaging is capped at seven days, and header or template misuse carries a six-hour suspension duty.
If your business sends SMS, makes outbound calls, runs a dialer, or holds registered DLT headers in India, this is the regulation that now governs it. TRAI describes the intent as "strengthening consumer confidence in the commercial communication ecosystem, ensuring greater accountability across stakeholders, and enabling more effective and timely action against misuse of telecom resources by the spammers".
This guide summarises TRAI Press Release No. 119 of 2026 and the amendments it describes. It is not legal advice. Before you change a consent flow, a dialer configuration or a contract, confirm your own obligations against the text of the Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 or with counsel. Where the press release does not state a detail, this guide says so rather than filling the gap.
Why Did TRAI Amend the Spam Rules in 2026?
Because enforcement under the 2018 framework depended on consumer complaints alone, and TRAI concluded that complaints arrive too late and too rarely to catch a spammer early. The amendment pairs complaint data with the AI and machine learning detection that operators already run, so a sender can be identified before the complaint volume builds up.
The process behind it is documented and worth knowing, because it tells you these rules were negotiated rather than imposed overnight. TRAI issued the draft for consultation on 13 March 2026. Comments closed on 19 April 2026 and counter-comments on 4 May 2026. An Open House Discussion with stakeholders was held on 3 June 2026. The final amendment followed on 18 September 2026. A separate TRAI Direction of 27 February 2026 had already required operators to share AI and ML intelligence on suspected UCC between themselves, and the amendment folds that Direction into the regulations as Regulation 21A.
What Changes for Senders in 2026? The Eleven Salient Features
TRAI lists eleven salient features. Five of them change what a marketing or sales team does day to day, three change what your telecom provider is obliged to do about you, and three are structural powers TRAI has taken for later use. The table maps all eleven so nothing is missed.
| Salient feature | What the press release says | Who it binds |
|---|---|---|
| AI and ML based UCC detection | New Regulation 21A requires TSPs to identify sender CLIs with a high probability of being used for UCC and share that information among TSPs | Access providers, with consequences for senders |
| Regulation of A2P calls | A2P calls defined; every entity using them must pre-declare to its TSP with CLI details; undeclared A2P calls "will be treated as UCC" | Every entity making application-driven calls |
| Inquiry-based communication | Commercial communication on the basis of a customer inquiry is permitted "only for a period of seven days from the date of such inquiry" | Senders, especially e-commerce and e-service platforms |
| Consumer appeal mechanism | Consumers may appeal against the resolution of a UCC complaint within 15 days before the Appellate Authority | Consumers, with exposure for senders |
| Complaint-based action | Action triggers at "3 or more unique complaints within a period of ten days" where the CLI is also flagged by the AI and ML system | Senders |
| Expanded explicit consent | Consent definition expanded to include legacy consents, valid only where obtained through verifiable means and registered on the TSP Digital Platform | Senders holding historical consent records |
| Header and template misuse | Originating Access Provider must suspend misused headers or templates "within six hours of becoming aware of such misuse"; telemarketer misuse draws one year of disconnection plus blacklisting | Access providers, senders and telemarketers |
| Essential agreement conditions | TRAI may prescribe conditions that must mandatorily form part of agreements between access providers and senders or telemarketers | Access providers, senders, telemarketers |
| Classification of senders | TRAI may classify senders into categories and specify differentiated enforcement measures | All senders, by sector and scale |
| Call Management Application limits | CMAs prohibited from blanket blocking, filtering or spam tagging designated commercial series; CMA spam reports must flow to the DLT platform | Call management apps, benefiting compliant senders |
| VNO digital interface | Network Service Operators must give VNOs a real-time digital interface to the DLT platform | Network operators and VNOs |
How Does the New Complaint Trigger Actually Work in 2026?
It is a two-condition test, and most summaries state only half of it. The press release says action "will be triggered against the sender if there are 3 or more unique complaints within a period of ten days and the concerned Sender's CLI is also flagged by the AI/ML-based system as suspected of sending UCC". Both conditions must hold. The previous framework used a threshold of five or more unique complaints in ten days on its own.
Read plainly, that is not simply a drop from five complaints to three. It is a different mechanism. Three complaints alone do not trigger action if your CLI is not flagged. A flag alone does not trigger complaint-based action either. The practical consequence for a legitimate sender is that clean sending behaviour protects you from a small number of complaints, while a pattern that looks like bulk spam to an operator's classifier lowers your complaint tolerance to three.
There is a separate and parallel mechanism on the detection side. Where five or more CLIs associated with a sender are flagged within ten days, the press release says access providers will initiate "further investigation and graded action", which it lists as KYC re-verification, physical verification, barring of outgoing services, and disconnection of telecom resources in cases of repeated violations and misuse. TRAI also notes that certain timelines under the complaint mechanism have been revised, but the press release does not state the new timelines, so treat that as an open item to check in the regulation text.
One protection is worth knowing: the special numbering series designated for commercial communication, including the 140xx, 1600xx and 1601xx series, "shall not be flagged as suspected spam for recipients", so that legitimate commercial and government communication from regulated series is not inadvertently missed.
What Are A2P Calls Under the 2026 Rules, and Who Must Declare Them?
A2P calls are defined in the amendment as "voice calls initiated by an application, software system or automated platform without direct human dialing, including using autodialing, robo-calls and pre-recorded/artificial voice technologies". Every entity using them must pre-declare that use to its telecom service provider along with the details of the CLIs used. A2P calls made without that prior declaration "will be treated as UCC".
This is the single provision most likely to catch an otherwise compliant business by surprise, because the definition covers ordinary sales tooling. A predictive dialer, an IVR callback, an automated reminder call and a pre-recorded announcement all sit inside it. The declaration is an administrative step with your operator, not a technical restriction, but skipping it reclassifies your legitimate calls as unsolicited commercial communication by default. The section on the A2P rules covers the definition, the declaration and the termination charge in detail.
What Does Pre-Declaration Actually Require?
The press release states that "every entity using A2P calls must pre-declare such use to its TSP along with the details of CLIs to be used for making such calls", and that "A2P calls made without the required prior declaration will be treated as UCC". Two obligations sit in that sentence: declare the use, and declare the specific calling line identities.
The consequence of skipping it is the part worth internalising. Undeclared A2P calls are not merely non-compliant paperwork. They are treated as unsolicited commercial communication by default, which brings them inside the enforcement mechanisms in the rest of the amendment, including the complaint trigger and the graded action on flagged CLIs. A perfectly legitimate service call to a consenting customer can be reclassified as UCC purely because the declaration was never filed.
| Requirement | What the press release says | What it means operationally |
|---|---|---|
| Who must declare | "Every entity using A2P calls" | The entity using them, which includes brands, not only the vendor supplying the dialer. |
| To whom | "To its TSP" | Your telecom service provider, so the process is operator-specific. |
| When | "Pre-declare", before use | Declaration precedes calling. A retrospective filing does not cure the calls already made. |
| What detail | "The details of CLIs to be used" | A list of numbers, which means keeping it current as you add or retire lines. |
| If you do not | "Will be treated as UCC" | Your legitimate calls sit inside the spam framework by default. |
How Much Is the A2P Termination Charge, and Who Pays It?
The press release introduces "a termination charge of up to 0.05 per minute" on A2P calls, "to be levied by the Terminating Access Provider on the Originating Access Provider". TRAI describes the purpose plainly: it is there "to act as a deterrent".
Note carefully who is on each side of that transaction. The charge runs between telecom operators, not directly from TRAI to your business. Whether and how it reaches you depends on your commercial arrangement with your provider or your calling vendor. The honest answer for a marketing or sales leader is that this is a question to put to your operator or platform in writing, because the press release establishes the inter-operator charge and says nothing about pass-through.
There are stated exemptions. The press release says "A2P calls made through any numbering series designated by the Authority for regulated commercial calls, and Authority-authorized calls are exempted from termination charges". In practice that points toward the regulated commercial series rather than ordinary ten digit numbers, which is a structural argument for moving high-volume automated calling onto designated series.
Which of Your Systems Count as A2P?
More than most teams expect. The test is whether a human dialled the number, so the presence of a live agent later in the call does not take a system outside the definition. The table below applies the definition as written to the tooling Indian sales and support teams actually run.
| System | Inside the A2P definition? | Reasoning against the definition |
|---|---|---|
| Predictive or power dialer | Yes | The platform initiates the call without direct human dialing. |
| Auto dialer with live agent connect | Yes | Autodialing is named in the definition. The agent joins after initiation. |
| Pre-recorded promotional announcement | Yes | Pre-recorded voice technology is named explicitly. |
| IVR outbound reminder or OTP call | Yes, on the definition as written | Initiated by an automated platform. The press release draws no purpose-based exemption in the definition. |
| AI voice agent placing outbound calls | Yes | Artificial voice technology, initiated by software. |
| Click-to-call from a CRM record | Judgement call | A human initiates each call, but software places it. Ask your TSP how it treats this rather than assume. |
| Agent dialling manually from a handset | No | Direct human dialing, which the definition excludes. |
It does not distinguish service or transactional A2P calls from promotional ones in the definition, does not describe the format or channel of the declaration, does not state whether the declaration must be renewed, and does not address whether the charge is passed through to businesses. It also does not publish a commencement date for this provision separate from 18 September 2026. Those are questions for the regulation text, your operator, or counsel.
What Should a Sales or Support Team Do?
- Inventory every outbound calling path. Include the ones nobody thinks of as marketing: delivery notifications, appointment reminders, OTP fallbacks, collections calls, feedback surveys.
- Establish who the "entity using A2P calls" is for each path. If a BPO or a cloud telephony vendor places calls on your behalf, ask in writing whether they declared, what they declared, and under whose name.
- Get the CLI list right and keep it current. The declaration covers specific numbers. Adding a new line without updating the declaration reopens the exposure.
- Ask your operator about the termination charge in writing. Whether it reaches your invoice, and at what rate, is a commercial question the press release does not answer.
- Evaluate the designated series. Authority-designated numbering series for regulated commercial calls are exempted from termination charges, and under the same amendment cannot be blanket blocked or spam tagged by call management apps.
- Separate consent from automation. A declaration makes automated calling visible to the regulator. It does not substitute for a lawful basis to call that person.
Why Does the Definition Matter More Than the Charge?
Because the charge is small and the reclassification is not. Up to 0.05 per minute between operators is a rounding error against the cost of a call centre. Having every automated call you place treated as unsolicited commercial communication is a different order of problem, because UCC status is what connects your traffic to KYC re-verification, physical verification, barring of outgoing services and disconnection under the graded action provisions.
That asymmetry should shape where you spend attention. The termination charge is a commercial conversation with your operator. The definition is a compliance question you need to answer correctly for every system you run, because getting it wrong on a single undeclared CLI is what puts otherwise lawful calling inside the spam framework. Businesses that read this provision as a pricing change will do the easy part and miss the part that carries the consequence.
There is a second reason the definition deserves the scrutiny. TRAI has taken a power under the same amendment to classify senders into categories by criticality, sector, economic importance, scale and telecom resource usage, and to apply differentiated enforcement. A business whose automated calling is declared, traceable and on a designated series presents very differently from one whose calls are undeclared, whatever the intent behind them. The sender classification section covers the stated factors.
What Are the Common Mistakes?
- Assuming A2P means robocalls only. The definition covers any call initiated by an application or platform without direct human dialing, including dialer-driven calling with a live agent.
- Assuming the vendor declared it. The obligation falls on "every entity using A2P calls". Confirm in writing rather than presume.
- Declaring once and forgetting. The declaration includes CLI details, so new numbers need to be added.
- Treating service calls as automatically exempt. The definition as published does not carve out service or transactional purposes.
- Assuming the 0.05 per minute charge lands on you. It is levied by the terminating operator on the originating operator. Ask about pass-through.
- Reading the declaration as permission to call. It makes your automation visible. Consent or another lawful basis is separate.
- Filing retrospectively after an issue. The requirement is to pre-declare, so a late filing does not address calls already placed.
How Long Can You Message Someone After an Inquiry in 2026?
Seven days. The press release states that commercial communications may be sent on the basis of a customer inquiry "only for a period of seven days from the date of such inquiry". The inquiry itself "shall be made in writing or through digital means, and shall be maintained in a verifiable form by the Sender", and TRAI says the amendment is intended primarily to facilitate e-commerce and e-service platforms.
For any Indian lead generation operation this is the rule that changes process rather than paperwork. A form fill or a chat inquiry opens a seven day window, and it opens it only if you can produce the record afterwards. A long drip sequence that runs for weeks off a single inquiry no longer sits inside this provision. Our seven day rule guide works through what that means for follow-up cadence and record keeping.
What Happens If a Header or Template Is Misused in 2026?
The clock is six hours. Where headers or content templates are misused, the press release says the Originating Access Provider "shall suspend the misused Headers or Content Templates, within six hours of becoming aware of such misuse", and must issue a notice to the sender within the prescribed period. The sender is then required to undertake specified remedial measures to prevent further misuse and to file a complaint with the appropriate law enforcement agency.
Where the misuse is attributed to a telemarketer, the consequence is severe and stated plainly: "all its telecom resources across the TSPs will be disconnected for a period of one year, along with blacklisting". For a brand, the operational risk is that a suspended header takes your legitimate transactional messaging down with it. The header and template misuse section covers the sequence and what a sender is obliged to do.
What Is the Six Hour Suspension Clock, and Who Does It Bind?
It binds your telecom operator, not you. The obligation is on the Originating Access Provider to suspend the misused header or content template within six hours of becoming aware of the misuse. Your business does not get a six hour grace period to investigate, and you cannot negotiate the window. The operator acts and then notifies you.
That direction of travel is the part worth planning around. The first you may learn of a problem is that messaging under a header has stopped. If that header carries your OTPs, delivery notifications or payment confirmations, the suspension that protects consumers from a misused resource also takes down the transactional messaging your customers depend on.
| Step | What the press release says | Who acts |
|---|---|---|
| 1. Awareness | The clock starts when the Originating Access Provider becomes aware of the misuse | Access provider |
| 2. Suspension | Suspend the misused headers or content templates "within six hours of becoming aware of such misuse" | Access provider |
| 3. Notice | Issue a notice to the concerned sender "within the prescribed period" | Access provider |
| 4. Remediation | The sender "shall be required to undertake specified remedial measures to prevent any further misuse" | Sender |
| 5. Law enforcement | The sender must "file a complaint with the appropriate law enforcement agency" | Sender |
| 6. Telemarketer consequence | Where misuse is attributed to a telemarketer, "all its telecom resources across the TSPs will be disconnected for a period of one year, along with blacklisting" | Access providers, across all TSPs |
What Does the One Year Telemarketer Disconnection Mean?
For a telemarketer it is close to an existential outcome. The press release states that where misuse is attributed to a telemarketer, all its telecom resources across the TSPs will be disconnected for one year, along with blacklisting. Note the scope: across the TSPs, not with the operator where the misuse happened. Moving providers is not a route out.
For a brand that buys messaging through an aggregator or a telemarketing partner, this creates a dependency worth examining before it matters. If your messaging vendor is disconnected across all operators for a year, your messaging stops with it. The commercial question is whether you know who actually holds the telecom resources your campaigns run on, and whether you could move if that entity were blacklisted.
The press release does not publish an equivalent blanket consequence for senders who are not telemarketers. What it does specify for senders is the remediation duty and the law enforcement complaint. Do not read the absence of a stated penalty as an absence of exposure, because the amendment separately provides for graded action including barring of outgoing services and disconnection of telecom resources in cases of repeated violations and misuse.
How Should a Brand Prepare for a Six Hour Clock?
By deciding in advance who gets the call and what happens next. A six hour operator duty means the useful preparation is not faster investigation, it is faster continuity. The questions below are the ones most Indian brands cannot currently answer quickly, and all of them are answerable before an incident rather than during one.
- Who at your company receives an operator notice? If it goes to a shared inbox nobody owns, or to a former employee, you will learn about a suspension from customers instead.
- Which headers carry which traffic? Map every registered header to the message types it sends, so you know immediately what a suspension takes down.
- Do your critical and promotional messages share a header? If OTPs and marketing run under the same resource, a promotional misuse problem becomes a login problem.
- Who can authorise remedial measures? The duty to undertake them sits with the sender, so somebody needs the authority to act the same day.
- Who files the law enforcement complaint? This is an explicit sender obligation in the press release. Decide now whether it is legal, security or compliance.
- Who holds the telecom resources? If a partner does, understand your exposure to its blacklisting and whether you have an alternative path.
It does not define what constitutes misuse, does not specify the prescribed period for the operator's notice to the sender, does not enumerate the specified remedial measures, and does not state how misuse is attributed to a telemarketer as opposed to a sender. It also publishes no general penalty schedule for senders. Those are questions for the regulation text or counsel, and this guide does not guess at them.
What Does Header Hygiene Look Like in Practice?
It looks like knowing, without asking anyone, which of your registered resources are live, who can send through them, and what each one carries. Most Indian brands accumulate headers and templates over years, across agencies and vendors, and the register grows faster than anyone prunes it. A header nobody uses is still a header somebody could misuse, and the suspension consequence lands on your messaging either way.
| Practice | Why it matters under the 2026 rules |
|---|---|
| Maintain a current register of headers and templates | You cannot assess the impact of a suspension on traffic you have not mapped. |
| Retire headers and templates you no longer use | An unused but live resource is exposure with no corresponding benefit. |
| Keep a list of who can send through each resource | Attribution of misuse matters, and so does being able to answer quickly. |
| Separate critical from promotional traffic | A suspension on a promotional resource should not stop an OTP. |
| Review vendor and agency access on exit | Access that outlives a relationship is a common route to misuse. |
| Name the recipient of operator notices | The notice is what transfers the remediation duty to you. |
None of this is novel security practice. What the 2026 amendment changes is the cost of not having done it, because the response window belongs to your operator and the remediation duty lands on you with a notice you may not be watching for.
What Are the Common Mistakes?
- Assuming you get six hours. The six hours is the operator's deadline to suspend, not your window to respond.
- Running transactional and promotional traffic under one header. A promotional problem then becomes an OTP outage.
- Letting operator notices land nowhere. The notice is the mechanism that tells you remediation is now your obligation.
- Treating the law enforcement complaint as optional. The press release states the sender is required to file one.
- Not knowing whose telecom resources you use. A telemarketer blacklisting runs across all TSPs for a year and takes dependent messaging with it.
- Reading no stated sender penalty as no sender risk. Graded action, barring and disconnection exist elsewhere in the same amendment.
- Treating header security as an IT issue. The consequences land on messaging operations and customer experience first.
Is Legacy Consent Still Valid in 2026?
Conditionally, yes, and this is one of the few genuinely permissive changes in the amendment. TRAI has expanded the definition of consent to include legacy consents already held by entities, and says the framework is being amended to enable their recognition and digitisation. The condition is strict: legacy consents "shall be considered valid only where they have been obtained through verifiable means and are subsequently registered on the Digital Platform of the TSPs".
That is a data project, not a policy update. It asks a brand to prove how a historical consent was obtained and then to register it on operator infrastructure. Consent captured without a verifiable record does not become valid simply because it is old. Our legacy consent guide sets out what the two conditions mean for a CRM owner.
Why Can Call Management Apps No Longer Block 1600xx Calls in 2026?
Because TRAI concluded that blanket tagging by third-party apps was mislabelling legitimate and government communication as spam. Call Management Applications are now prohibited from blanket blocking, filtering or spam tagging calls from series designated for commercial communication, specifically 1600xx and 1601xx for service and transactional calls and 140xx for regulated promotional calls. Individual consumers keep full freedom to block or filter calls on their own devices.
There is a second obligation attached. No CMA may offer users the ability to report unsolicited commercial communication, "under any name such as spam, junk, etc.", unless the CMA sends that report to the DLT platform maintained by the access providers. For brands on regulated series this cuts both ways: fewer calls silently suppressed, and a wider net of reports feeding the system that can flag your CLI. The section on the CMA rules covers the brand-side implications.
Which Number Series Are Protected?
The press release names three series in the CMA provision, and a parallel protection elsewhere in the same amendment covers the same ground from the operator side.
| Series | Designated use per the press release | Protection in 2026 |
|---|---|---|
| 1600xx | Service and transactional calls | CMAs may not blanket block, filter or spam tag |
| 1601xx | Service and transactional calls | CMAs may not blanket block, filter or spam tag |
| 140xx | Regulated promotional calls | CMAs may not blanket block, filter or spam tag |
| All three | Special numbering series designated for commercial communications | Operator AI and ML systems "shall not be flagged as suspected spam for recipients" |
The operator-side protection comes from the AI and ML detection provisions. Special numbering series designated for commercial communications, including 140xx, 1600xx and 1601xx, "shall not be flagged as suspected spam for recipients", so that legitimate commercial and government communications from the regulated series are not inadvertently missed. A call on a designated series is therefore protected from blanket spam labelling at both the operator layer and the app layer.
What Freedom Do Consumers Keep?
All of it, at the individual level. The press release states that "individual consumers retain full freedom to block, or filter calls on their own devices". The prohibition targets blanket action by the app, not choices made by a person about their own phone.
That distinction matters for how a brand should read this rule. It does not guarantee that your 1600xx call reaches a customer. A customer who blocks your number personally has exercised a right the amendment preserves. What the rule removes is a third party deciding on the customer's behalf, across millions of devices at once, that your regulated series is spam.
Why Does the Reporting Rule Matter to Brands?
Because it widens the net that feeds enforcement. Before the amendment, a spam report filed inside a call management app could stay inside that app. Now a CMA may only offer spam or junk reporting if it sends those reports to the DLT platform maintained by the access providers. TRAI describes the purpose as facilitating "wider collation of data for action against spammers".
For a sender that cuts both ways, and both directions deserve attention. On one side, the regulated series gain protection from blanket tagging. On the other, reports that consumers file in popular apps now flow into the system that operators use, alongside their own AI and ML detection, to identify senders. Under the same amendment, action triggers against a sender at three or more unique complaints within ten days where the sender's CLI is also flagged by the operator's AI or ML system. More reporting channels feeding the platform means complaint patterns surface faster.
| Effect on a brand | Direction | What it means in 2026 |
|---|---|---|
| Calls on 140xx, 1600xx and 1601xx not blanket tagged by apps | Helps compliant senders | Legitimate regulated calls are less likely to be silently suppressed. |
| Calls on designated series not flagged as suspected spam by operators | Helps compliant senders | Operator-side warnings should not attach to regulated series. |
| App spam reports must reach the DLT platform | Raises exposure for poor practice | Consumer complaints made in apps now feed the regulated enforcement system. |
| Consumers can still block individually | Neutral | Your number can still be blocked by a person who does not want your calls. |
Should Your Business Move Calling Onto a Designated Series?
For high-volume service, transactional or regulated promotional calling, the 2026 amendment strengthens the case. Calls on designated series are now protected from blanket spam labelling by both operators and apps. Separately, the amendment states that A2P calls made through any numbering series designated by the Authority for regulated commercial calls are exempted from the new A2P termination charge of up to 0.05 per minute.
The protection is not a licence. A designated series carries the accountability of the regulated route: registration, consent and the complaint mechanism all still apply. What changes is that the cost of being on the regulated route now comes with its benefit intact. The A2P calls section covers the declaration requirement for automated calling.
It does not name specific call management apps, does not describe how compliance by CMAs will be monitored, does not state a penalty for a CMA that breaches the prohibition, and does not describe the technical format for routing CMA reports to the DLT platform. It also does not say whether a brand can raise a complaint if its designated series is blanket tagged. Those are questions for the regulation text or counsel.
What Should a Brand Do?
- List which of your calls run on designated series and which run on ordinary ten digit numbers. The protection applies only to the designated series.
- Check whether customers have reported your calls as spam. If you see suppression on a designated series, note it, because blanket tagging is now prohibited.
- Assume app-based complaints now count. Treat reports filed in popular caller apps as part of the complaint pattern the regulated system sees.
- Review automated calling against the A2P rules, because designated series also carry the termination charge exemption for A2P calls.
- Keep consent and lawful basis intact. The CMA rule protects regulated calls from blanket labelling. It does not make an unwanted call wanted.
What Evidence Should a Brand Keep?
Enough to show your calling was regulated and consented if a question arises. The press release does not describe a complaint route for a brand whose designated series is blanket tagged, so the useful preparation is internal rather than procedural.
- Which series each campaign or service flow used, so you can show a call ran on a designated series.
- The lawful basis for each contact, whether consent, a recognised legacy consent or an inquiry within its seven day window.
- A2P declarations and CLI lists, for any automated calling, since undeclared A2P calls are treated as UCC regardless of series.
- Answer and connection rates over time by series, so a sudden drop on a designated series is visible rather than anecdotal.
What Are the Common Mistakes?
- Assuming every call is now protected. The prohibition covers the designated series named in the press release, not ordinary mobile or landline numbers.
- Assuming customers cannot block you. Individual consumers retain full freedom to block or filter on their own devices.
- Ignoring app-based reports. CMAs offering spam reporting must now send those reports to the DLT platform.
- Reading protection as permission. A designated series removes blanket tagging, not the need for a lawful basis to call.
- Missing the operator-side protection. Designated series also cannot be flagged as suspected spam to recipients by operator AI and ML systems.
- Overlooking the A2P link. Designated series are exempted from the A2P termination charge, which affects the economics of automated calling.
How Might TRAI Classify Your Business in 2026?
Under a new regulation, TRAI may classify senders into different categories and specify differentiated enforcement measures for each. The press release lists the considerations: the criticality of the services and the sector a sender belongs to, the importance of the entity to the economy, scale of operations, extent of telecom resource usage, and the potential impact on consumers of suspending or disconnecting that sender's telecom resources.
No categories have been published in this press release. What has changed is that TRAI has taken the power to treat a bank, a hospital, a utility and a promotional D2C brand differently for the same violation. If your messaging carries genuine service criticality, that is worth documenting now rather than arguing later. The sender classification section works through the five stated factors.
What Are the Five Factors TRAI Lists?
The press release lists the considerations on which senders vary. They are the closest thing published to the criteria a classification would use.
| Factor, as listed by TRAI | What it asks about a sender | Who it likely distinguishes |
|---|---|---|
| Criticality of the services and the sector to which a sender belongs | How essential is what the sender communicates, and in which sector | Banking, healthcare and utilities versus purely promotional activity |
| Importance of the entity to the economy | How significant the sender is economically | Large systemically relevant entities versus small ones |
| Scale of operations | How large the sender's operations are | National operations versus local ones |
| Extent of usage of telecom resources by the sender | How much telecom capacity the sender uses | High-volume messaging and calling versus occasional use |
| Potential impact of suspending or disconnecting the sender's telecom resources on consumers | What consumers would lose if the sender went dark | Senders whose messages consumers depend on versus those they would not miss |
The right-hand column is interpretation, not regulation, and should be read that way. The press release lists the factors without saying how they combine, how they are weighted, or which categories result. What can be said with confidence is the direction each factor points.
What Could Differentiated Enforcement Mean in Practice?
The press release does not say, and this is the part most worth not inventing. It states that TRAI may specify differentiated sets of enforcement measures applicable to categories of senders for violations. It does not publish those measures, does not indicate whether critical senders would face lighter or heavier treatment, and does not describe any process by which a sender is placed in a category.
One reasonable reading, given that consumer impact of suspension is an explicit factor, is that TRAI wants room to avoid disconnecting senders whose messages consumers depend on. That reading is consistent with the stated reasoning. It is still a reading. A business should not plan on lenient treatment because it believes itself critical, and should not assume the opposite either. The honest position for 2026 is that the power exists and its use is not yet published.
It does not publish any categories, does not describe the enforcement measures for each category, does not explain how the five factors are weighted or combined, does not describe a process for a sender to be classified or to contest a classification, and does not give a date by which classification will happen. It describes a power TRAI has taken, not a scheme it has published.
How Should Different Kinds of Senders Prepare?
By documenting the facts that map to the five factors, because those facts are cheap to assemble now and hard to reconstruct under pressure. The point is not to argue a classification in advance. It is to be able to describe your messaging accurately if the question is asked.
| Sender type | What to document in 2026 |
|---|---|
| Banks, NBFCs, insurers | Which messages are transactional or security-critical, such as OTPs and payment alerts, and what customers lose if they stop |
| Healthcare providers | Appointment, result and care messages, separated from promotional health content |
| Utilities and telecom-dependent services | Outage, billing and service notices and their consumer reach |
| E-commerce and D2C brands | Order and delivery messaging separated from promotional campaigns, with volumes for each |
| Agencies and telemarketers | Which clients and sectors your traffic serves, because your telecom resource usage may span categories |
| Small and occasional senders | Low volume and narrow purpose, which also maps to the scale and usage factors |
Why Does Separating Traffic Types Help?
Because the criticality factor is about services, not about companies. A bank sends OTPs and also sends credit card offers. If both run under the same resources and something goes wrong with the promotional traffic, the consequence can land on the critical traffic. That is already true under the six hour header suspension rule in the same amendment, and classification makes the same logic structural.
Keeping critical and promotional traffic on separate headers, templates and, where it makes sense, separate designated series gives you two things. It limits the blast radius of any enforcement action. And it makes your messaging legible: anyone looking at your traffic can see which parts consumers depend on. The header and template misuse section covers the suspension mechanics, and the call management app section covers the designated series.
What Other Structural Power Did TRAI Take?
The power to prescribe essential conditions for agreements between access providers and senders or telemarketers. The press release explains that TSPs are obligated to ensure compliance by senders and telemarketers through contractual obligations, but that operators "many times do not put strict conditions in the agreements to ensure compliance by these entities, primarily due to competition issues". The new provision lets TRAI prescribe conditions "that must mandatorily form part of these agreements".
Read alongside classification, this signals where the framework is heading. TRAI is building the means to set enforcement by category and to fix minimum terms in the contracts that govern sender access. Neither has been published in detail yet. Both are worth knowing about before your next contract renewal with a messaging provider. The full amendment guide sets both powers alongside the operational rules.
What Should Agencies and Aggregators Take From This?
That their position is the hardest to describe and the most worth documenting. An agency or a messaging aggregator often carries traffic for banks, hospitals, retailers and promotional brands at once. Measured on extent of telecom resource usage, it may look large. Measured on criticality, its traffic is mixed. If classification is applied at the level of the entity holding the resources, a mixed portfolio could be categorised in a way that suits none of its clients.
The practical response is separation and records: keep client traffic attributable, keep critical and promotional streams distinct, and be able to show which clients and sectors each resource serves. Combined with the one year telemarketer disconnection that applies to header misuse, it is also a reason for brands to know exactly which entity holds the telecom resources behind their campaigns.
What Are the Common Mistakes?
- Assuming categories have been published. The press release describes a power TRAI may use, not a published scheme.
- Assuming critical status means leniency. The press release does not say which direction differentiated enforcement runs.
- Treating classification as company-level only. The criticality factor refers to services and sectors, which is why separating traffic types matters.
- Mixing OTPs with promotions on one resource. That exposes critical messaging to consequences triggered by promotional traffic.
- Ignoring the agreement conditions power. Mandatory contract terms may change what your messaging provider requires of you.
- Waiting for publication before documenting. Describing your traffic against the five factors is useful whatever the scheme turns out to be.
What Is the New Consumer Appeal Route in 2026?
Consumers can now appeal the resolution of a UCC complaint. The appeal may be preferred within 15 days before the Appellate Authority, and will be resolved under the Telecom Consumers Complaint Redressal Regulations, 2012. It can be filed through any mode available for lodging UCC complaints, which the press release lists as the TRAI DND App, the TSP app or portal, and a call or SMS to 1909, besides the modes specified under the TCCR Regulations.
For a brand the effect is duration. A complaint that is closed is no longer necessarily finished, because a further 15 day window exists in which the consumer can reopen the question. The appeal mechanism section covers what that means for complaint handling.
How Does a Consumer File an Appeal?
Through the same channels used to lodge a UCC complaint in the first place. The press release states the appeal "may be preferred through any of the modes available for lodging UCC complaints", which it lists, "besides the modes specified under TCCRR, 2012".
| Element | What the press release says |
|---|---|
| Who can appeal | Consumers, "against the resolution of UCC complaints" |
| Window | "Within 15 days" |
| Before whom | "The Appellate Authority" |
| Governing rules | Resolved "as per the Telecom Consumers Complaint Redressal (TCCR) Regulations, 2012" |
| Channel: app | The TRAI DND App |
| Channel: operator | The TSP's app or portal |
| Channel: call or SMS | Call or SMS to 1909 |
| Other channels | "Besides the modes specified under TCCRR, 2012" |
The choice of channels is deliberate. Using the existing complaint modes means no new behaviour for the consumer: anyone who can complain can appeal, in the same place, with the same app or the same short code.
What Does the Appeal Route Mean for a Brand?
Mostly, it means time. A complaint about your messages that has been resolved is no longer necessarily closed, because a further 15 day window exists in which the consumer can contest the resolution. The press release does not state from which event that 15 day period runs, so treat the precise start point as a question for the regulation text.
The practical consequence is that a brand's complaint position should be read over a longer horizon than before. A burst of complaints, a resolution, and then a period in which some of those could return through appeal is a different risk profile from a burst that simply closes. That matters more under this amendment than it would have before, because complaint-based action now triggers at three or more unique complaints within ten days where the sender's CLI is also flagged by the operator's AI or ML system.
It does not identify who the Appellate Authority is, does not state from which event the 15 day appeal window runs, does not say whether a sender is notified of or can participate in an appeal, and does not describe what outcomes an appeal can produce or how they feed back into complaint counts. It also notes that certain timelines under the complaint mechanism have been revised without stating the new timelines. Those are questions for the regulation text, the TCCR Regulations 2012, or counsel.
What Should Brands Do About Complaints?
Treat complaint prevention as the only reliable strategy, because the amendment has narrowed every other option. There is no procedure described in the press release for a brand to intervene in an appeal, so the useful work happens before any complaint is filed.
- Know your lawful basis for every contact. Consent, a recognised legacy consent, or an inquiry within its seven day window. Contacts with no basis generate complaints.
- Respect the seven day inquiry limit. Messaging past the window off a single inquiry is a predictable source of complaints.
- Declare automated calling. Undeclared A2P calls are treated as UCC under the same amendment.
- Make opting out easy and honour it fast. A customer who can stop your messages has no reason to complain about them.
- Watch for complaint clusters. If your customer support sees a run of "how did you get my number" contacts, treat it as an early warning rather than noise.
- Keep the records. If a complaint is resolved in your favour, the record of your lawful basis is what supported it, and an appeal may revisit it.
Why Does a 15 Day Window Change Complaint Handling?
Because it extends the period during which a complaint is live, and the complaint mechanism counts unique complaints within ten day windows. A brand monitoring its complaint exposure can no longer assume that a resolved complaint has left the picture. The press release does not describe how a successful appeal interacts with the complaint count, which is exactly why the conservative operating assumption is to treat appealable complaints as still relevant until the window has passed.
For most legitimate senders the effect will be small. Appeals require a consumer to disagree strongly enough with a resolution to act again, within 15 days, through the same channels. For senders operating close to the line, the appeal route removes one of the ways a complaint could quietly go away. The full amendment guide sets this alongside the other changes, and the seven day rule guide covers the most common source of avoidable complaints.
What Should Customer Support Teams Change?
Their role in spotting complaints before they reach the regulated channels. Most consumers who end up complaining to 1909 or through the TRAI DND App have usually signalled their irritation somewhere first: a reply asking to stop, a question about where you got their number, an angry message to support. Those signals arrive in your systems before they arrive in TRAI's.
| Signal in your own systems | What it may indicate in 2026 | Response |
|---|---|---|
| "How did you get my number?" | No lawful basis the customer recognises | Check the basis for that contact and the source it came from. |
| Repeated STOP or unsubscribe replies | Opt-out not being honoured quickly enough | Audit opt-out processing time across every channel. |
| Complaints that arrive weeks after an inquiry | Messaging past the seven day inquiry window | Cap inquiry-based sequences at seven days from the inquiry date. |
| Complaints about unexpected automated calls | Possible undeclared A2P calling | Confirm A2P declarations and the CLI list with your TSP. |
| A sudden cluster from one campaign | A list or targeting problem | Pause the campaign and check its source before it repeats. |
None of this requires knowing the internal mechanics of the appeal process, which the press release leaves undefined. It requires treating your own support inbox as the earliest available warning, because under the 2026 rules the gap between a few irritated customers and an enforcement trigger is narrower than it was.
What Are the Common Mistakes?
- Treating a resolved complaint as closed. A consumer may appeal the resolution within 15 days.
- Assuming you will be notified of an appeal. The press release does not describe sender notification or participation.
- Assuming the appeal window runs from a fixed event. The press release does not state the start point.
- Reading the trigger as three complaints alone. It is three or more unique complaints in ten days and an AI or ML flag on the CLI.
- Relying on the regulatory process to clear your name. Prevention is the only part of the process a sender fully controls.
- Ignoring complaints made through caller apps. CMAs offering spam reporting must now send those reports to the DLT platform.
What Should a Marketing Team Do This Week in 2026?
Six things, in this order. None of them require a legal opinion to start, and all of them are cheaper to do now than to retrofit after an operator notice.
- Inventory your outbound calling. List every system that places calls without a human dialing each one: predictive dialers, IVR callbacks, automated reminders, pre-recorded announcements. Each is a candidate for A2P pre-declaration with your TSP.
- Find out whether the declaration has been filed. If your calling runs through a vendor or a call centre, ask in writing who declared what, and get the CLI list.
- Audit your inquiry records. For every lead source, establish whether the inquiry exists in writing or digital form and whether you could produce it in verifiable form on request.
- Re-cadence inquiry-based follow-up to the seven day window, and move anything longer onto a consent basis rather than an inquiry basis.
- Check how your legacy consent was captured, and whether the capture method would count as verifiable. Then ask your operator about registering it on the Digital Platform.
- Assign an owner for header and template monitoring, because a six hour suspension duty on your operator means your response time has to be shorter than that.
What Are the Common Mistakes in 2026?
- Reading the trigger as "three complaints". It is three or more unique complaints in ten days and an AI or ML flag on the CLI. Stating only the first half overstates your risk in one direction and understates it in the other.
- Confusing the two thresholds. Three unique complaints in ten days is the complaint trigger. Five or more flagged CLIs in ten days is the detection trigger for graded action. They are separate provisions.
- Assuming A2P only means robocalls. The definition covers any call initiated by an application or platform without direct human dialing, which includes ordinary dialer-driven sales calling.
- Treating an inquiry as open-ended consent. Seven days, with a record you can produce.
- Assuming old consent is safe because it is old. Validity depends on verifiable capture and registration on the TSP Digital Platform.
- Leaving header monitoring to the operator. The six hour duty sits with the access provider, but the remedial measures and the law enforcement complaint sit with the sender.
- Waiting for penalties to be spelled out. The press release states consequences for telemarketer header misuse and graded action on detection. It does not publish a general penalty schedule, and the absence of one is not an absence of exposure.
Key Takeaways for 2026
The 2026 amendment moves Indian spam enforcement from complaint-led to detection-led, and it attaches specific, short clocks to the things that go wrong.
- Introduced 18 September 2026 as the Third Amendment to the TCCCPR, 2018, after a consultation that ran from 13 March 2026 to an Open House Discussion on 3 June 2026.
- Complaint-based action now triggers at three or more unique complaints in ten days, but only where the sender's CLI is also flagged by the operator's AI or ML system.
- Five or more flagged CLIs in ten days triggers investigation and graded action including KYC re-verification, physical verification, barring of outgoing services and disconnection.
- A2P calls are defined and must be pre-declared to your TSP with CLI details. Undeclared A2P calls are treated as UCC.
- Inquiry-based commercial communication is capped at seven days and requires a verifiable written or digital record of the inquiry.
- Legacy consent is recognised only where it was obtained verifiably and is registered on the TSP Digital Platform.
- Misused headers or templates must be suspended by the originating access provider within six hours; telemarketer misuse draws one year of disconnection across all TSPs plus blacklisting.
- Consumers get 15 days to appeal a UCC complaint resolution, so a closed complaint is not always a finished one.
- The 140xx, 1600xx and 1601xx series cannot be flagged as suspected spam to recipients, and call management apps cannot blanket block or tag them.
Distk works with brands and agencies across India on the operational side of this: mapping which systems now need an A2P declaration, rebuilding inquiry-based follow-up to fit a seven day window with records that survive scrutiny, and assigning ownership for header monitoring. If you send SMS or make outbound calls in India, that audit is where we would start.
Sources
- TRAI Press Release No. 119 of 2026, "TRAI Strengthens Framework for Curbing Unsolicited Commercial Communications through Technology-Driven Enforcement and Enhanced Consumer Protection", 18 September 2026. Every rule, date, number and quotation in this guide comes from that press release.
- TRAI press release listing, which carries the dated entry and the source PDF.