Choosing a bulk SMS provider in India looks like a pricing decision and almost never is. Two providers quote within a paisa of each other; six months later one campaign is landing at 97% and the other is quietly failing on a third of your database, and nobody can tell you why because the reports do not go deep enough to show it.
The rate is the easiest thing to compare, which is why every buyer starts there and why every bulk SMS provider leads with it. This guide is the other way round: the fourteen things worth scoring first, and the rate last.
Score any bulk SMS provider on delivery reporting, DLT handling, billing model and support before you compare rates. Ask two questions almost nobody asks: are you billed per message sent or per message delivered, and who registers your DLT entity, sender ID and templates. Those two answers change your real cost and your time-to-launch far more than the quoted per-SMS price does.
- Compare delivered cost, not list rate. A quote billed on messages sent is not the same product as one billed on messages delivered.
- DLT is three separate registrations — entity, sender ID and every content template. Ask who does them and whether it is charged.
- Ask for the delivery rate on your route, not the marketing average. A provider who cannot produce operator-level receipts cannot prove anything.
- Regional-language messages cost roughly double. Unicode fits about 70 characters per part instead of 160.
- Promotional and transactional are different products with different rules, windows and reach. Know which you are buying.
- Score 14 criteria before you look at price again. A cheap bulk SMS provider with no failure visibility is cheap to buy and expensive to run.
Why choosing a bulk SMS provider is harder than it looks
Bulk SMS in India is not a commodity, even though it is sold like one. Three things vary enormously between bulk SMS providers, and none of them appear on a pricing page.
Routes differ
Two bulk SMS providers can quote the same rate and deliver very differently, because they buy connectivity from different operators on different route qualities. The only way to know is to test on your own database.
Reporting differs
Some bulk SMS providers show you operator-level delivery receipts and per-campaign failure reasons. Others show a total and a percentage. You cannot fix what you cannot see, and you cannot argue an invoice you cannot audit.
Compliance load differs
DLT registration is mandatory and fiddly. Some bulk SMS providers absorb it into onboarding; others hand you a portal login and wish you luck. That difference is a week of your time, minimum.
The two pricing models, and who each one suits
Set the numbers aside for a moment — the model matters more than the figure inside it, because the model decides how your cost behaves as you grow.
Volume slabs
Your per-SMS rate falls as committed volume rises. It reads well on a pricing page, but the attractive rates sit behind a large upfront commitment, and that money becomes credits rather than cash. If your volume is seasonal or uncertain, you are buying a discount you may never reach and cannot get back.
Flat rate
One price regardless of volume. Less dramatic on a landing page, but budgeting becomes one multiplication, there is no penalty for a quiet month, and you are never negotiating for a rate you were told existed.
When a slab rate is quoted, ask what the commitment is, what happens to unused credits, and whether the credits expire. A rate you cannot reach is not a rate, and credits you cannot spend are not a discount.
Are you billed per message sent, or per message delivered?
This is rarely advertised and it changes your real cost more than any slab does. Indian databases always contain disconnected numbers, DND-filtered numbers and handsets that are simply off. If you are billed the moment a message is processed, you pay for every one of them.
What the same quote actually costs you
Take any quoted rate. Apply a realistic delivery rate. The two billing models diverge immediately.
This single distinction routinely outweighs the difference between two providers’ headline rates. Get the answer in writing.
The 14 criteria to score any bulk SMS provider against
Take your shortlist, score each bulk SMS provider out of 14, and only then open the pricing conversation. The exercise takes an afternoon and routinely reorders the list.
Score your shortlist out of 14 before you look at price again. A provider that fails on failure visibility and DLT support is not cheap — it is cheap to buy and expensive to run, and you will not find out which until a campaign underperforms and nobody can explain it.
Delivery rates: what to actually ask for
Every bulk SMS provider claims a high delivery rate. The claim is close to meaningless without three qualifiers, so ask for all three.
- On which route Transactional routes run considerably higher than promotional ones, because promotional traffic is filtered against DND registration. A blended average hides that.
- Over what period A figure from a good week is not a figure. Ask for a rolling 30-day number.
- Measured how Operator delivery receipts, or the provider’s own assumption that a message left the gateway? These are very different claims.
Above 95% on transactional routes is a reasonable expectation. Promotional will be lower and that is normal, not a failing. What is not normal is a provider who cannot produce the number for your traffic when asked.
DLT compliance, and where it goes wrong
Every commercial SMS to an Indian number must pass through the DLT framework mandated by TRAI under the Telecom Commercial Communications Customer Preference Regulations. It is not one registration but three, and each is a separate opportunity to lose a week.
Principal entity
Your business registers itself on a DLT platform. Documentation-heavy, done once.
Sender ID
The six-character header your messages come from. Must be registered and approved before use.
Content templates
Every message format, registered individually with variable fields declared. This is where most delays happen.
An unregistered or mismatched template does not throw a loud error. It simply fails to deliver, often silently, and you find out when someone notices the OTPs stopped arriving. Ask any prospective bulk SMS provider how their platform surfaces template rejections — and how quickly.
A provider who registers your entity, header and templates as part of onboarding saves you a week of portal navigation and a lot of rejected submissions. One who hands you a login has not sold you a managed service. Step-by-step walkthrough: How to get a DLT Template ID ↗
Regional languages change your economics
An English SMS fits 160 characters in a single message part. A message in Hindi, Tamil, Bengali or any other Indian script uses Unicode encoding, which fits 70 characters per part. That is not a carrier policy but the GSM 03.38 encoding standard: an SMS payload is 140 bytes, which holds 160 seven-bit characters or 70 sixteen-bit ones.
The practical effect is that the same message, translated, often costs about twice as much to send — because it becomes two parts instead of one. If a meaningful share of your audience is served in a regional language, model your volume in parts rather than messages before you compare any two quotes.
Bulk SMS provider red flags worth taking seriously
None of these are automatically disqualifying. All of them are worth a direct question before you commit.
- Flag 1 A delivery rate quoted with no route, period or measurement method attached.
- Flag 2 Reports that show totals but not per-campaign failure reasons.
- Flag 3 Vagueness about whether billing is on sent or delivered messages.
- Flag 4 Credits that expire, particularly on the larger commitments where the good rates live.
- Flag 5 DLT described as “your responsibility” with no onboarding support offered.
- Flag 6 A setup or account-opening fee that appears only after you ask for a contract.
Eight questions for the sales conversation
Ask these in order. The answers will separate your shortlist faster than any pricing page.
What to ask, and why it matters
Write the answers down. Ambiguity on any of these is itself an answer.
What to prioritise, by monthly volume
The same fourteen criteria matter at every size, but the weighting changes considerably.
Startup or small business
- Prioritise no minimum commitment and no setup fee
- Slab models will leave you in the entry band indefinitely
- Avoid credit expiry — at low volume you will not burn through a pack
- Weight ease of use highly; you will not have a developer on hand
Growing D2C or SaaS
- This is the band where billing model costs you the most
- Weight delivered-vs-sent billing and failure visibility above everything
- API quality and CRM integration start to matter as sends get automated
- Test on your own database before committing to any volume tier
Enterprise
- Get quotes from at least four providers — at this scale everyone negotiates
- Insist that sent-versus-delivered billing is stated explicitly in the contract
- Weight channel breadth: consolidating SMS, WhatsApp, RCS and voice with one vendor usually beats a marginal rate difference
- Ask for route-level delivery reporting as a contractual deliverable, not a favour
We are a provider, and this is the checklist we expect to be scored on
We are UDO, a bulk SMS provider in India, so treat this guide as coming from an interested party — but the criteria above are the ones we would want a buyer to apply to us, because they are the ones that separate a working messaging programme from a cheap one that quietly underperforms.
We bill on delivered messages, register DLT entity, header and templates as part of onboarding, and provide exportable delivery receipts. If you are running this checklist across a shortlist, ask us the same eight questions you ask everyone else and compare the answers.
Run your checklist
Frequently asked questions
Score your shortlist against delivery reporting, DLT handling, billing model, API quality and support before comparing rates. The two questions that matter most are whether you are billed per message sent or per message delivered, and who registers your DLT entity, sender ID and content templates. Both change your real cost more than the quoted price does.
It varies by bulk SMS provider and is rarely advertised. If you are billed on sent messages at 92% delivery, you pay roughly 8.7% above the quoted rate per message that actually reached someone. At 85% delivery it approaches 18%. Get the answer in writing before comparing quotes.
Above 95% on transactional routes is a reasonable expectation. Promotional routes run lower because of DND filtering, which is normal. Ask for a rolling 30-day figure for your specific route, measured from operator delivery receipts rather than gateway acceptance.
Yes, and it is three separate registrations: your business as a principal entity, your sender ID or header, and every content template you intend to send. TRAI mandates all three. Some bulk SMS providers complete them during onboarding; others hand you a portal login.
Transactional messages such as OTPs, order updates and service alerts reach all numbers including DND-registered ones and can be sent around the clock. Promotional messages are marketing, are filtered by DND preferences, and are confined to a permitted daytime window that ends at 9pm.
Indian scripts require Unicode encoding, which fits 70 characters per message part instead of 160 under the GSM 03.38 standard. A message that was one part in English frequently becomes two in Hindi or Tamil, so the same campaign costs about twice as much to send. Model your volume in parts, not messages.
No. Delivered cost, failure visibility and DLT support change your real spend far more than a paisa on the list rate. A bulk SMS provider that cannot show you why a campaign failed cannot help you fix it, and that costs more over a year than any rate difference.
You should insist on it. Run a small pilot against a sample of your own database rather than a clean test list — route quality and delivery rates only reveal themselves against real contacts. Keep the pilot small, but make it representative: same mix of operators, circles and message types you actually send.
