💬 WhatsApp API @ Best Rate | Zero Setup Fee → 99.9% Uptime OTP Delivery — Try FREE Demo! 🏆 10,000+ Registered Businesses — 2,000+ Enterprise Clients Served 🚀 API Integration in Under 5 Minutes 🏅 Verified Business Badge with RCS Messaging 💬 WhatsApp API @ Best Rate | Zero Setup Fee → 99.9% Uptime OTP Delivery — Try FREE Demo! 🏆 10,000+ Registered Businesses — 2,000+ Enterprise Clients Served 🚀 API Integration in Under 5 Minutes 🏅 Verified Business Badge with RCS Messaging
Talk to Sales: India 1800 102 1822
Regulatory reference

TRAI Regulations and DLT Guidelines for Commercial SMS

A current reference to India's TCCCPR framework, from message categories and header suffixes to variable tagging and CTA whitelisting, plus how other major markets regulate A2P SMS.

TCCCPR and amendments-P / -S / -T / -G headersTyped variable tagsWorldwide A2P rules
30 minWindow that defines a transactional message
4Header suffixes: -P, -S, -T, -G
6Typed variable tags in DLT templates
7 daysTime limit to report UCC

Quick answer

Commercial SMS in India is governed by TRAI's TCCCPR 2018 and its amendments. Senders register as Principal Entities on operator DLT platforms, along with headers, content templates and their telemarketer chain. Messages are classed as transactional (within 30 minutes of a customer action), service, promotional or government, and carry a -T, -S, -P or -G header suffix. Template variables must be type-tagged, and links and callback numbers must be whitelisted.

India: TRAI and DLT

TCCCPR: the rulebook behind commercial SMS in India

Every commercial SMS and voice call in India is governed by the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR), issued by the Telecom Regulatory Authority of India (TRAI) on 19 July 2018. TRAI sets the rules, and each access provider enforces them through its own Distributed Ledger Technology (DLT) platform and Codes of Practice.

Under TCCCPR, a business (the Sender or Principal Entity) can only send commercial communication after registering itself, its headers (sender IDs) and its content templates on DLT. Each message is scrubbed in real time against those registrations and the recipient's preferences and consents. Customers can complain about unsolicited commercial communication (UCC) through 1909 or the TRAI DND app.

Key regulatory milestones

InstrumentDateWhat it changed
TCCCPR, 2018 (6 of 2018)19 July 2018DLT-based registration of senders, headers, templates, consent and preferences
TRAI direction on URL/APK/OTT whitelistingIssued 20 Aug 2024, enforced from 1 Oct 2024Messages with non-whitelisted links blocked
Message traceability (PE-TM chain)Enforced from 11 Dec 2024Messages with an undeclared or mismatched telemarketer chain rejected
TCCCPR (Second Amendment) Regulations, 202512 Feb 2025New message categories, -P/-S/-T/-G header suffixes, stricter complaint handling and penalties
TRAI direction on pre-tagging of template variables18 Nov 2025Every template variable must carry a typed tag; failing messages rejected after a 60-day logger period
TRAI direction on 1600-series for BFSI19 Nov 2025Phased move of service and transactional calls by RBI, SEBI and PFRDA-regulated entities to 1600-series
TCCCPR (Third Amendment) Regulations, 2026Announced 18 Sep 2026AI/ML-assisted UCC detection, A2P call rules, appeals, faster action on header/template misuse
This page summarises the regulations for senders. The binding text is the Gazette notification; read the Second Amendment Regulations on trai.gov.in and TRAI's UCC consumer page for the authoritative version.

The Second Amendment: four message categories

The Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025, dated 12 February 2025, rewrote the definitions every DLT template is classified by. The headline change is a four-way split of commercial communication:

