TRAI Commercial Communication Rules 2026: What Businesses Need to Know
Quick note
Below is the official summary and the reference document preview. Use “Open PDF” for full screen view.
Schedule a Call Back
Summary
Businesses that rely on automated calls, bulk messaging, telemarketing vendors, DLT platforms, or large pools of business numbers now have a much wider set of TRAI requirements to review.
The Telecom Regulatory Authority of India notified the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, Regulation No. 05 of 2026, on 18 September 2026. These regulations amend the earlier Telecom Commercial Communications Customer Preference Regulations, 2018 and apply throughout India.
The change is much broader than a small amendment to spam-call rules. It deals with automated A2P voice calls, consent, service communication, AI/ML-based spam identification, sender KYC, header and content-template misuse, consumer complaints, telecom-resource blocking, third-party caller-ID applications and 1909 preference settings.
There is also no single start date for every provision. Most parts begin after 30 days from publication in the Official Gazette, some begin after 60 days, and specific Annexure-listed amendments begin after 90 days.
For businesses, the practical question is simple: Which part of the amended framework applies to the way the business currently calls or messages customers?
TRAI Third Amendment Regulations 2026 at a Glance
| Particular | Details |
| Issuing authority | Telecom Regulatory Authority of India |
| Regulation | Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026 |
| Regulation number | 05 of 2026 |
| Date | 18 September 2026 |
| Parent regulations | Telecom Commercial Communications Customer Preference Regulations, 2018 |
| Legal basis | TRAI Act, 1997 |
| Territorial coverage | Entire India |
| General commencement | After 30 days from Gazette publication |
| Certain provisions | After 60 days |
| Annexure-listed provisions | After 90 days |
| Main areas covered | A2P calls, consent, spam detection, DLT, KYC, complaints, telemarketers, templates, caller-ID apps |
| Main business audience | Senders, Principal Entities, telemarketers, Access Providers, VNOs and businesses using automated communication |
The staggered implementation makes internal mapping important. A business should not assume that every new duty becomes operational on the same day.
What Are the TRAI Commercial Communication Rules 2026?
The 2026 amendment does not replace the existing 2018 commercial communication framework. Instead, it changes and expands several parts of it.
The earlier framework already governed areas such as:
- commercial SMS,
- promotional calls,
- consumer choice registration,
- sender registration,
- telemarketing activity,
- controls based on DLT,
- headers,
- content templates, and
- complaints about unsolicited commercial communication.
The 2026 amendment adds more detail in areas where communication technology and spam-control methods have changed.
For example, automated voice calling is now expressly recognised through a new definition of Application-to-Person call, or A2P call. AI-based detection systems are connected more directly with enforcement. The regulations also establish stronger procedures where a registered header or template is misused.
This means the amendment affects both the communication itself and the technology, records, and vendors behind it.
Regulatory Framework Behind the Amendment
The Third Amendment has been issued under the powers available to TRAI under the Telecom Regulatory Authority of India Act, 1997.
It amends the Telecom Commercial Communications Customer Preference Regulations, 2018.
The regulation also updates references to the older Indian Telegraph Act and uses definitions from the Telecommunications Act, 2023, in relevant places.
Another important point is the relationship between these TRAI rules and the Digital Personal Data Protection Act, 2023.
The regulation makes it clear that compliance with the commercial communication consent framework does not exempt a sender from obligations or liability under the DPDP Act.
So, for a business, “we have TRAI consent” should not be treated as a blanket answer to every personal-data question.
Who Is Likely to Be Affected?
The amendment touches several parties, but not every party has the same responsibility.
| Stakeholder | Why the Amendment Matters |
| Senders | A2P declaration, consent, CLI use, complaints, spam flagging |
| Principal Entities | DLT records, headers, templates, telemarketer access |
| Registered Telemarketers | Correct use of registered resources and campaign infrastructure |
| Unregistered Telemarketers | Complaint thresholds and enforcement |
| Originating Access Providers | Investigation, KYC, DLT recording and enforcement |
| Terminating Access Providers | Spam detection and complaint handling |
| Virtual Network Operators | Access to necessary DLT-linked digital interfaces |
| Call-management applications | Spam-reporting and designated-number treatment |
| Consumers | 1909 preferences, complaints and appeals |
| Businesses using automation | A2P calling and CLI declaration requirements |
A company does not need to be a telecom operator to be affected. A bank, retailer, fintech, e-commerce company, insurance company, or BPO may still fall within the framework as a sender.
When Do the New Rules Start Applying?
TRAI has divided implementation into separate periods.
General 30-Day Commencement
The general rule is that the regulations come into force after 30 days from publication in the Official Gazette.
60-Day Commencement
Certain provisions receive a longer period.
These include Regulation 4, Regulation 6, Regulation 8(a) and Regulation 18.
These provisions relate to important operational matters such as:
- A2P call declarations,
- VNO digital interfaces,
- header/content-template misuse, and
- A2P termination charges.
90-Day Commencement
The amendments listed in the Annexure come into force after 90 days.
The Annexure includes specific changes relating to the appeal mechanism, corroboration of complaint data with AI-flagged sender data, and certain content-template categorisation consequences.
Why This Matters for Businesses
A compliance team should prepare a provision-wise implementation calendar.
Using only one “TRAI amendment effective date” can create mistakes because different obligations start at different times.
What Has Changed Under the 2026 Amendment?
The amendment makes changes across several areas at once.
| Area | What Changed |
| A2P calls | New definition and advance declaration requirement |
| Consent | Meaning and treatment of consent revised |
| Explicit consent | Verification and registration approach expanded |
| Relationship | Enquiry and application periods clarified |
| Service communication | Scope revised and examples added |
| Spam control | AI/ML-based detection linked with enforcement |
| KYC | Network-wide sender identification introduced |
| Headers/templates | Strict remedial process after misuse |
| Complaints | Regulation 25 substantially revised |
| Call-management apps | New restrictions and DLT-reporting requirements |
| A2P charges | New terminating charge provision |
| Consumer preferences | BLOCK PROMO and revised 1909 mechanisms |
The business impact will depend on whether the organisation sends promotional communication, service communication, A2P calls, or a combination of these.
What Is an A2P Call?
A2P means Application-to-Person.
Under the amended regulation, an A2P call is a voice call initiated by:
- an application,
- software,
- an automated platform,
- without direct human dialling and delivered to an individual telecom subscriber.
The definition includes:
- auto-dialling,
- robocalls,
- pre-recorded voice, and
- artificial voice technology.
This is wider than the common idea of a “spam robocall”.
A bank's automated reminder system, an e-commerce delivery bot, or a software-triggered recorded call may fit the A2P definition depending on how the call is initiated.
A normal employee manually dialling a customer is different.
New A2P Call Declaration Requirement
This is one of the most commercially important changes.
A sender using A2P calls must declare their use in advance to their Originating Access Provider.
The declaration must include details such as:
- CLI ranges used for A2P calling,
- number series or numbering resources, and
- any other information that TRAI may prescribe.
The OAP records this declaration on the DLT platform together with the relevant numbering resources assigned to the sender.
What Happens if the Declaration Is Not Made?
A call made without the required prior declaration may be treated as Unsolicited Commercial Communication.
This gives businesses a clear reason to audit automated calling systems before the provision becomes applicable.
Teams That Should Be Involved
For many organisations, this will require coordination between:
- compliance,
- telecom operations,
- IT,
- marketing,
- customer support,
- procurement, and
- third-party call-centre vendors.
The people operating the communication technology may know which numbers are used, while the compliance team may know what the regulation requires. Both sides need to work together.
Changes in the Meaning of Consent
The amendment revises the definition of consent.
Consent is described as voluntary permission, whether explicit or inferred, given by a customer to a sender for commercial communication related to a specific purpose, product or service.
The regulation further explains that, for TCCCPR purposes, consent relates to permission to establish a communication channel between the sender and the customer.
It also explains that revocation means withdrawal of that permission.
This makes the scope clearer.
A business should be able to answer:
- What exactly did the customer agree to?
- For which product or service?
- Through which communication channel?
- Is the consent still active?
- Can it be verified?
What Is Explicit Consent?
The amendment also changes the definition of explicit consent.
It can be:
directly verified from the recipient in a robust and verifiable manner and recorded by the Consent Registrar, or
obtained through another verifiable method and later registered in the Consent Register according to TRAI's prescribed process.
For businesses, this turns consent into an evidence issue.
The question is not only whether consent was obtained. The business should also know whether it can prove:
- who gave it,
- what was agreed,
- when it was obtained,
- how it was verified, and
- whether it was properly registered where required.
TRAI Consent Is Not the Same as DPDP Compliance
The amendment makes this distinction directly.
Nothing in the regulations exempts a sender from obligations or liability under the Digital Personal Data Protection Act, 2023.
This matters because a customer may permit commercial communication in one context while a separate legal analysis may still be needed for the collection, use, or processing of personal data.
Businesses should therefore review TRAI communication consent and DPDP compliance as related but separate subjects.
What Counts as a Relationship With the Customer?
The amended definition of “relationship” includes different situations.
Existing Business or Commercial Relationship
A relationship may exist for a business or commercial reason, with or without exchange of consideration.
Recent Enquiry
A relationship may arise from an enquiry about goods, products or services where the enquiry was made during the seven days immediately before the communication.
The enquiry must be:
- made in writing or digitally, and
- maintained by the sender in a verifiable form.
Recent Application
A relationship can also arise from an application for a product or service submitted during the preceding three months, provided the relationship has not already been terminated.
Practical Business Meaning
CRM systems should not simply label every old lead as an “existing relationship”.
If a business is relying on an enquiry or application to justify communication, the date and proof of that enquiry can matter.
Revised Rules for Service Calls and Service Messages
The amendment provides clearer examples of communication that may qualify as a service message or service call.
These include communication about:
- a product already purchased,
- an existing service,
- warranty,
- product recall,
- software upgrade,
- safety or security,
- periodic balance alerts,
- delivery of goods or services,
- OTP authentication,
- app login,
- password reset, and
- two-factor authentication.
Such communication must not be promotional in nature.
This distinction is important.
A message may begin as a service communication but lose that character if marketing material is added to it.
Service Communication Connected With an Ongoing Transaction
The definition also covers communication used to facilitate an ongoing purchase or use of products or services.
In this situation, explicit consent is required.
The communication must remain non-promotional.
The explicit consent is valid for seven days or until the customer revokes it, whichever happens earlier. It may be renewed for another seven days at the customer's request.
The seven days should not be applied blindly to every form of consent under the regulations.
Promotional, Service and Transactional Communication: Main Difference
| Type | Purpose | Promotional? | Compliance Focus |
| Promotional | Marketing products or services | Yes | Preference, consent and promotional controls |
| Service | Information linked to existing product/service or permitted transaction | No | Correct classification and consent where applicable |
| Transactional | Communication connected with a transaction | No | Transaction-specific treatment |
| Transactional with service information | Transaction plus service information | No | Treated as service communication |
For compliance teams, correct classification should happen before a campaign goes live, not after complaints begin.
AI/ML-Based Spam Detection Is Now Part of Enforcement
A new Regulation 21A changes the way suspected spam can be handled.
Terminating Access Providers must use their AI/ML-based UCC detection systems to identify CLIs with a high probability of being involved in UCC.
Such numbers are flagged as:
“Suspected high probability UCC CLI”
Once identified, the information has to be shared with the relevant Originating Access Provider through the DLT platform immediately and, in any case, within two hours.
This means enforcement is no longer dependent only on complaints.
Behavioural patterns can also bring a sender under review.
What Happens After a Number Is Flagged?
The sender does not immediately lose all telecom resources simply because one CLI is flagged.
The process moves through several stages.
Stage 1: Sender Notification
The OAP sends an SMS, email, or both to the sender informing it that the CLI has been identified as suspected of sending UCC.
Stage 2: KYC Mapping
Within one business day, the OAP identifies the sender's unique KYC identifiers. These are shared through DLT with other Access Providers.
Stage 3: Other Telecom Resources Are Identified
Other Access Providers identify telecom resources linked with the same sender.
Stage 4: Ten-Day History Is Checked
Access Providers review whether other CLIs linked to that sender were also identified as suspected high-probability UCC CLIs in the previous ten days.
This is why a business operating many numbers should maintain a proper telecom-resource inventory.
Five CLI Threshold and Sender-Level Review
If five or more CLIs belonging to the same sender are identified as suspected high-probability UCC CLIs within ten days, the regulations require further action.
The next step depends on whether it is the first, second, or a later occurrence.
| Occurrence | Required Action | Timeline |
| First | KYC re-verification | Within next 3 business days |
| Second | Physical KYC verification and misuse check | Within next 5 business days |
| Later occurrence | Further investigation and enforcement | Within next 5 business days |
For a second occurrence, where KYC information does not match, or telecom resources are found to be misused for UCC, outgoing services of all relevant telecom resources can be barred for 15 days.
This may include:
- PRI trunks,
- SIP trunks,
- SIMs, and
- other telecom resources allotted to the sender.
New Rules for Header and Content Template Misuse
The regulations take a much stronger approach when a registered header or content template is misused.
Once misuse is detected, the OAP has to suspend the affected header or content template across Access Providers.
The suspension should happen immediately and within the prescribed outer limit.
A notice is also issued to the sender whose name is linked with that header or template.
This area deserves attention from both compliance and IT teams because misuse can arise through:
- compromised login details,
- leaked passwords,
- API-key exposure,
- unauthorised access,
- telemarketer misuse,
- cloning, or
- system compromise.
What Must the Sender Do After Misuse Is Reported?
The amendment lays down specific remedial steps.
Reset Passwords and API Credentials
Within three business days of receiving the notice, the sender must reset relevant communication-system credentials, including:
- passwords,
- API keys, and
- system permissions.
File a Complaint With Law Enforcement
A formal complaint must be filed with the appropriate law-enforcement agency within the prescribed period.
The sender should identify whether misuse arose due to:
- compromised login credentials,
- unauthorised system access,
- misuse by a telemarketer, aggregator or delivery entity, or
- another identifiable cause.
A copy must also be shared with the OAP within the applicable time.
Review All Registered Communication Assets
The sender also needs to review registered:
- headers,
- content templates, and
- consent templates.
This creates a strong reason to maintain an updated internal list of active templates instead of allowing old registrations to remain unmanaged.
What if the Telemarketer Is Responsible?
Where a telemarketer is found to have misused a header or content template, or to have been complicit in the misuse, stricter action can follow.
The sender is required to file the relevant complaint with law enforcement.
The OAP can bar the telemarketer's outgoing services and issue a notice seeking an explanation.
If the OAP finally concludes that the telemarketer was responsible or involved, all telecom resources of that telemarketer can be disconnected across Access Providers for one year.
The telemarketer can also remain blacklisted during that period.
For businesses using external telemarketers, vendor access controls therefore become much more important.
Compromised Headers and Templates May Need Re-Registration
Where misuse results from leakage, cloning or compromise of credentials, the Registrar Access Provider can be required to de-register the sender's headers and content templates.
The sender then has to re-register them, and new IDs are issued.
The regulations recognise that bulk de-registration may disrupt important communications. In such situations, phased de-registration may be permitted subject to the regulatory conditions.
A large organisation should therefore know in advance which communication templates are operationally critical.
New Complaint Handling Mechanism
Regulation 25 has been rewritten.
The new mechanism links complaint information with AI/ML-generated intelligence.
Access Providers must establish systems and processes to:
- resolve customer complaints,
- match complaint data with information on suspected UCC senders,
- investigate the communication, and
- take remedial action where required.
Complaint Recording
The Terminating Access Provider records complaints and reports on DL-Complaints.
The information is generally shared with the Originating Access Provider in real time.
Incomplete Complaint
Where the full sender number or header is not available, the customer may be informed why the complaint cannot proceed and how to file it correctly.
Seven-Day Complaint Window
The regulation checks whether the complaint was made within seven days of receiving the commercial communication.
If it is reported after seven days, it may be closed as a formal complaint and recorded instead as a report.
The information remains part of the system.
This is useful to understand because a late complaint may still contribute to the broader regulatory picture even if it is not processed in the same way as a timely complaint.
Complaints Against Registered Senders
Where a complaint concerns a registered sender or registered telemarketer, the OAP examines whether the complained communication actually took place.
It reviews communication detail records and, in SMS cases, checks whether required regulatory pre-checks were followed.
Where non-compliance is found, action can be taken under the regulations.
For businesses, this underlines the importance of retaining enough internal campaign information to explain what was sent, when it was sent, and through which approved route.
Complaint Thresholds for Unregistered Telemarketers
The amended system uses both complaint counts and AI-generated data.
Certain actions can be triggered where:
- three or more complaints from unique recipients are linked with a sender and a CLI is also identified as a suspected high-probability UCC CLI, or
- five or more complaints from unique recipients are received within the specified ten-day period.
These are separate tests and should not be combined into one simplified rule.
What Happens When UCC Is Confirmed?
Where the OAP concludes that the sender or its telemarketer was involved in UCC, the consequences can extend far beyond the one number that generated the complaint.
First Violation
Outgoing services of all telecom resources allotted to the sender can be barred for 15 days.
This includes resources such as:
- PRI trunks,
- SIP trunks,
- SIMs, and
- other telecom resources.
Subsequent Violation
For later violations:
- telecom resources can be disconnected for one year,
- the sender can be blacklisted for one year,
- no new telecom resources can be issued during that period, and
- devices used for UCC can also be blocked for one year.
That is why organisations should treat repeated UCC complaints as an operational risk, not just as a marketing issue.
Can a Sender Challenge the Action?
Yes.
A sender can make a representation to the Originating Access Provider.
The OAP has to decide the representation within a maximum of seven business days and record its findings.
Where the sender remains dissatisfied, a further representation can be made to TRAI under Regulation 29.
Consumer Appeal Mechanism
Consumers also have access to an appeal route.
The amendment permits appeal to the Appellate Authority under the Telecom Consumers Complaint Redressal Regulations, 2012.
It also requires Access Providers to establish mechanisms to transmit relevant appeals to the concerned authority.
This means complaint handling now includes both sender-side representations and consumer-side appeals.
TRAI Can Classify Different Types of Senders
Regulation 25A gives TRAI the power to classify senders into different categories for enforcement.
TRAI may look at factors such as:
- importance of the entity to the economy,
- whether it belongs to a critical sector,
- criticality of services supplied to consumers,
- regulatory status,
- scale and volume of operations,
- telecom-resource usage, and
- likely impact of suspension or disconnection on consumers.
This can allow different enforcement criteria for different types of senders.
A hospital, bank, utility company, and ordinary promotional caller may not necessarily create the same consumer impact if communication resources are disconnected.
Record-Keeping Becomes More Important
The regulations provide for two years of complaint history.
Records may include:
- complaints,
- appeals,
- alleged violations,
- date and time,
- resolution status, and
- supporting documents used to resolve the matter.
Sender-wise histories must also be recorded.
TRAI can also require relevant information, including call detail records, when auditing complaint-handling processes.
Financial Disincentive for Access Providers
The amendment also places responsibility on Access Providers.
Where UCC occurs because an Originating Access Provider failed to conduct scrubbing in accordance with customer preference and consent, the OAP can be liable for a financial disincentive of 1,000 rupees for each valid complaint.
Where the issue arises because another Access Provider improperly registered the relevant header or content template, responsibility can shift accordingly.
Restoration of Telecom Resources
The regulations also provide a route for restoration.
If TRAI finds that an Access Provider's investigation was not based on sufficient evidence, it may direct restoration of the sender's telecom resources and removal from the blacklist, subject to feasibility.
In another category of cases, restoration may be allowed where corrective steps have been taken.
The specified restoration charge is:
- 5,000 rupees per telecom resource
- subject to a total limit of 5 lakh rupees
- For PRI and SIP trunks, each DID number is treated as a separate resource for this calculation.
- TRAI may also reduce or waive the amount where it finds merit in the sender's response.
New Rules for Call-Management and Caller-ID Applications
A new Regulation 34A deals with call-management applications and similar services.
These platforms cannot broadly tag, block, or filter calls from number series designated by TRAI or the Central Government for commercial or government communication in a manner that conflicts with the regulation.
The rule also says that where such an application allows a user to report a call as spam, junk, or UCC, the report has to be sent to the DLT platform maintained by the Access Providers.
Can a Consumer Still Block a Call Personally?
Yes.
The regulation does not prevent an individual from blocking or filtering a call on their own device.
The restriction is aimed at platform-level treatment of designated number series.
This distinction is important.
A user can still decide that they do not want to receive a particular call. Still, an application cannot necessarily use crowd-sourced reports to label designated commercial or government series for all users broadly.
New A2P Call Charge
Regulation 35A allows the Terminating Access Provider to charge the Originating Access Provider up to:
0.05 rupees per minute
for A2P calls, on a per-minute pulse basis.
The charge cannot exceed the lowest tariff offered by the TAP to the senders or telemarketers for whom it acts as an OAP.
This is a provider-level charging rule. It should not be presented as a direct consumer charge.
A2P Calls Exempt From the Charge
The regulation excludes certain A2P calls.
| Call Type | Charge Position |
| Calls from 140xx | Exempt under the specified rule |
| Calls from 1600xx | Exempt |
| Calls from 1601xx | Exempt |
| Other TRAI-designated series | Exempt unless otherwise notified |
| Calls made by TRAI | Exempt |
| Calls made on TRAI's direction | Exempt |
| Calls by authorised agencies | Exempt where covered |
Changes to Consumer Preference Through 1909
Schedule II revises the customer preference structure.
Consumers can now use the system to block promotional commercial communication by category or block all promotional categories.
The main categories include:
- Banking, insurance, financial products and credit cards
- Real estate
- Education
- Health
- Consumer goods and automobiles
- Communication, broadcasting, entertainment and IT
- Tourism and leisure
- Food and beverages
BLOCK PROMO and UNBLOCK ALL
| Option | What It Does |
| BLOCK PROMO | Blocks promotional commercial communication |
| Category block | Blocks the selected promotional category |
| UNBLOCK ALL | Unblocks all promotional categories |
| Category unblock | Unblocks the selected category |
BLOCK PROMO does not block transactional communication, service communication, or government communication.
What Happens to Existing FULLY BLOCK Preferences?
Existing preferences under FULLY BLOCK are to be migrated to BLOCK PROMO within 15 days from the commencement of the relevant provision.
For consumers, this is more than a change of name.
BLOCK PROMO focuses on promotional communications. Transactional, service, and government communications are treated differently.
Businesses should therefore update internal interpretations of DND preference data.
Impact on Banks, NBFCs, Insurers and Fintech Companies
Financial-sector entities use several kinds of customer communication every day.
These may include:
- OTPs,
- fraud alerts,
- balance alerts,
- service reminders,
- loan communication,
- insurance communication,
- promotional offers, and
- automated voice calls.
The 2026 amendment makes correct classification more important.
Banks and financial companies should review:
Automated Calling
Check whether voice bots, reminder systems, or other software-generated calls fall within A2P calling.
CLI Mapping
Know which CLI range is used for each communication category.
Consent
Separate service communication from marketing consent.
Telemarketers
Review whether external agencies are using approved resources only.
DLT Credentials
Restrict access to headers, templates, APIs, and registered communication assets.
Impact on E-Commerce and Retail Businesses
E-commerce companies commonly send both service and promotional communication.
Order confirmation, OTP, and delivery updates may be service-related, while cross-selling, discount campaigns, or new-product advertisements are promotional.
Mixing the two in the same template may create problems.
A retailer should review:
- campaign categories,
- consent source,
- DLT templates,
- automated voice calls,
- customer enquiry records,
- telemarketer access, and
- complaint trends.
Impact on BPOs, Call Centres and Telemarketers
For a BPO or contact centre, this amendment can affect day-to-day operations directly.
The business should know:
- whose telecom resource is being used,
- whose KYC is linked with it,
- which client owns each header,
- which templates are permitted,
- which API keys are used,
- whether numbers are shared across clients,
- whether calls are automated, and
- what happens if a complaint or spam flag is received.
Misuse by a telemarketer can result in action against telecom resources across Access Providers.
Impact on SaaS and Cloud Telephony Companies
Cloud telephony and automated calling platforms should also review their operating model.
Not every software company automatically becomes a regulated sender.
The relevant questions are:
- Who initiates the communication?
- Who controls the telecom resource?
- Who owns the CLI?
- Whose customer is receiving the communication?
- Who is registered on DLT?
- Who holds the header and content template?
These questions help identify where regulatory responsibility actually sits.
Impact on Telecom Operators and VNOs
The amendment creates several operational duties for Access Providers.
These include:
- AI-based spam detection,
- sharing flagged CLI information,
- KYC mapping,
- complaint investigation,
- DLT recording,
- sender notification,
- resource suspension,
- representations, and
- audit records.
For a Virtual Network Operator, the Network Service Operator must provide the necessary digital interface with real-time DLT functionality so that the VNO can comply with the regulations.
DLT Compliance Areas Businesses Should Review
| Area | What Should Be Checked |
| Sender registration | Correct legal entity and current details |
| CLI mapping | Correct mapping of numbers and ranges |
| A2P calls | Whether declaration is required |
| Headers | Active, authorised and secure |
| Content templates | Correct category and approved use |
| Consent templates | Correctly registered |
| Telemarketer access | Only approved vendors/users |
| API credentials | Controlled and monitored |
| KYC | Matches current business details |
| Complaint process | Clear owner and escalation route |
Telecom and DLT Credential Security
The amendment makes credential security a practical compliance issue.
Businesses should consider reviewing:
Password Access
Avoid common logins shared across many people or vendors.
API Keys
Maintain an inventory of active API credentials.
Vendor Access
Remove access immediately when an agency or employee is no longer authorised.
Audit Logs
Keep enough internal information to understand who used which resource.
Incident Response
Set a clear internal process for:
- detecting misuse,
- blocking access,
- resetting credentials,
- informing the OAP,
- filing a complaint where required, and
- reviewing all related headers and templates.
Compliance Requirements for Senders
| Requirement | Trigger | Action |
| A2P declaration | Automated A2P calls are used | Declare relevant use and CLI ranges |
| Consent management | Communication relies on consent | Maintain verifiable basis |
| Enquiry relationship | Communication relies on enquiry | Preserve enquiry in verifiable form |
| Template misuse | Misuse reported | Reset credentials and complete remedial action |
| Law-enforcement complaint | Specified misuse occurs | File complaint |
| Spam flag | CLI identified as suspected UCC | Review and respond |
| KYC verification | Threshold reached | Complete required verification |
Recommended Internal Compliance Checklist
| Check | Responsible Team | Priority |
| List every automated calling system | Operations / IT | High |
| Identify all CLI ranges | Telecom / IT | High |
| Verify DLT sender details | Compliance | High |
| Review headers | Compliance | High |
| Review content templates | Marketing / Compliance | High |
| Check consent records | Legal / Compliance | High |
| Review telemarketer access | Vendor Management | High |
| Review API-key access | IT Security | High |
| Confirm KYC details | Compliance | Medium |
| Build complaint escalation process | Customer Support | Medium |
| Map 1909 preference changes | Customer Communication | Medium |
Main Risks of Ignoring the Amendment
The risks depend on the actual violation.
Possible regulatory consequences include:
- suspension of headers,
- content template suspension,
- outgoing services ban,
- KYC re-verification,
- physical KYC verification,
- telecom resource disconnection,
- blacklist entry,
- device blocking,
- financial penalties, and
- restoration costs.
In terms of operation, companies may also encounter:
- stopping customer calls,
- disrupting call center activities,
- blocking of marketing activities,
- immediate DLT correction,
- supplier conflict,
- customer complaints, and
- re-registration work.
Major Timelines Businesses Should Track
| Period | Where It Appears |
| 30 days | General commencement |
| 60 days | Selected provisions |
| 90 days | Annexure-listed changes |
| 2 hours | Sharing flagged CLI information |
| 1 business day | Certain KYC/resource identification steps |
| 3 business days | KYC re-verification and some remedial actions |
| 5 business days | Physical verification and certain investigations |
| 7 days | Certain consent and complaint-related periods |
| 10 days | CLI/complaint review periods |
| 15 days | Certain service restrictions and preference migration |
| 1 year | Certain blacklisting/disconnection measures |
| 2 years | Complaint and sender history |
The same number can appear in different parts of the regulations for different purposes. Each internal deadline should therefore be linked to the exact provision.
What Businesses Should Do Now
The amendment is too wide for a business to handle through one generic DLT check.
A better approach is to review the full communication chain.
1. Identify Automated Calling
Find every system that places a call without manual human dialling.
2. Create a Telecom Resource Inventory
Map:
- CLI ranges,
- telephone numbers,
- SIP trunks,
- PRI trunks,
- SIMs, and
- automated calling systems.
3. Review DLT Registrations
Ensure that the DLT communications data of the existing business corresponds to its actual communications process.
4. Verify Consent
Determine the type of consent used for every campaign and whether it can be verified.
5. Verify Classification of Communication
Differentiate between:
- promotional,
- service, and
- transactional communication.
6. Audit Headers and Templates
Look for wasted, duplicate, or insufficiently controlled assets.
7. Telemarketer Access Audit
Be sure of who is authorized to access which communication tool.
8. Improve Credentials Management
No passwords or API keys should be kept permanently shared among teams.
9. Plan for Spam Notification Response
Develop an internal procedure for dealing with OAP notifications and evidence collection.
10. Map the Correct Effective Period
Prepare separately for 30-day, 60-day, and 90-day provisions.
How Corpseed Can Help With TRAI Compliance
The 2026 amendment ties compliance with telecom infrastructure, DLT records, consent, campaign structure, and vendor access. For most companies, the problem does not lie in understanding one particular regulation but figuring out which ones apply to their communication infrastructure.
Corpseed’s Telecom Regulatory Compliance Services would be able to help businesses evaluate these items prior to any operational issues arising from them.
Services may include:
- Applicability of TRAI compliance
- Compliance assessment for A2P calls
- DLT compliance assessment
- Sender and Principal entity compliance assessment
- CLI & Telecom resources mapping
- Consent process review
- Header/content template assessment
- Telemarketer compliance review,
- regulatory gap assessment,
- internal compliance checklist preparation,
- telecom compliance consulting, and
- ongoing regulatory support.
A business using automated calls, bulk SMS, telemarketers, or DLT-linked communication systems can benefit from reviewing the entire communication flow rather than treating each issue separately.
Key Takeaways
- Third Amendment Regulations, 2026, to the 2018 commercial communication framework have been adopted by TRAI.
- There is a specific definition of A2P voice calls now.
- Senders of such A2P calls have to adhere to the advance declaration norms after the implementation of the provision.
- Consent and explicit consent have been revised.
- Service messages and service calls have been defined in more detail.
- AI/ML-based spam identification now feeds into sender-level investigation.
- Several flagged CLIs linked to one sender can trigger KYC re-verification and physical verification.
- Misuse of header and content template could lead to automatic suspension and necessary remediation.
- Handling complaints is now done using both consumer complaints and artificial intelligence data.
- There are new guidelines for call management apps regarding series designation and DLT reporting.
- A2P calls may attract a terminating charge of up to 0.05 rupees per minute in applicable cases.
- Consumer preference settings under 1909 have also been revised.
- Businesses should map their obligations according to the 30-day, 60-day, and 90-day implementation periods.
Schedule a Call Back
Document Preview
Embedded reference document
Related
Explore more updates from the same department.
