smler.in is Smler's default short link domain, and it also supports a DLT HEADER path, so an SMS link can carry the sender header you registered on DLT without blowing past the 30-character link limit that many SMS providers and telecom operators apply. The exact limit varies by provider. If you want the full picture of TRAI SMS compliance, including custom domains and header setup, see what TRAI requires and who whitelists what below. This page focuses on the character math and the specific restrictions you'll run into.
What is smler.in used for?
smler.in is the default domain for all Smler short links, and it also supports the DLT header path, smler.in/HEADER/{dynamicShortLinkID}, for SMS links in India that you want tied to the sender header registered on DLT. Its short length leaves as much room as possible for your HEADER and dynamic link ID, so the final URL can still fit the 30-character link limit many SMS providers and operators apply.
How many characters does the HEADER format actually use?
The math is fixed once you know the pieces. smler.in's domain, including "https://", takes 16 characters. Add the slash after it, then the 6-character Header ID (your sender header as registered on DLT) plus its slash, 7 characters, and you're at 24 characters. A 6-character dynamic ID such as abc123 brings the full link to 30 characters.
| Component | Character count | Running total |
|---|---|---|
| https://smler.in/ | 17 | 17 |
| HEADER/ (6-character Header ID plus its slash) | 7 | 24 |
| Dynamic short link ID (for example abc123) | 6 | 30 |
The 30-character figure is not a Smler rule. It is a limit many SMS providers and telecom operators apply, and it varies by provider: where your provider allows longer links, your links can be longer.
A link in this format looks like:
https://smler.in/HEADER/{dynamicShortLinkID}That structure keeps you inside the limit while still leaving a usable ID length, which is more headroom than many longer domains can offer.
Is smler.in a general url shortener or an SMS-specific tool?
smler.in is both. It is the default domain for all Smler short links, so it works as a general URL shortener for a wide range of use cases, including social media bios, blog site redirection, offers and marketing campaigns. It also supports the DLT header path, smler.in/HEADER/{dynamicShortLinkID}, which SMS senders in India use to tie each link to the sender header registered on DLT.
What other alternatives exist if I want my own branded HEADER domain?
The main alternative to using smler.in directly is bringing your own custom domain and adding HEADER support to it. That gives you the same header format with your own branding, and you whitelist your own domain on DLT instead of smler.in, for example:
https://yourbrnd.link/HEADER/{dynamicShortLinkID}Setting this up follows the same domain and header configuration steps covered in our custom brand domains guide. If your SMS links also need to route users to a specific landing experience from the root domain, see our root routing guide.
Does the tool restrict which headers or characters I can use?
Yes, in one specific way: the HEADER itself has to be the sender identifier registered with your telecom operator under India's DLT (Distributed Ledger Technology) framework, not an arbitrary string you invent. smler.in doesn't restrict what you can shorten, but it does assume the HEADER you add is the one your operator has on file, so each link points to the right sender. What lets a link through is the whitelisted domain, not the header in the path.
What does the TRAI/DLT header actually do in an SMS link?
In a Smler link, the HEADER is Smler's way to tie a short link to the sender header you registered on DLT, so every link shows which sender it belongs to. None of the TRAI directions linked on this page asks for a header in the URL. They require headers registered on DLT and links that are whitelisted, and since October 1, 2024 operators may not permit traffic with URLs that aren't whitelisted (see the direction of August 30, 2024 and the dates below). For Smler links, what you whitelist is the domain: smler.in or your own.
SMS compliance rules and why Smler was built
Why Smler built a TRAI-compliant shortener
Smler launched on October 1, 2024, the day TRAI's new rules rolled out, to fix a problem at Bokimo. Bokimo sends SMS updates to customers ordering food from partner restaurants, and the URLs in those messages now had to be whitelisted. Shorteners like Bitly and Rebrandly didn't support a format that ties each link to the sender header, so the team built one. Bokimo's SMS messages were unblocked, and customers could again open order status and review links.
Other businesses had the same problem, so Smler opened to the public. In its first 20 days it passed 1 million clicks, generated 200,000 dynamic URLs and gained 100+ signups, 15 of them paying clients.
What TRAI requires and who whitelists what
From October 1, 2024, telecom operators may not permit SMS traffic that contains URLs, APKs or OTT links that aren't whitelisted. TRAI first set this for September 1, 2024 in its direction of August 20, 2024, which also covered callback numbers, then moved the date for URLs, APKs and OTT links to October 1, 2024 in its direction of August 30, 2024, leaving the callback number timeline to be fixed separately. TRAI's directions are addressed to the operators (access providers), who apply them to senders on the DLT platform.
The whitelisting rule for links with a changing part is older. As the August 20, 2024 direction records, a TRAI direction of May 12, 2023 already told operators to allow only whitelisted URLs, APKs, OTT links and callback numbers in content templates, and, where a URL has a fixed part and a variable part, to have the fixed part whitelisted. Since TRAI's direction of November 18, 2025, every variable field in a template must also be pre-tagged, for example #url# for a link, and tagged fields are scrubbed against the pre-whitelist of URLs, OTT links, APK links and callback numbers.
The Header ID is a 6-character code that identifies the sender. Every SMS campaign must be linked to a registered Principal Entity (PE), and its Header ID must be registered on DLT. In a link like https://smler.in/HEADER/abc123:
smler.inis the domain. The sender whitelists it once on DLT.HEADER/is your Header ID. It keeps each link tied to your sender header. It is not something you whitelist with the domain.abc123is the code. It changes per link without re-whitelisting and doesn't affect compliance.
The same model works on your own domain, as https://yourbrnd.link/HEADER/abc123, where you whitelist yourbrnd.link. A custom domain is more recognizable to recipients, can be whitelisted, and lets you protect your URLs from misuse. Smler also screens destination URLs against TRAI standards before shortening.
Smler provides the tools, but registering and whitelisting is the sender's job:
- Register your custom domain or subdomain in Smler.
- Add your Header ID when creating short links. Headers for custom domains can also be set from the Team Dashboard.
- Register your Header ID on the DLT platform, and submit your domain (
smler.inor your own domain or subdomain) for whitelisting with your telecom operator. The Header ID identifies the sender, and the domain or subdomain must be approved by the operator. - Monitor your campaigns to confirm your links are whitelisted and ready for SMS delivery.
How India's SMS rules have tightened since 2024
India's SMS rules did not tighten in one step in 2026. TRAI added them direction by direction from 2024, and each one ran on a fixed date:
| Date | What happened | TRAI source |
|---|---|---|
| October 1, 2024 | Traffic with URLs, APKs or OTT links that aren't whitelisted is not permitted. The callback number timeline was left to be fixed separately. | Direction, August 30, 2024 |
| December 11, 2024 | Messages are rejected when the chain of telemarketers between the sender (Principal Entity) and the operator is not defined or doesn't match the declared chain. | Direction, November 30, 2024; Press Release 92/2024 |
| October 16, 2025 | The Joint Committee of Regulators discussed misuse of shortened URLs and mandatory whitelisting of all URLs, OTT links, APKs and callback numbers sent in SMS. | Press Release 112/2025 |
| November 18, 2025 | Every variable field in an SMS template must be pre-tagged (such as #url#, #urlott# or #cbn#), and tagged fields are scrubbed against the pre-whitelist of URLs, OTT links, APK links and callback numbers. After a 60-day logger period, messages that fail variable tag validation are rejected and not delivered. | Direction, November 18, 2025; Press Release 133/2025 |
| February 13, 2026 | TRAI reported its 2025 enforcement against unregistered telemarketers: 731,120 notices issued and 184,482 telecom resources disconnected. | Press Release 20/2026 |
| March 13, 2026 | TRAI released the draft Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026 for consultation. | Press Release 38/2026 |
Non-compliant messages are rejected, not filtered silently. During the chain binding changeover in late 2024, and for the first 60 days of variable tag scrubbing, messages that failed the check were still delivered but flagged with error codes or fault messages for the sender. After that, messages that fail the check are rejected, as the November 18, 2025 direction and Press Release 92/2024 describe.
TRAI also gave its reason for watching links closely. Its Press Release 58/2024 of August 27, 2024 says fraud takes place through malicious links sent in the variable parts of messages, and the August 20, 2024 direction notes that malicious APKs and URLs were found in some messages.
What an SMS policy should cover
- How consent is captured and stored (timestamped, auditable)
- Message frequency caps per user per campaign
- Approved link domains for tracking
- Escalation steps if a carrier flags or blocks a campaign
- A review cadence; quarterly is common
Centralize link creation: ad hoc URLs from individual marketers create inconsistency, while bulk shortening keeps every link in the same compliant structure. Link-level analytics catch delivery drops early. To stay current, follow TRAI, the FCC and national telecom authorities, review carrier policy documents quarterly, audit existing campaign links for compliant domain structure, and test new templates in a sandbox before full rollout.
Shared short domain or your own build?
- No short domain to buy. Short domains are often expensive, and you have to manage renewals and keep them working. You can start shortening immediately on the smler.in domain, without that upfront investment.
- No API to maintain. Building a TRAI-compliant shortener API could take up to two days. The real work starts after: monitoring, uptime and scaling. If your shortener goes down, so does your communication with customers. Smler handles the uptime and technical maintenance.
- Dynamic URLs stay traceable. Whether your SMS links carry tracking, reviews or order updates, the header ties each one to your sender, and the whitelisted domain is what lets it through.
How do I start using smler.in for an SMS campaign?
Register your account, connect the HEADER assigned to your sender ID, and generate links in the HEADER/{dynamicShortLinkID} format shown above. From there you get the same tracking and analytics available across Smler, including click and delivery data on every link you send. Pricing for the service is listed here: smler.in pricing.