CategoryDefinition (summary of the regulation)ConsentHeader suffix
TransactionalSent to a customer in response to a customer-initiated transaction within thirty minutes of the transaction, e.g. OTPs from banks, e-commerce or app logins, transaction alerts and confirmations, balance alerts after a transaction, refund informationNot required-T
Service(i) Information to an existing customer about a product or service: warranty, recall, software upgrade, safety or security, periodic balance alerts, delivery updates; or (ii) messages that facilitate an ongoing purchase after explicit consent, valid for seven daysNot required for (i); explicit consent for (ii)-S
PromotionalAny communication containing promotional material or advertisement; must carry an opt-out option in the same messageDelivered only where preferences allow or explicit digital consent exists-P
GovernmentSent on the directions of the Central or State Government through DLTNot required-G
Mixing rule: if promotional content is mixed into a transactional or service message, the whole message is treated as promotional. A transactional message that carries service information is treated as service. A delivery update sent hours after the order is a service message, not transactional, because it falls outside the thirty-minute window.

Complaints and enforcement

  • Recipients must report UCC within seven days of receiving it; customers do not need to be on the DND preference register to complain against unregistered telemarketers.
  • Action against an unregistered sender is triggered by complaints from five or more unique recipients in ten days (previously ten complaints in seven days).
  • First proven violation: all the sender's outgoing telecom resources are barred for fifteen days. Repeat violations: disconnection across all operators for one year and blacklisting.
  • Headers and content templates unused for ninety days are temporarily deactivated and can be reactivated on request.
  • Access providers face graded financial disincentives for misreporting UCC, wrongly closing valid complaints and approving non-compliant headers or templates.

The Third Amendment: AI-led spam enforcement

On 18 September 2026 TRAI announced the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, following a consultation that opened on 13 March 2026. Its salient features, as published in TRAI's press release, include:

AI/ML spam detection

Operators must flag CLIs with a high probability of sending UCC and share them across networks. Five or more flagged CLIs of a sender in ten days trigger graded action, from KYC re-verification to disconnection.

Faster complaint action

Action can start at three unique complaints in ten days when the sender's CLI is also flagged by the operator's AI system. Consumers gain an appeal route within fifteen days.

A2P calls regulated

Calls placed by software, auto-dialers or robo-calls must be pre-declared to the operator with the CLIs used; undeclared A2P calls are treated as UCC.

Header and template misuse

Misused headers or templates are suspended within six hours. Senders must take remedial steps and report to law enforcement; a telemarketer at fault is disconnected for a year and blacklisted.

It also recognises verifiable legacy consents once registered on the operators' consent platform, allows commercial messages for seven days after a written or digital customer inquiry, and bars call-management apps from blanket spam-tagging the 140xx, 1600xx and 1601xx series.

Clause-wise effective dates for the Third Amendment are set in its Gazette text. SMSGatewayHub will apply operator implementation notices as they are issued; check with your account manager before changing live flows.

The DLT ecosystem: who registers what

DLT is the shared ledger operators use to record every party and asset in a commercial message. The building blocks:

Principal Entity (PE)

The business that sends commercial communication and is accountable for it. Registers with KYC documents and receives a PE ID.

Header (sender ID)

The alphanumeric or numeric string shown as the sender. Each header is registered by the PE and now displays a category suffix.

Content template

The approved message text with fixed content and typed variables. One content template can be linked to only one header.

Consent template

The text shown to a customer when seeking consent, stating the purpose and the brand. Consent is sought through the 127xxx short code.

Telemarketer (TM)

The registered aggregator or delivery partner that submits traffic to operators, such as SMSGatewayHub's operator-registered platform.

PE-TM chain binding

The PE declares every telemarketer in its delivery chain. Since 11 December 2024, messages with an undeclared or mismatched chain are rejected.

CTA whitelist

URLs, APK and OTT links and callback numbers the PE registers as safe. Only whitelisted values pass scrubbing.

Preference and consent registers

Records of each subscriber's DND preferences and digital consents, checked in real time before a promotional message is delivered.

SMSGatewayHub helps you complete DLT registration, declare the PE-TM chain and map headers and templates in your panel. See our guide to PE-TM chain binding.

Headers and the -P, -S, -T, -G suffixes

The Second Amendment requires that recipients can identify the type of commercial communication from the header itself. Operators therefore append -P, -S, -T or -G to the header based on the DLT category of the template used. Operators began rolling the suffixes out network-wide in May 2025, so a transactional message from a header such as STRIPL is displayed with a -T ending.

