This guide walks through the nine most common reasons OTP SMS is slow or never arrives, and what to do about each. Most of them are fixable in an afternoon.

Why OTP SMS delivery is different from other messages#

A promotional SMS that lands in ten minutes is fine. An OTP usually expires in five. That changes everything about how OTP traffic should be treated:

• Speed matters more than cost. A slightly more expensive route that delivers in seconds beats a cheap route that queues.
• Every failure is visible. The user is staring at the screen, waiting.
• Volume is spiky. Logins peak in the morning and around sales; a flash sale can multiply OTP traffic in minutes.

Keep those three facts in mind — every fix below comes back to one of them.

1. The DLT template doesn't match the message#

Every commercial SMS in India must match a template approved on the TRAI DLT portal. If your OTP text differs from the approved template by even a word, an extra space or a changed variable, operators reject it. This is the most common cause of "the OTP never came".

Fix: copy the approved template text exactly, and only change what sits inside the {#var#} placeholders. Keep the OTP itself in a single variable. If you change the wording, register the new template first. Our DLT registration guide covers template rules in detail.

2. The OTP is sent on the wrong route#

OTP traffic should travel on a transactional or service route registered for it, with a header (sender ID) linked to the right template. Sending OTPs through a promotional header means DND numbers are blocked and time-window rules apply — so some users will never get the code.

Fix: check that your OTP header and template are registered under the right category, and that your provider sends them on its transactional/service route, not the bulk promotional one.

3. Phone numbers are stored in messy formats#

"98765 43210", "+91-98765-43210", "098765 43210", a number pasted from Excel with a hidden non-breaking space — they all look like the same number to a person. To a gateway, some are invalid. Numbers that arrive with invisible characters are a surprisingly common cause of silent OTP failures.

Fix: normalise every number to one format (country code plus ten digits, e.g. 919876543210) before sending, and reject entries that aren't valid mobile numbers instead of passing them to the operator. TextNation does this automatically and lists anything that isn't a mobile number in the report, uncharged.

4. OTPs wait in the same queue as bulk campaigns#

If a 2-lakh-number promotional campaign and your login OTPs share one queue, the OTPs wait their turn. That's how a marketing send at 11 am becomes a login outage at 11:02.

Fix: your provider should give OTP and transactional traffic its own priority lane that never waits behind bulk sends. We explain how priority queues work in how to deliver 10M+ messages daily.

5. No delivery reports are being watched#

Many teams send OTPs and never look at delivery reports. When an operator starts rejecting a template, or a route slows down, nobody notices until users complain.

Fix: track delivery status for OTP traffic separately, and alert on two numbers: the delivery rate over the last 15 minutes, and the share of messages still waiting for a delivery report. A sudden drop in either is your early warning.

6. Users tap "Resend" too fast#

When a code hasn't arrived after 10 seconds, users tap Resend. Each tap sends another OTP, invalidates the previous one, and adds load. Sometimes the first OTP arrives a moment later — and no longer works.

Fix: show a visible countdown (30–60 seconds) before Resend is enabled, keep the previous code valid until the new one is delivered, and offer an alternative channel on the second attempt rather than a third SMS.

7. There's no fallback channel#

SMS can fail for reasons outside your control: the phone is out of coverage, the inbox is full, a network is congested. If SMS is the only channel, the user is stuck.

Fix: offer a second channel. WhatsApp authentication templates are built for one-time codes, with a copy-code button, and most Indian smartphone users have WhatsApp. A voice call that reads out the code works on any phone. Offer the fallback after the first resend.

8. OTP abuse is eating your capacity#

Bots that hit your "Send OTP" endpoint with random numbers — OTP pumping — cost you money and can slow down delivery for real users. It usually shows up as a sudden spike of OTPs to numbers that never verify.

Fix: rate-limit OTP requests per number, per IP and per device; add a CAPTCHA after repeated attempts; and watch the ratio of OTPs sent to OTPs verified. A healthy flow verifies most codes — a falling ratio means someone is abusing the endpoint.

9. The message itself is hard to use#

Even a delivered OTP can fail if the user can't use it quickly. Codes buried in long text, missing the app name, or written in a way that phone keyboards can't auto-fill all slow people down.

Fix: put the code first, name your brand, say how long it's valid, and add the app hash if you use Android's SMS Retriever API so the code fills in automatically. For example: "482910 is your TextNation login code. Valid for 5 minutes. Do not share it."

A quick OTP delivery checklist#

• OTP text matches the approved DLT template exactly
• Sent on a transactional/service header, not promotional
• Numbers normalised before sending; invalid entries rejected
• OTPs have a priority lane that never waits behind bulk sends
• Delivery rate and pending reports monitored, with alerts
• Resend countdown and a fallback channel (WhatsApp or voice)
• Rate limits and abuse monitoring on the OTP endpoint
• Code first in the message, with brand name and validity

Getting WhatsApp template categories right is the difference between templates that sail through approval and campaigns that are paused, rejected or billed at a higher rate than you planned. This guide explains each category, how Meta decides, and how to avoid the most common surprises.

The three WhatsApp template categories#

The rule of thumb: if the message would still make sense to send even if you had nothing to sell, it's probably Utility. If any part of it promotes something, it's Marketing.

Marketing templates#

Marketing templates are the most flexible. They can include images, video, documents, buttons, links and carousels, and they can promote anything that WhatsApp's commerce policy allows.

They are also the most closely watched. Users can block or report marketing messages, and a template with poor feedback can be paused or limited by Meta. Users can also opt out of marketing messages from a business — so marketing templates need consent, relevance and frequency limits.

Utility templates#

Utility templates confirm, update or remind users about something they already started: an order, a booking, a payment, a support request. They must be specific to that transaction.

What turns a Utility template into Marketing is usually one extra line. "Your order has shipped" is Utility. "Your order has shipped — use code SAVE10 on your next purchase" is Marketing. Meta reviews the whole message, not just the first sentence.

Authentication templates#

Authentication templates carry one-time passcodes, and they are the most structured. Meta provides the message format; you supply the code. The template can add a security disclaimer and an expiry note, and it uses a copy-code or one-tap button so the user can enter the code quickly. Links, media and promotional text are not allowed.

If you're building login flows, an authentication template is a strong fallback when SMS OTPs don't arrive — see our guide on why OTP SMS fails and how to fix it.

How pricing depends on the category#

WhatsApp Business Platform pricing is set per category and per country. Meta charges for template messages by category, with Marketing typically priced highest and Authentication and Utility lower. Utility templates sent while a customer-service window is open (within 24 hours of the user's last message) are not charged.

Rates change, so always check Meta's current rate card for India before planning a large campaign. The point to remember: the category directly changes your cost, which is why recategorisation matters.

When Meta changes a template's category#

This is the surprise that catches most teams. You get a template approved as Utility, build a flow around it, and later Meta reclassifies it as Marketing — so every message now costs more, and marketing opt-outs apply.

Common triggers:

• A discount code, offer or "shop now" line inside a utility message
• Generic wording that isn't tied to a specific transaction ("Here's an update for you")
• Buttons that lead to a product catalogue rather than the order
• Sending the same "utility" text to users who never made a transaction

TextNation watches for these changes. If a template moves from Utility to Marketing while a campaign is running, the campaign pauses and shows you the change — so you decide whether to continue at the new rate, instead of finding out from the invoice.

How to get templates approved first time#

1. Pick the honest category. Submitting a promotional message as Utility to save money usually ends in rejection or recategorisation.
2. Be specific. Reference the transaction: "Your order {{1}} for {{2}} has been shipped."
3. Use sample values. Give realistic examples for every variable so the reviewer understands the message.
4. Keep variables away from the edges. A template that starts or ends with a variable, or has two variables side by side, is more likely to be rejected.
5. Match buttons to the purpose. A utility template's button should open the order, booking or ticket — not the home page.
6. Avoid near-duplicates. Many almost-identical templates are harder to manage; use variables instead.

Template categories at a glance#

• Marketing — anything promotional; most flexible; needs consent; highest cost
• Utility — specific to a user's transaction or account; lower cost; free inside an open service window
• Authentication — one-time codes only; fixed format with a copy-code button; no links or media

For a broader comparison of WhatsApp with SMS on reach, open rates and cost, read WhatsApp Business API vs SMS, or see how TextNation's WhatsApp Business API handles templates, campaigns and replies.

This guide explains what RCS business messaging is, what it can do in India today, where it beats SMS and WhatsApp, and how to roll it out without losing reach.

What is RCS business messaging?#

RCS (Rich Communication Services) is the upgrade to SMS built into Android's messaging app (Google Messages). When a business sends an RCS message, the user sees:

• A verified sender — your brand name and logo with a verification badge, instead of a six-character header
• Rich content — images, GIFs, video and rich cards with a title, description and buttons
• Carousels — several cards side by side, for products, plans or offers
• Suggested replies and actions — tappable buttons that open a link, start a call, show a location or send a reply
• Read receipts — you know when the message was read, not just delivered

The user doesn't install anything. If their phone supports RCS, the message simply arrives richer.

RCS vs SMS vs WhatsApp#

No single channel wins everywhere. SMS has the widest reach, WhatsApp has deep engagement, and RCS adds a rich, branded experience inside the inbox people already check for OTPs and alerts.

Where RCS works best#

Promotions that need visuals. A carousel of three products with "Buy now" buttons converts very differently from a 160-character SMS with a link.

Transactional journeys. Order updates with a "Track order" button, appointment reminders with "Reschedule" and "Get directions", payment alerts with "View statement".

Trust-sensitive messages. A verified brand name and logo help users tell a real message from a spoof — useful for banks, insurers and delivery companies whose names are often impersonated.

The reach question — and how fallback solves it#

Not every phone can receive RCS. iPhones, older Android phones, and devices where RCS is turned off will not get the rich version. That's why RCS should never be a separate channel you switch to — it should be the first attempt, with SMS as the automatic backup.

With RCS-first, SMS-fallback, the platform checks whether the number can receive RCS. If it can, the rich message goes out. If it can't — or the RCS message isn't delivered within a set time — the same content goes out as SMS on your DLT-registered header. Every user gets the message; the ones who can see more, do.

Building journeys with RCS#

RCS gets more powerful when one message leads to the next. A user who taps "Interested" on a carousel can automatically get a follow-up; someone who didn't read the first message can get an SMS reminder the next day. TextNation's Journey Builder lets you design these flows visually across RCS, SMS, WhatsApp and voice.

How to launch RCS business messaging#

1. Register your brand agent. Your RCS sender (the "agent") is set up with your brand name, logo, colours, description and contact details, then verified and approved before it can message users.
2. Design for rich content. Plan images (and their sizes), card titles, buttons and suggested replies. Keep text short — RCS is visual.
3. Turn on SMS fallback. Make sure every RCS message has an SMS version on a registered DLT header and template.
4. Start with transactional traffic. Measure RCS reach and read rates on messages you already send.
5. Expand to campaigns. Use carousels and rich cards for offers, with clear opt-out options.
6. Measure end to end. Compare read rates, button taps and conversions with your SMS baseline.

Is RCS right for your business?#

RCS is a strong fit if you send high volumes of transactional messages, run visual promotions, or need users to trust that a message really comes from you. Combined with SMS fallback, it upgrades the experience for every user who can receive it, without losing anyone who can't.

To compare RCS with the other channels in more depth, read WhatsApp Business API vs SMS, or explore RCS messaging on TextNation.

Whether you are evaluating an enterprise SMS provider or building your own messaging infrastructure, understanding these layers will help you ask the right questions and set realistic expectations.

Layer 1 — Carrier Connectivity: Direct Peering vs Aggregator Routing#

Every SMS ultimately travels over a telecom operator's network. How a messaging platform connects to those networks is the most fundamental architectural decision — and the one with the greatest impact on delivery rates and latency.

Aggregator routing (the common approach)#

Most SMS providers purchase capacity from wholesale SMS aggregators, who in turn connect to carriers. The typical chain looks like: your application → SMS platform → aggregator A → aggregator B → carrier → subscriber. Each hop adds latency (10–500ms per hop), introduces a potential failure point, and reduces delivery reliability. Grey routes — unauthorised paths that bypass carrier agreements — are common in aggregator networks and violate TRAI regulations.

Direct carrier peering (the enterprise approach)#

A direct carrier connection means the messaging platform has a bilateral agreement with the telecom operator and connects via a dedicated SMPP (Short Message Peer-to-Peer) link directly to the carrier's SMSC (Short Message Service Centre). The chain becomes: your application → SMS platform → carrier SMSC → subscriber.

The benefits are substantial:

• ✓Sub-100ms delivery latency for domestic messages
• ✓Direct DLR (Delivery Receipt) from the carrier — not an estimated status from an aggregator
• ✓No grey routing — 100% compliance with TRAI regulations
• ✓Higher throughput limits negotiated directly with the carrier
• ✓Dedicated connections that are not shared with other customers during peak periods
• ✓Carrier-level visibility into why a message failed (handset off, number invalid, DND, etc.)

TextNation maintains direct SMPP connections to all four major Indian carriers: Airtel, Jio, BSNL, and Vi. This means every message is routed based on the subscriber's actual current carrier (not a static lookup), and delivery receipts reflect the actual handset status.

Layer 2 — The SMPP Protocol and Throughput Management#

SMPP (Short Message Peer-to-Peer) is the industry-standard protocol for SMS communication between messaging platforms and carrier SMSCs. It operates over TCP/IP using a persistent connection (unlike HTTP, which is stateless).

Key SMPP parameters relevant to high-throughput deployments:

// Key SMPP throughput parameters
max_outstanding_pdus: 500     // concurrent unacknowledged messages per link
window_size: 256              // sliding window for pipelining
enquire_link_timer: 30s       // heartbeat to detect dead connections
session_init_timer: 10s       // connection establishment timeout
submit_sm_throttle: 1000/s    // per-link submit rate

To achieve 1M+ messages per hour, a platform needs multiple parallel SMPP connections to each carrier. A single SMPP link with a window size of 256 and 500ms average latency can theoretically sustain ~500 messages/second. To reach 1,000+ messages/second per carrier, you need at least 2–4 parallel links, with automatic load balancing across them.

Connection pooling — maintaining a pool of pre-established SMPP sessions rather than opening new connections per batch — is essential. SMPP session establishment takes 100–300ms; a cold-start approach would destroy throughput at scale.

Layer 3 — Queue Architecture and Priority Management#

Not all messages are equal. An OTP that expires in 60 seconds must be delivered immediately. A promotional campaign can afford to be delivered within a 2-hour window. Queue architecture must reflect this reality.

A production-grade messaging queue has at minimum three priority tiers:

At 10M messages/day, promotional campaigns represent the bulk of volume — often 70–80% of daily traffic. Rate-limiting P3 traffic is essential so that a sudden spike in promotional sends does not degrade OTP delivery times for other customers on the platform.

The queue itself is typically built on a distributed message broker (Apache Kafka, RabbitMQ, or AWS SQS, depending on the architecture). Consumer workers pull from the queue and submit to carrier SMPP connections. The number of consumer workers scales horizontally with load.

Layer 4 — DND Filtering, Blacklist Management, and DLT Validation#

Before any promotional message enters the queue, it must pass through regulatory filters:

1. DND/NDNC registry check — TRAI publishes a National Do Not Call (NDNC) registry. Enterprise platforms download and index this list (updated daily by TRAI) and filter all promotional submissions against it before queuing. At 10M messages/day, this filter must be a fast in-memory lookup — a hash set or bloom filter — not a database query per message.
2. Internal blacklist / unsubscribe management — Numbers that have replied with "STOP," raised complaints, or are flagged as invalid must be excluded. This list is maintained in-platform and merged with the NDNC filter before every batch send.
3. DLT parameter validation — Every message must carry a valid Entity ID, Header, and Template ID. Invalid DLT parameters result in carrier rejection. Validation at submission time (before queuing) prevents wasted capacity and helps customers identify misconfigured API calls before they become a bulk delivery failure.
4. Time-window enforcement — Promotional SMS is restricted to 9am–9pm IST by TRAI. Messages submitted for promotional delivery outside this window must be held in the queue until the window opens — not silently dropped.

Layer 5 — Retry Logic and Failure Handling#

Not every message delivers on the first attempt. Handsets are switched off, in areas with poor coverage, or temporarily unreachable. Carriers return specific error codes that indicate whether a retry is warranted:

Intelligent retry logic — as opposed to blind retry-everything approaches — is critical for both delivery rates and cost efficiency. Retrying permanently invalid numbers wastes carrier capacity and inflates customer costs.

Layer 6 — Carrier Failover and Load Balancing#

No single carrier is reliable 100% of the time. Planned maintenance windows, unplanned outages, and regional degradations happen. At 10M messages/day, a 30-minute carrier outage can mean 200,000+ undelivered messages if there is no failover.

Carrier failover requires:

• ✓Real-time health monitoring of each carrier connection — tracking submission success rates, delivery rates, and response latencies on a per-minute basis.
• ✓Automatic rerouting — when a carrier's success rate drops below a threshold (e.g., 95% within 5 minutes), traffic is automatically shifted to backup carriers.
• ✓Subscriber MNP (Mobile Number Portability) awareness — routing messages to the subscriber's current carrier, not their original carrier. India has had significant MNP adoption; routing to the wrong carrier for a ported number adds an unnecessary hop.

Load balancing across carriers also improves cost efficiency. Carriers offer different pricing tiers for volume commitments. A well-designed platform routes messages to the most cost-effective carrier for each traffic type while maintaining delivery quality thresholds.

Layer 7 — Real-Time Delivery Monitoring#

At 10M messages/day, delivery monitoring is not a reporting feature — it is an operational necessity. The monitoring stack needs to answer these questions in real time:

• What is the current delivery rate per carrier, per message type, per customer?
• Are any carrier connections degraded or failed?
• Is the queue depth growing (indicating a processing bottleneck)?
• Are any customers sending at abnormally high rates (potential abuse)?
• What is the average end-to-end latency for P1 messages in the last 5 minutes?

TextNation's analytics dashboard surfaces per-campaign and per-carrier delivery statistics in real time, with alerting for delivery rate drops below configurable thresholds. Enterprise customers can also receive webhooks for each delivery receipt event, enabling real-time status updates in their own applications.

What to Look for in an Enterprise SMS Provider#

Based on the architecture layers above, here are the questions to ask any enterprise SMS provider:

• Q1: Do you have direct carrier connections or do you use aggregators? — Direct connections = lower latency, higher delivery rates, no grey routing.
• Q2: Which Indian carriers do you have direct SMPP agreements with? — You want coverage of Airtel, Jio, BSNL, and Vi minimum.
• Q3: What is your sustained throughput capacity per customer? — Ask for limits in messages/second, not messages/month. Burst capacity matters for OTP use cases.
• Q4: How do you handle carrier failover? — Ask for specifics: detection threshold, failover time, whether it is automatic or manual.
• Q5: Do you provide real DLR from carriers or synthetic status estimates? — Some providers return "delivered" based on submission confirmation, not actual carrier DLR.
• Q6: What is your uptime SLA and how is downtime measured? — Get this in writing. Ask for historical uptime data.
• Q7: How do you handle DLT compliance on my behalf? — Do they validate DLT parameters at submission? Do they manage DND filtering?

This article breaks down the comparison across six dimensions: reach, open rates, engagement, cost, compliance overhead, and integration complexity. We end with a use-case decision matrix so you can make the call for your specific situation.

1. Reach: Who Can You Actually Message?#

SMS#

SMS works on every mobile phone in India — from a ₹500 feature phone in rural Rajasthan to the latest iPhone. There are approximately 1.1 billion mobile subscribers in India (TRAI, 2025), and virtually all of them can receive SMS. No app installation is required. No internet connectivity is needed.

The caveat: promotional SMS cannot be delivered to numbers registered on the DND/NDNC registry. As of 2025, approximately 300 million Indian numbers are DND-registered. For transactional and OTP messages, DND restrictions do not apply.

WhatsApp#

WhatsApp has approximately 500 million active users in India, making it the world's largest WhatsApp market. However, this means roughly 55% of Indian mobile subscribers are reachable on WhatsApp — a significant gap compared to SMS.

WhatsApp requires the recipient to have the app installed and an active data connection. Users in rural areas or on older devices may not receive WhatsApp messages reliably. For this reason, enterprise platforms like TextNation offer SMS fallback — if a WhatsApp message fails to deliver within a configured window, an SMS is automatically sent instead.

2. Open Rates: Who Actually Reads the Message?#

SMS achieves a 98% open rate in India, with most messages read within 3 minutes of delivery. This is not because people love SMS — it's because the notification is inescapable and the message appears in a clean, distraction-free inbox.

WhatsApp achieves 70–80% open rates, which are substantially higher than email (20–25% in India) but lower than SMS. The gap widens for promotional messages: WhatsApp users are increasingly using the "mute" and "archive" features for business messages they find irrelevant. WhatsApp also introduced the "Recent Updates" section for business broadcasts in 2024, creating a separation from personal messages.

The critical nuance: SMS open rate measures whether the message was opened, not whether it was read. A user who opens an SMS notification without reading is counted. WhatsApp's read receipts (double blue ticks) provide a more reliable signal of genuine engagement.

3. Click-Through and Conversion Rates#

This is where WhatsApp has a clear structural advantage. WhatsApp supports interactive message types that SMS cannot match:

• ✓ Quick reply buttons (up to 3) that reduce friction to a single tap
• ✓ Call-to-action buttons with URLs or phone numbers
• ✓ Rich media: images, PDFs, videos, location pins
• ✓ Product catalogues and list messages for e-commerce

Based on aggregated data from TextNation's enterprise clients across BFSI, e-commerce, and healthcare verticals in 2025: WhatsApp interactive messages achieved a 15–25% CTR compared to 6–8% for SMS links. The highest performers were WhatsApp template messages with a single, prominent CTA button and a relevant visual.

However, SMS CTR has improved with the adoption of RCS (Rich Communication Services), which brings WhatsApp-like buttons and media to the SMS channel. For operators supporting RCS (primarily Airtel and Jio in India), RCS achieves CTRs comparable to WhatsApp at SMS-equivalent costs.

4. Cost Comparison#

Cost structures differ fundamentally between the two channels:

For high-volume transactional use cases (OTPs at 500K/day, delivery alerts, bank notifications), SMS is dramatically cheaper. The math is simple: at ₹0.08/SMS, sending 100,000 OTPs costs ₹8,000. The same volume via WhatsApp, even assuming full conversation windows, would cost significantly more.

For conversational use cases — customer support, sales qualification, post-purchase follow-up — WhatsApp's per-conversation model is often more economical than per-message SMS, because a single 24-hour WhatsApp conversation window can include many back-and-forth messages for one conversation fee.

5. Compliance Overhead#

SMS compliance: TRAI DLT#

SMS in India requires TRAI DLT registration — entity, headers, and pre-approved templates. Initial setup takes 3–7 working days. Every new message type requires a new pre-approved template. The framework is prescriptive but stable and well-documented.

Ongoing compliance: maintain templates, re-verify entity annually, pass Template IDs with every API call. The compliance overhead is moderate and largely automatable via your SMS provider.

WhatsApp compliance: Meta BSP framework#

To use WhatsApp Business API, your business must be verified by Meta and connect through an official Business Solution Provider (BSP) like TextNation. The onboarding process involves:

• Facebook Business Manager account setup and business verification
• WhatsApp Business Account (WABA) creation
• Phone number registration and verification
• Message template creation and Meta approval (usually 24–72 hours)
• Quality rating management: your templates are rated based on recipient feedback

WhatsApp's compliance framework is more dynamic than DLT. Meta can change template categories, pricing, and approval criteria with relatively short notice. Template quality ratings affect your sending limits — poor-quality templates can throttle your account. This requires active monitoring that SMS does not.

6. Use Case Decision Matrix#

Use this matrix to choose the right channel for your specific use case:

The Omnichannel Answer: Use Both#

The most effective enterprise messaging strategies in India do not choose one channel — they orchestrate both. The pattern that consistently delivers the best results:

1. Transactional triggers → SMS. — OTPs, alerts, and confirmations go via SMS for speed and reach. Cost is minimised at high volume.
2. Engagement campaigns → WhatsApp. — Marketing, re-engagement, and conversion flows go via WhatsApp for richer interactions and higher CTR among opted-in users.
3. WhatsApp with SMS fallback. — For messages where delivery matters above all (payment reminders, appointment confirmations), attempt WhatsApp first and fall back to SMS automatically if undelivered within a set window.
4. Measure and optimise. — Track delivery rates, open rates, CTR, and conversion per channel per campaign type. Let data drive channel allocation over time.

TextNation's unified API lets you manage SMS and WhatsApp from a single integration, with fallback logic, unified delivery reporting, and campaign analytics across both channels — eliminating the need to maintain separate vendor relationships.

This guide covers every step of the DLT registration process as of 2026, including updated portal workflows, common rejection patterns, and how to get your SMS campaigns live without delays.

What Is TRAI DLT and Why It Exists#

The Telecom Regulatory Authority of India introduced the DLT framework in 2018 under its Telecom Commercial Communications Customer Preference Regulations (TCCCPR). The mandate became enforceable for all commercial entities in November 2020.

DLT uses a blockchain-based distributed ledger maintained by Telecom Service Providers (TSPs) — Airtel, Jio, BSNL, and Vi — to record every Principal Entity (business sending SMS), every registered sender ID (header), and every approved message template. When your SMS gateway submits a message, the TSP checks the DLT ledger in real time. If any element — entity, header, or template — is not registered, the message is rejected before it reaches the subscriber.

The goal: eliminate unsolicited commercial communications and spam, give subscribers verifiable information about who is messaging them, and create an auditable chain of responsibility for every commercial message sent in India.

Before You Register: Prerequisites#

Gather the following before starting the DLT registration process. Incomplete documents are the single biggest cause of entity registration rejection.

• PAN Card of the business — Active PAN issued to the entity (company, LLP, partnership, or proprietorship) sending SMS. Individual PANs are accepted only for sole proprietors.
• GST Registration Certificate — Must match the legal name under which you intend to register. If your GST is under a trade name that differs from the legal entity name, prepare an explanation letter.
• Certificate of Incorporation or Business Registration — For companies: MCA Certificate of Incorporation. For LLPs: LLP Agreement. For proprietorships: Shop & Establishment certificate or equivalent.
• Authorised Signatory Details — Name, designation, mobile number, and email of the person who will be the entity's DLT account holder. This mobile number must be reachable for OTP verification.
• Brand Name / Trade Name — The name you want to appear as your sender ID prefix. This must match your registered business or trademark. Mismatches are rejected.

Step 1 — Choose Your DLT Portal#

Each major TSP operates its own DLT portal. Registration on any one portal gives you a Universal Entity ID that is accepted across all operators. You do not need to register separately on every portal.

Step 2 — Entity Registration#

Entity registration creates your Principal Entity (PE) record on the DLT blockchain. This is your business identity for all commercial SMS in India.

1. Create an account — On the chosen portal, select "Register as Principal Entity." Enter your authorised signatory's mobile number. You will receive an OTP to verify the number.
2. Enter business details — Fill in Legal Name (exactly as on PAN), PAN number, GSTIN, registered address, and business category. Select the correct category — "Bank/NBFC," "Healthcare," "E-Commerce," "Education," "Government," etc. Category determines the template types you can register later.
3. Upload documents — Upload PAN card (PDF/JPG, max 2MB), GST certificate, and incorporation/registration document. File names should be descriptive (e.g., "PAN_TextNation.pdf") — portals sometimes reject files with special characters in names.
4. Accept T&C and submit — Review the terms and submit. You will receive an acknowledgement email with a reference number. Keep this — it is required if you need to follow up.
5. Verification and approval — The TSP verifies documents within 1–3 working days. On approval, you receive your Universal Entity ID (a 19-digit alphanumeric string). This ID is your DLT identity across all TSPs.

Step 3 — Header (Sender ID) Registration#

A header is the sender name that appears on the recipient's phone. TRAI defines three types:

To register a header, navigate to the "Headers" or "Sender IDs" section of your DLT portal. Enter your desired 6-character string, select the header type, link it to your registered entity, and submit. Header approval typically takes 24–48 hours.

You can register multiple headers under a single entity (e.g., separate headers for OTP, alerts, and promotions). Most enterprises register 3–5 headers to segment message types cleanly.

Step 4 — Template Registration and Pre-Approval#

Every message body must match a pre-approved template. Templates define the fixed and variable parts of your messages.

Template types and variable rules#

DLT templates use a {#var#} placeholder syntax for variable content. Key rules:

• Each variable is represented as {#var#} in the template text.
• You cannot have two consecutive variables without fixed text between them.
• The fixed portion of the template must make up the majority of the message content.
• OTP/PIN values count as variables and must use the {#var#} placeholder.
• URLs in templates must be either hardcoded or from a TRAI-whitelisted URL shortener.
• Promotional templates cannot include phone numbers or URLs that redirect to non-branded pages.

Example: OTP template#

// Approved template (Transactional, Header: TXTNTN)
Your TextNation verification code is {#var#}. Valid for 10 minutes. Do not share with anyone. — TextNation

Submitting templates#

1. In the DLT portal, go to "Templates" → "Register New Template."
2. Select the template type (Transactional / Promotional / Service).
3. Select the header this template will be sent from.
4. Enter the template content using {#var#} for each variable.
5. Provide a brief description of the template purpose (e.g., "OTP for login verification").
6. Submit. Approval typically takes 24–72 hours.
7. Once approved, you receive a Template ID. This ID must be passed with every API call to your SMS provider.

Common Rejection Reasons and How to Avoid Them#

• Entity name mismatch (very common) — The business name on PAN does not exactly match what was entered in the registration form. Solution: copy the name letter-for-letter from your PAN card.
• Two consecutive variables in a template (very common) — e.g., "Your order {#var#} {#var#} has shipped" is rejected. Fix: "Your order {#var#}, quantity {#var#}, has shipped."
• Template content too short (common) — Very short messages (under 15 characters of fixed text) are frequently rejected for not meeting the fixed-content threshold.
• Wrong template type for a header (common) — Submitting a promotional template against a transactional header. The header type and template type must match.
• Unregistered URL in promotional template (common) — URLs in promotional templates must be from TRAI-whitelisted domains or registered URL shorteners. Bare domain links to external sites are rejected.
• Document quality issues (moderate) — Blurred or cropped PDFs, password-protected files, or files exceeding the 2MB portal limit cause entity registration failures.

Timelines and What to Expect After Registration#

Once all three elements are registered and approved, you are ready to send. Your SMS provider (like TextNation) will need your Entity ID, Header, and Template ID for each message submission. These are passed in the API request so the gateway can include them in the DLT chain.

DLT entities must re-verify annually. You will receive an email reminder from the TSP portal 30 days before expiry. Failure to re-verify results in suspension of all registered headers and templates.

How TextNation Simplifies DLT Compliance#

Managing DLT registration, tracking template IDs, and passing the right DLT parameters with every API call adds overhead to your engineering and operations teams. TextNation's enterprise SMS platform handles this transparently:

• Dedicated DLT onboarding support — our compliance team guides you through entity, header, and template registration on your preferred TSP portal.
• Template ID management — store all approved template IDs in your TextNation dashboard and reference them by name in API calls.
• Automatic DLT parameter injection — the API handles Entity ID and Template ID fields so your application code stays clean.
• DND filtering applied automatically — promotional messages are filtered against the NDNC/DND registry before dispatch.
• Annual re-verification reminders — we flag expiring registrations 45 days in advance.