BlogIndia

DLT SMS links in India: TRAI URL whitelisting and deep links that still open your app

· 8 min read · By the Strait team

Since 1 October 2024, Indian operators block business SMS carrying links that aren't whitelisted on DLT. What TRAI's direction and the 2025 rules say, how they affect short links and app deep links, and a setup that keeps links working without re-registering templates.

If you send business SMS in India, the link in the message is now regulated almost as tightly as the message itself. Since 1 October 2024, telecom operators have been told to stop any commercial SMS that carries a URL, APK or OTT link the sender hasn't whitelisted. In February 2025, TRAI added stricter rules for content templates. For app teams this raises practical questions. Which domain do you whitelist: your website, your short-link domain, or both? Can a link change after the template is approved? And will the link still open the app?

This post sums up what the official sources say, without the rumours, then turns it into a setup for deep links in SMS. We aren't lawyers or an SMS aggregator. Your operator's DLT portal and your aggregator have the final word on how entries must be formatted, so check the details with them.

The rules, from the official sources

The framework. Business SMS in India runs under TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR). Senders register as entities, register headers (the sender IDs people see) and register content templates with an operator, on a distributed ledger (the "DLT" in DLT registration). TRAI's own description in the 2025 amendment: before sending, senders "are required to get content templates registered with the Access Providers. These templates typically have fixed and variable components", and every message is checked against its template; "if it fails, then it is not allowed to go forward."

The URL direction (August 2024). According to the Press Information Bureau, TRAI issued a Direction on 20 August 2024 telling all access providers "to block any traffic containing URLs, APKs (Android Package Kit), or OTT (Over The Top) links that have not been whitelisted". After operators asked for more time, TRAI moved the date. A PIB release of 30 August 2024 says the revised Direction requires that non-whitelisted URL, APK and OTT traffic "is not permitted with effect from October 1, 2024". A PIB release of 26 September 2024 adds that senders who don't whitelist "will not be able to transmit any messages containing URL/APK/OTT links". It also asks registered senders to upload their links "to the portal of the respective Access Providers".

The 2025 amendment. The TCCCPR (Second Amendment) Regulations, 2025, notified on 12 February 2025, put several related rules into the regulations themselves:

  • Operators must process scrubbing of messages containing "URLs/ APKs/ OTT links/ call back numbers … using, whitelisted data uploaded by the Senders", and the sender must submit an undertaking that the whitelisted links "are not malicious".
  • Content templates unused for ninety days are deactivated automatically, and reactivated on request.
  • More than three variables in a template are allowed only "in special circumstances" with justification. Each variable must be "pre-tagged for the purpose it is proposed to be used", and at least thirty percent of a template's characters must be fixed.
  • One content template can't be linked with more than one header.

Those are the rules. Everything below is about living with them when your links are deep links.

A deep-link service changes three things about the URL in your SMS, and each one matters for DLT.

  1. The domain in the message is the link service's domain, not your website's. A text that says https://hilltop.strait.link/order/8812 carries the link domain. That's the host the operator's scrubber sees, so that's the one that has to be whitelisted. Whitelisting hilltop.example doesn't cover a short link on another domain.
  2. Short links hide the destination. The person, and the scrubber, see the short URL, not the screen it opens. That's why the undertaking that your links "are not malicious" covers what's behind them too. A link service that lets anyone create links on a shared domain makes that promise hard to keep.
  3. Links change. Campaign destinations move, products sell out, order pages expire. If every change meant a new URL, and a new URL meant a template change, you'd be re-registering every week.

A setup that works

Whitelist one host that carries only your links. On Strait, every workspace gets its own subdomain, <handle>.strait.link, with HTTPS. Nobody else can create links on it, so whitelisting it lets your links through and nobody else's. The same advice applies to any provider: avoid whitelisting a shared short domain that thousands of other senders also use, because you'd be vouching for links you didn't create.

How you enter it (a domain, a full URL, or a URL prefix) depends on the operator's portal. Ask your aggregator what format they expect before you submit.

Keep the URL fixed and change the destination behind it

Register the template with the link in it, and change where the link goes on the server side when you need to. On Strait, a link's destination can be updated through the API (PATCH /v1/links/{slug} with a new longUrl) or in the dashboard. The short URL in the approved template doesn't change, so neither does the template. The new destination still has to be an https URL, and our engine checks it again on every update.

Put the variable part in a tagged URL variable

For transactional messages, the link usually differs per person (/order/8812, /order/8813). Under the 2025 rules each variable must be pre-tagged for its purpose, and templates with more than three variables need special justification. So plan the template around one link variable, tagged as a URL in your operator's portal, and keep the rest of the text fixed. Short slugs help: Strait slugs are up to 64 letters, digits, hyphens and underscores, so an order link stays short enough to leave room for the message.

An OTP follow-up or a delivery update shouldn't open a stale screen six months later. Give each transactional link an expiry (expiresAt on the link). On Strait, a tap on an expired link shows a branded "This link has expired" page by default, or goes to the app store or a web page you choose, per link or for the whole workspace.

Watch the ninety-day clock on seasonal templates

A Diwali or end-of-season template that sits unused for ninety days is deactivated automatically under the 2025 rules. Because the URL stays the same while the destination changes, you can reuse one approved template across seasons. Just send through it often enough, or ask for reactivation before the campaign.

Making the tap open the app

Getting the SMS delivered is half the job. The other half is the tap.

SMS apps generally don't open links in a browser of their own: Google Messages, Samsung Messages and Apple's Messages hand a tapped link to the phone's system. On Android with verified App Links for your link domain, the app opens directly on the right screen. Without verification, the link opens in the default browser, and the link server hands off to the app or to Google Play. On iPhone, a Universal Link on your domain opens the app (tested on a real iPhone in October 2026). How SMS links open has the details for each phone.

If the app isn't installed, the link should survive the install. On Android, Strait sends people to Google Play with the link in the install referrer, so the first open lands on the screen from the SMS. The deferred deep linking docs show what your app receives.

On Galaxy phones, watch one more thing: an unverified link opened from Messages can end up in Google Play even when the app is installed. We explain why in the Samsung Internet intent:// issue, and the fix is the same: verify your App Links.

Counting SMS taps

You'll want to know whether the SMS worked. When an Android messaging app opens a link in the browser, the browser reports which app sent it. Our engine maps Google Messages, Samsung Messages and the stock Android messaging app to the channel sms. iPhone doesn't pass that on, so add utm_source=sms and a utm_campaign to the destination, and iPhone taps join the same row. The free UTM builder makes those links, and UTM parameters for app campaigns in India suggests names for SMS, WhatsApp and push.

Checklist before your next SMS send

  • The link domain in the message (not just your website) is whitelisted on every operator portal you send through
  • The domain carries only your links
  • One URL variable per template, tagged as a URL; at least 30% of the template is fixed text
  • Transactional links have an expiry
  • Seasonal templates are used, or reactivated, before the ninety-day cut-off
  • App Links verified for the link domain (assetlinks.json checker)
  • utm_source=sms on destinations, so iPhone taps are counted too
  • A test send to your own phone on each operator before the campaign goes out

For the rest of the go-live list (keys, fingerprints, fallbacks, webhooks), see the production checklist.

Sources and how we checked