SuffixCategoryTypical useWhat the sender must do
-TTransactionalOTP, login code, payment confirmation within thirty minutesRegister the template as transactional only if it meets the thirty-minute test
-SServiceDelivery updates, renewal reminders, account and warranty alertsKeep content strictly informational, with no offers
-PPromotionalOffers, launches, discounts, re-engagementInclude an opt-out; respect preferences, consent and the delivery window
-GGovernmentMessages on directions of the Central or State GovernmentAvailable only to government senders
You do not add the suffix yourself; it is applied by the operator from your DLT template category. What you control is choosing the correct category, which is why template classification now matters to customer trust. See our SMS sender ID guide for header formats.

Service Explicit now sits under Promotional

DLT previously had Service Explicit (consent-based) and Service Implicit (existing customer) categories. Because explicit-consent service messages were often misused for offers, the Second Amendment narrowed the service definition and limited explicit consent to seven days.

Operators have since stopped accepting new Service Explicit templates and migrated existing ones to the Promotional category, so they carry the -P suffix and follow promotional scrubbing and delivery-time rules. Informational messages to existing customers continue as Service (-S) templates.

If your old Service Explicit templates carried any offer, coupon or cross-sell text, they will now behave as promotional traffic. Re-register purely informational content as Service, and move marketing content to Promotional with consent. Our Service Explicit vs Service Implicit guide covers the migration in detail.

Typed variable tagging in content templates

On 18 November 2025 TRAI directed all access providers to require that each variable in every SMS content template is pre-tagged with its content type, purpose and validation rule. Tagged values are then validated at scrubbing time, and links and numbers are matched against your whitelisted CTAs. The tags listed in the direction's annexure:

