/ 01FROM AN APPOPEN YOUR APP FROM ANY APP · SMS

Make links in SMS open your app

SMS has no in-app browser, so a texted link is handed to the phone itself. Whether that ends in your app depends on verified links, and in India on your DLT template.

SMS · the problem

A texted link is handed to the phone, and an unverified link opens the browser.

What it costs you

Until your App Links and Universal Links are verified, every texted link opens a browser tab first.

What Strait does

It serves the verification files on your workspace domain, so the phone can open your app directly.

Short answer: Messages apps pass a tapped link to the phone, which first checks whether an installed app has verified the domain. With verified App Links or Universal Links your app opens directly. Otherwise the browser loads the link and the link server hands off to the app, or to the store with the link attached.

/ 02FROM AN APPPASTE A LINK

Will it open from SMS?

Paste the address your link points to and pick how the tap arrives from SMS. The answer prints like a record, stamped.

Runs the link server’s own decision code in your browser; nothing you paste is sent. The example app has an Android package and an App Store ID. More settings in the full simulator.

What the link server decides

What Strait does with a tap from SMS

Each card is the link server’s real decision for that kind of tap, worked out by running its code on the user agent the tap arrives with. The example app has an Android package and an App Store ID; the link points to https://shop.example.com/products/42.

Android, Messages opens the browser (App Links not verified yet)

What Strait sees
Android (Android 14), in the phone's browser.
Decision
Opens the app if installed, otherwise Google Play with the link attached for deferred deep linking.
App installed
The app opens at the deep link, directly from the tap.
App not installed
Google Play, with the link in the install referrer. After install, the SDK reads it and opens the right screen (a deferred deep link).

Android, Samsung Messages opens Samsung Internet

What Strait sees
Android (Android 14), in the phone's browser.
Decision
Opens the app if installed, otherwise Google Play with the link attached for deferred deep linking.
App installed
The app opens at the deep link, directly from the tap.
App not installed
Google Play, with the link in the install referrer. After install, the SDK reads it and opens the right screen (a deferred deep link).

iPhone, Messages opens Safari (app not installed)

What Strait sees
iPhone or iPad (iOS 17.5), in the phone's browser.
Decision
iPhone browser: the app did not open by itself (not installed), so it shows the "Get the app" page; the tap on it goes to the App Store; after install the app can pick up the link on first open (when install matching is on).
App installed
If the app is installed and its Universal Links are set up, iOS opens the app before the tap reaches Strait, so this page does not appear.
App not installed
A "Get the app" page. The tap on it goes to the App Store, and the app can pick up the link on first open when iPhone install matching is switched on (opt-in).

iMessage building the rich link preview

What Strait sees
A link-preview fetcher or script, not a person.
Decision
Preview (link-preview bots and requests without a browser user agent): served the preview card (title, description, image), never a redirect; counted as a preview, never billed.
App installed
No redirect. The chat shows a preview card built from the link's title, description and image.
App not installed
Same: previews never redirect and are never billed as taps.

Google Messages, Samsung Messages and Apple's Messages all pass a tapped link to the operating system rather than showing it themselves. That is good news. The phone checks first whether an installed app has verified the link's domain, and only then picks a browser.

  • Android with verified App Links: the app opens directly at the link. The link server never sees a browser request; the SDK resolves the short link and reports the open.
  • Android without verification: the link opens in the default browser, Chrome or Samsung Internet. The link server answers with the Android hand-off, which opens the app if it's installed and Google Play (with the link attached) if not. The cards above show both browsers getting the same answer.
  • iPhone with the app installed: a Universal Link on your domain opens the app from Messages. Strait's Universal Links were tested on a real iPhone in October 2026, though not yet from inside an SMS app; install matching after an App Store install is opt-in.
  • iPhone without the app: Safari loads the link and the link server shows the Get the app page; the app can pick up the link on first open.

Why a text still opens the browser

When a texted link lands in Chrome even though the app is installed, App Links verification has almost always failed. The usual causes are a missing SHA-256 fingerprint (often the Play App Signing key), an intent filter without autoVerify, or an app installed before the fingerprints were saved. The free checkers test your domain's assetlinks.json and apple-app-site-association in a few seconds.

DLT templates in India

Promotional and transactional SMS in India go through DLT, and the URLs in a message must match the template you registered. Your workspace has its own subdomain on the link domain, so you whitelist that one host, and only your links pass. Register the template with the link's base and keep the slug variable if your SMS provider allows it, or register each campaign link on its own.

A readable slug, like /diwali or /kyc, also matters in a 160-character message. People are wary of random strings in texts from businesses, and a short, branded link is more likely to be tapped.

The preview bubble

On iPhone, Messages builds the rich preview on the sender's phone, with a user agent that names the Facebook and Twitter crawlers. The link server treats it as a preview: it gets the title, description and image and is never counted. Android messaging apps may show a preview too.

Counting SMS taps

Android messaging apps usually report themselves as the source when they open the browser. Taps from Google Messages, Samsung Messages and the stock Android messaging app are labelled sms in Analytics. iPhone doesn't pass that on, so add utm_source=sms and a utm_campaign per send, and the iPhone taps join the same row.

Transactional texts (OTP follow-ups, delivery updates, payment reminders) deserve deep links too. Point each at the exact screen, and set an expiry so an old text can't open a stale order months later.

Analytics

How SMS taps are counted

Analytics files these taps under the channel sms even when the link has no UTM tags. It works that out from, in order: a utm_source on the tap or in the link’s destination, then the in-app browser’s user agent, when the tap happens inside SMS, then Android reporting that the tap came from com.google.android.apps.messaging, com.samsung.android.messaging or com.android.mms. A utm_source you set always wins, so a campaign tag like utm_source=sms-broadcast keeps its own row.

/ 03FROM AN APPTHREE STEPS

Try a real tap from SMS

  1. 1Send yourself the demo linkPaste demo.strait.link/try into SMS (a chat with yourself, a draft, a private post) and tap it on your phone. You see what your users would see first. Without our demo app installed, the tap ends on our website.
  2. 2Simulate itOpen the simulator with SMS already picked, change the link or clear an app setting, and watch the decision change.
  3. 3Trace itScan the Live Tap Trace on the home page with your phone to see each step of one real tap arrive.

Make your own link for SMS.

Free for 25,000 taps a month, no card. Every tap from SMS shows up with its own trace.