Three ways to send
an SMS in Bangladesh.
A local aggregator, a global messaging platform, or Nishchit. This page compares the categories rather than named vendors — and says plainly where Nishchit is the wrong answer.
Nobody’s price list stays still, so none is reproduced here — a rival’s rate copied into this page would be wrong within a quarter and misleading for as long as it stayed up. What follows are the differences that hold across a category, and a set of questions you can put to any provider, this one included.
What actually differs
between the three.
Generalisations about a category, not claims about any particular company. Verify each against whoever you are actually evaluating.
| LOCAL AGGREGATOR | GLOBAL PLATFORM | NISHCHIT | |
|---|---|---|---|
| Time to first message | Usually same-day, often after a sales conversation and a manual account setup. | Minutes. Self-serve signup with a card. | Minutes. Self-serve signup, no card, no KYC, live key immediately. |
| Countries | Bangladesh, sometimes neighbouring markets. | Most of the world. | Bangladesh only. A non-BD recipient is rejected at validation. |
| Sender identity | Will usually handle operator registration for you, given a trade licence and a wait. | You register the sender ID yourself with the operators, which takes weeks. | A managed sender you can use today. Customer-owned sender IDs are not available yet. |
| Bangla segment pricing | Commonly billed at the Unicode rate without the 70-character limit being explained anywhere. | Documented in general encoding terms, rarely in terms of what a Bangla message costs. | Stated on the pricing page, in the docs, and computed by a public calculator before you send. |
| Delivery reporting | Frequently presented as universal. Ask which routes actually return receipts. | Reported where the route supports it; Bangladesh specifics are often unaddressed. | Two separate fields. The primary route returns no receipts and the API says so, permanently. |
| Error model | Often a numeric code from the upstream gateway, documented thinly or not at all. | Mature, well-documented error taxonomies. | A stable code plus a doc_url linking to the anchor for that exact code. |
| Idempotency | Rarely offered. A retry usually means a second SMS and a second charge. | Generally supported. | Keys claimed before the upstream call, so a concurrent retry conflicts rather than double-sends. |
| Test mode | Often none — you test against live traffic and pay for it. | Test credentials with simulated outcomes. | A test key that never reaches a carrier, with magic numbers for deterministic failures. |
| Payment | Prepaid bundles, bank transfer or mobile money, with a local invoice. | Self-serve card, usually billed in USD. | Manual top-up against a reference. Self-serve payment is not built yet. |
| Two-way SMS | Not available on the major Bangladeshi networks. | Not available on the major Bangladeshi networks. | Not available on the major Bangladeshi networks. |
Seven questions
to ask any provider.
Including us. Each one has a correct answer that is checkable, and each one is commonly answered vaguely.
Which of your Bangladesh routes return delivery receipts, and which do not?
The single most useful question in this market, and the one most likely to produce a vague answer. If delivery confirmation is described as universal, ask for it per route. Nishchit answers: the primary route returns none.
What does a 140-character Bangla message cost compared to a 140-character English one?
The correct answer is roughly three times, because Bangla is UCS-2 at 70 characters per segment. A provider that quotes one per-SMS rate without mentioning segments is quoting the English price.
What happens if I retry a send after a timeout?
Without idempotency, a timeout you retry is two messages and two charges. Ask whether there is a key, and when it is claimed relative to the upstream call.
Can I test a failure without spending money or reaching a carrier?
Error branches that are never exercised are error branches that do not work. Ask whether there is a test key and whether failures can be forced deterministically.
What do your error responses look like, and are the codes documented?
A raw upstream code with no documentation turns every failure into a support ticket. Ask to see the error reference before you integrate, not after.
How long until I can send under my own brand name?
Alphanumeric sender IDs require operator pre-registration on the major Bangladeshi networks, and it is measured in weeks. Any answer of "immediately" deserves a follow-up question.
What is the minimum commitment, and do credits expire?
Bundles with expiry dates and monthly minimums are common. Nishchit has neither, which is easy to state and easy to verify.
Five cases where
Nishchit is the wrong answer.
A comparison page that concludes in its own favour every time is worth nothing to the person reading it. These are real and current.
You send outside Bangladesh
Nishchit is BD-only by design and rejects a non-Bangladeshi recipient at validation. If you need two countries, you need a global platform — and if you need Bangladesh properly and the rest of the world roughly, you may genuinely want both.
You need your own sender ID now
Customer-owned sender IDs are on the roadmap and not in V1. If your brand name in the from line is a launch requirement rather than a nice-to-have, an aggregator that will run the operator registration for you is the faster path today.
You need to pay by card, self-serve
Credits are added manually against a reference while the payment integration is built. If procurement cannot work with that, wait for it or use something else — we would rather say so than take the signup.
You need voice, WhatsApp or email in one contract
Nishchit does SMS in one country. Multi-channel is explicitly out of scope for V1, so a platform that bundles them will serve you better than we will.
You need inbound messages
Two-way SMS is not available on the major Bangladeshi networks, so no provider can sell it to you here. If your design depends on replies, the design needs to change rather than the provider.
The constraints apply
whoever you choose.
Bangla is billed at 70 characters per segment, alphanumeric sender IDs need operator pre-registration, two-way SMS is unavailable, and the primary route returns no delivery receipts. None of that is a property of a vendor — it is a property of the market, and it will be true of whichever provider you pick. The only real variable is whether they tell you before you integrate.
The obvious
follow-up questions.
Why does this page not name any competitors?
Is Nishchit cheaper than a local aggregator?
Is a global platform more reliable?
What is the actual argument for Nishchit?
Your product has something to say.
Give it a reliable way to say it.
Self-serve signup, live immediately. Content checked instead of paperwork.
One credit per segment at ৳0.35. No contract, no minimum.
An nk_test_ key never reaches a carrier or spends a credit.
One country, done properly — Bangla pricing, observable delivery.