TagUse forValidation at scrubbing
{#numeric#}OTPs, amounts, quantities, account digitsDigits only, no letters or special characters
{#alphanumeric#}Order, booking and ticket IDsLetters and numbers with length validation
{#url#}Website, tracking or short linksMust match a registered static, dynamic or short-URL CTA
{#urlott#}App download, APK or OTT linksMust match a registered OTT or APK CTA
{#cbn#}Callback numbersMust match a registered mobile, landline or toll-free CTA
{#email#}Support or reply email addressesMust be a valid email format

Compliance timeline

  • New templates registered from ten days after the direction must be tagged before approval.
  • Operators had thirty days to start scrubbing tagged variables against the CTA whitelist.
  • Existing templates had sixty days from the start of tag scrubbing to be modified.
  • During those sixty days messages ran in logger mode: delivered, but with fault records. After that window, any message failing variable validation is rejected outright.

Variables should still be used sparingly. The Second Amendment allows more than the usual number of variables only on recorded justification, requires each such variable to be pre-tagged and keeps at least thirty percent of the template as fixed content. Read our explainer on mandatory variable tagging and the DLT template registration process for worked examples.

Whitelisting URLs, APKs, OTT links and callback numbers

Since 1 October 2024, operators block any commercial SMS containing a URL, APK or OTT link that the sender has not whitelisted on DLT, under a TRAI direction issued on 20 August 2024. The Second Amendment extended scrubbing to callback numbers and requires the sender to submit an undertaking that whitelisted links are not malicious.

  1. List every domain, short link, app-store or APK link and callback number your templates use.
  2. Upload them as CTAs on your operator DLT portal, using your own or a trusted short-link domain.
  3. Tag each link variable as {#url#} or {#urlott#} and each phone variable as {#cbn#}.
  4. Re-test after any domain, shortener or support-number change.
Public URL shorteners that are not whitelisted by you are a common cause of silent rejections. Use a branded short domain registered against your own Principal Entity.

140-series and 1600-series voice numbering

TCCCPR also covers commercial voice calls. Under the Second Amendment, promotional calls, including auto-dialer and robo-calls, are allowed only from 140-series numbers, while service and transactional robo-calls should use the 1600-series allotted by the Department of Telecommunications, or another series allotted for the purpose. Senders must declare auto-dialer or robo-call use to their operator in advance.

SeriesPurposeWho uses it
140xxPromotional voice callsRegistered telemarketers and senders making marketing calls
1600xx / 1601xxService and transactional callsBanks, financial institutions, government and other authorised entities

On 19 November 2025 TRAI directed BFSI entities regulated by RBI, SEBI and PFRDA to move service and transactional calls to 1600-series in phases: commercial banks by 1 January 2026; large NBFCs, payments banks and small finance banks by 1 February 2026; mutual funds, AMCs, CRAs and pension fund managers by 15 February 2026; other NBFCs, co-operative banks and regional rural banks by 1 March 2026; and qualified stockbrokers by 15 March 2026.

Running voice SMS and OBD campaigns? Tell us whether the calls are promotional or service so we can map them to the correct number series and DLT declarations.

Sender compliance checklist

Use this checklist before launching any new SMS flow in India:

  1. Register your organisation as a Principal Entity on DLT and keep KYC details current.
  2. Register headers that reflect your brand; avoid unused headers, which are deactivated after ninety days.
  3. Classify each template correctly: transactional only for customer-initiated events within thirty minutes, service for informational updates, promotional for anything with an offer.
  4. Tag every variable with the correct typed tag and keep templates mostly fixed text.
  5. Whitelist every URL, APK or OTT link and callback number used in templates.
  6. Declare your full PE-TM chain, including SMSGatewayHub, on the DLT portal.
  7. Collect promotional consent via DCA where you need to reach DND subscribers, and include an opt-out in every promotional message.
  8. Schedule promotional sends inside the daytime window and keep consent and complaint records.

Ready-made formats are in our DLT sample templates library and the template approval guide.

Common DLT rejection reasons and fixes

Rejection reasonLikely causeFix
Template mismatchSent text differs from the approved template, including spaces or punctuationCopy the approved text exactly and only change variable values
Variable validation failedValue does not match its tag, e.g. letters in {#numeric#}Re-tag the variable or correct the data sent
URL or callback not whitelistedLink domain or number not registered as a CTAAdd the CTA on DLT and retest
Header or template inactiveNot used for ninety days or suspendedRequest reactivation on the DLT portal
PE-TM chain mismatchTelemarketer not declared in the chainUpdate the chain declaration to include every TM
Header-template mismatchTemplate linked to a different headerLink each template to exactly one header
Promotional outside window or to DNDSend time outside daytime window, or no consentReschedule and scrub against consent

For operator-specific codes and step-by-step resolutions, see DLT error codes and solutions. If you need hands-on help, DLT priority support connects you with our compliance desk.

Worldwide A2P SMS rules

How other countries regulate A2P SMS

Outside India, rules split into consent and marketing law and sender ID registration. Where rules are set by carriers rather than a regulator, we say so.

CountryRegulator / frameworkSender ID ruleConsent ruleNotable requirement
USAFCC (TCPA); carrier rules under CTIA guidelines10DLC brands and campaigns registered through The Campaign Registry; toll-free numbers verified; short codes approved per carrierPrior consent for marketing texts under TCPAUnregistered 10DLC traffic is filtered by carriers
CanadaCRTC (CASL)Varies by operatorExpress or implied consentIdentify the sender, include an unsubscribe, honour it within 10 business days
UKICO (PECR, UK GDPR); Ofcom for numberingVaries by operatorSpecific consent, or soft opt-in for similar products to existing customersNever hide identity; offer an opt-out in every message
EUNational data and telecom regulators (GDPR, ePrivacy Directive)Alphanumeric sender rules vary by country and operatorPrior consent, with a limited existing-customer exceptionLawful basis and records of consent
UAETDRASender IDs registered through licensed providers; promotional senders start with ADPrior explicit consent for marketingMarketing SMS only between 7 AM and 9 PM UAE time; recipients block via 7726
Saudi ArabiaCSTAlphanumeric sender IDs must be pre-registeredVaries by operatorPromotional sender IDs carry an -AD marker
SingaporeIMDAAlphanumeric sender IDs must be on the SMS Sender ID Registry (SSIR)Do Not Call Registry checks under the PDPAUnregistered IDs labelled Likely-SCAM since 31 Jan 2023
AustraliaACMA (Spam Act 2003)Branded sender IDs registered on the SMS Sender ID RegisterConsent, sender identification and unsubscribeUnregistered IDs show as Unverified from 1 Jul 2026
IndonesiaKomdigi; operatorsAlphanumeric sender IDs registered with each operatorVaries by operatorGrey routes are blocked
PhilippinesOperatorsSender ID registration required by major operatorsVaries by operatorLetter of authorisation and sample content
Carrier and regulator rules change often. Rows marked "varies by operator" have no single published national rule we could verify; confirm current requirements with our international desk before a launch.

Country notes for international senders

United States

The Telephone Consumer Protection Act, enforced by the FCC, requires prior consent for marketing texts. US carriers additionally require brand and campaign registration through The Campaign Registry for 10-digit numbers (A2P 10DLC), verification of toll-free senders, and opt-in, HELP and STOP handling in line with the CTIA Messaging Principles and Best Practices.

Canada, UK and EU

CASL requires consent, sender identification and an unsubscribe honoured within 10 business days (CRTC guidance). In the UK, marketing texts need specific consent or the soft opt-in, with a simple opt-out in every message (ICO guidance). EU sender ID formats differ by country and operator.

Middle East and Asia-Pacific

Official sources: TDRA FAQs for the UAE time window and 7726 blocking, IMDA for Singapore's SSIR, and ACMA for Australia's Sender ID Register. In Saudi Arabia, Indonesia and the Philippines, sender IDs are pre-registered with operators, and documents and lead times vary by network.

Reach overseas customers from the same panel with international bulk SMS; our team checks sender ID and template requirements for each destination before you go live.
Staying compliant

How SMSGatewayHub keeps you compliant

SMSGatewayHub is a TRAI DLT-registered messaging provider operating since 2009, trusted by 10,000+ registered businesses. Compliance is built into onboarding, not left to you:

DLT registration help

Guided PE, header and template registration on operator portals, plus PE-TM chain declaration for our platform.

Template and tag checks

We review category, typed variable tags and fixed-text ratio before you submit, reducing rejections.

CTA whitelisting support

We help you list and whitelist every URL, APK, OTT link and callback number your templates use.

Global sender rules

Sender ID registration and consent guidance for international routes, from 10DLC to SSIR and TDRA.

Our infrastructure is ISO 27001, ISO 9001:2015 and SOC 2 certified and VAPT tested; details are on the Trust Center. Answers to common account and DLT questions are on our FAQ page.

Frequently asked questions

TCCCPR is the Telecom Commercial Communications Customer Preference Regulations, 2018, issued by TRAI. It requires businesses to register on operator DLT platforms and governs headers, templates, consent, customer preferences and complaints for commercial SMS and calls in India. It has been amended in 2025 and 2026.

They show the category of the message: Promotional, Service, Transactional or Government. Operators add the suffix automatically from the DLT category of the template used, so senders only need to classify templates correctly.

A transactional message is one sent in response to a customer-initiated transaction within thirty minutes of that transaction, such as an OTP, a payment confirmation or a refund alert. Updates sent later, like delivery notifications, are service messages.

The amended rules narrowed service messages and limited explicit consent to seven days. Operators no longer accept new Service Explicit templates and have moved existing ones to the Promotional category, where they follow promotional scrubbing and timing rules.

TRAI's direction of 18 November 2025 requires every variable to be pre-tagged. The tags are numeric, alphanumeric, url, urlott, cbn and email, written as {#numeric#} and so on. Values that do not match their tag, or links and numbers that are not whitelisted, fail scrubbing.

Yes. Since 1 October 2024, operators block commercial SMS containing URLs, APKs or OTT links that the sender has not whitelisted on DLT, and the 2025 amendment extends scrubbing to callback numbers. Register every link and number as a CTA before sending.

Only if the recipient has given explicit digital consent through the operator's Digital Consent Acquisition facility. Without consent, promotional messages reach only subscribers who have not blocked that category, and only within the daytime delivery window.

It is the declaration of every telemarketer between a Principal Entity and the operator. Since 11 December 2024, messages whose telemarketer chain is undeclared or does not match the declared chain are rejected.

Promotional calls must come from 140-series numbers. Service and transactional calls use the 1600-series, and TRAI has directed banks and other entities regulated by RBI, SEBI and PFRDA to adopt it in phases.

Yes. Our team advises on sender ID registration and consent rules for each destination, such as 10DLC in the USA, the SSIR in Singapore and TDRA rules in the UAE, before your international campaign goes live.

Need help staying compliant?

Our DLT team registers your entity, headers and templates and checks every campaign before it goes out.