A bulk SMS campaign is only as good as its delivery rate. In India, a clean setup on a quality route should deliver 95–98% of transactional messages and 90–95% of promotional messages. If your reports show 80% or less, you are paying for messages that never arrive — and the causes are almost always identifiable and fixable. This guide covers the delivery optimization techniques that matter on Indian networks.
1. Fix DLT Template Matching First
Since the DLT (Distributed Ledger Technology) framework went live, the single largest cause of failed SMS in India is template mismatch. Every message is checked against your registered content template before an operator accepts it. The match must be exact:
- Punctuation and spacing count. An extra space, a missing full stop, or a hyphen where the template has a colon will cause rejection.
- Variables must map to {#var#} placeholders. If your template has two variables and your message fills three dynamic values, it fails scrubbing.
- Variable length is capped at 30 characters. A long product name or URL inside a single variable silently breaks delivery.
- Template ID must be passed correctly. Most gateway APIs require the DLT template ID with each request; a wrong or stale ID gets the message dropped at the operator.
Practical fix: export your registered templates from the DLT portal, store them in your application as the source of truth, and generate messages from the template string rather than free-typing content that "should" match.
2. Keep Sender IDs and Headers Healthy
Your 6-character alphanumeric header (for example QIKSMS, displayed as something like AD-QIKSMS with the operator prefix) carries reputation. Headers that mix content types or trigger spam complaints get throttled or blacklisted, and a blacklisted header takes all its traffic down with it.
- Use separate headers for OTPs, service alerts and promotions — never send marketing on your OTP header.
- Keep headers active: operators deactivate headers and templates unused for long periods, and reactivation takes time you will not have during a campaign.
- Register headers on all operator DLT platforms (Jio TrueConnect, Airtel, Vi, BSNL) so delivery does not silently fail on one network.
3. Scrub Your Number Database
Dead numbers are pure waste — you pay for the submission, and high failure rates degrade route quality. Before every large campaign:
- Validate format: Indian mobile numbers are 10 digits starting with 6, 7, 8 or 9. Strip country codes, spaces and leading zeros consistently.
- Remove numbers that returned EXPIRED or UNDELIV in the last 3 consecutive campaigns — they are switched off, out of coverage permanently, or recycled.
- For promotional routes, expect DND scrubbing to remove a large share of your list; plan reach targets accordingly rather than resending.
- Deduplicate. Duplicate submissions inflate cost and can trigger operator-side spam filters.
4. Know How Indian Operators Behave
The four networks handle traffic differently, and a delivery strategy that ignores this will underperform on at least one of them.
| Operator | What to watch |
|---|---|
| Jio | Strictest template scrubbing; even minor content deviations are rejected. Largest subscriber base, so template hygiene here has the biggest impact. |
| Airtel | Fast delivery and quick DLRs; sensitive to sudden volume spikes from new headers. |
| Vi | Generally reliable; delivery receipts can lag during peak evening hours. |
| BSNL | Slower delivery and delayed DLRs, especially in rural circles; allow longer validity periods before treating messages as failed. |
5. Use Smart Routing, Retries and Throttling
- Multi-route failover: a good gateway resubmits messages that fail on a primary route through an alternate route automatically. For OTPs, this is essential.
- Set a sensible validity period: an OTP that arrives after 10 minutes is useless — set short validity so it fails fast and your application can offer a resend. Promotional messages can carry longer validity to ride out temporary handset unavailability.
- Respect throughput limits: pushing 500 messages per second into a route provisioned for 100 TPS creates queuing delays that look like delivery failure. Match campaign ramp-up to your account's provisioned TPS.
- Avoid peak congestion: operator SMSCs are busiest 6–9 PM and during festival days; schedule non-urgent bulk sends late morning.
6. Read Delivery Reports Properly
Optimization is impossible without reading DLRs (delivery receipts) beyond the headline percentage. The status codes tell you exactly what to fix:
| DLR status | Meaning | Action |
|---|---|---|
| DELIVRD | Reached the handset | None |
| REJECTD | Blocked at operator — usually DLT template or header mismatch | Fix template mapping; verify header registration on that operator |
| UNDELIV | Invalid, unreachable or DND-scrubbed number | Clean the number from promotional lists |
| EXPIRED | Handset off or out of coverage for the validity period | Retry later; remove after repeated expiry |
Break failure rates down per operator and per template. A campaign showing 92% overall but 60% on Jio points to a template problem on one DLT platform, not a list problem.
7. Measure Latency, Not Just Delivery
For OTPs and transactional alerts, speed is part of delivery. Track submission-to-DLR time: a healthy transactional route delivers OTPs in under 5 seconds; anything consistently above 15–20 seconds drives users to hit resend, doubling your traffic and cost. If you integrate over an HTTP API, log the gateway response ID for every message so failures can be traced end to end — our developer API returns per-message IDs and real-time DLR callbacks for exactly this purpose.
Frequently Asked Questions
Why are my SMS delivered on some networks but not on Jio?
Almost always DLT scrubbing. Jio's TrueConnect platform matches content against registered templates more strictly than other operators, so a template that passes elsewhere can fail there. Verify the header and template are registered and active on Jio's DLT portal and that message content matches the template character for character.
What is an acceptable SMS delivery rate in India?
On a clean, deduplicated list with correct DLT setup: 95–98% for transactional and OTP traffic, 90–95% for promotional traffic after DND scrubbing. Sustained rates below 85% indicate template mismatches, stale numbers or a poor-quality route.
How fast should an OTP SMS arrive?
Under 5 seconds from API submission to handset on a good transactional route. If your OTPs regularly take longer than 15 seconds, check whether you are exceeding provisioned throughput, using an overloaded route, or missing operator-level template registration that forces retries.