A2P SMS in Bangladesh: Routing and Rules

Bangladesh is one of the larger A2P messaging markets in South Asia, and one where the route your traffic takes is now as much a licensing question as a technical one. For an international sender, the practical issues are how traffic reaches the four mobile networks, who is permitted to hand it over, and what happens when that permission is withdrawn.

The networks you are actually sending to

Bangladesh has four mobile operators: Grameenphone, Robi, Banglalink and Teletalk. They differ in subscriber base, in how they handle alphanumeric sender IDs, and in filtering behaviour. A supplier can be genuinely strong on one and weak on another.

This matters when you read a rate sheet. A single “Bangladesh” line with one price is averaging across four networks. Ask for the breakdown by MCC-MNC, and when you test, split volume across all four rather than sampling whichever your test handset happens to be on.

The aggregator regime

A2P SMS delivery into Bangladesh runs through aggregators enlisted with the Bangladesh Telecommunication Regulatory Commission. The BTRC maintains a list of enlisted A2P SMS service providers, and delivery of commercial A2P traffic is expected to run through that licensed chain rather than around it.

The regulator has been actively enforcing this. The BTRC has cancelled the licences and certificates of A2P aggregators in enforcement actions reported in the national press, in one instance covering dozens of companies at once. Whatever the specifics of any single action, the direction is consistent: the regulator is treating unlicensed and non-compliant A2P delivery as something to remove from the market rather than tolerate.

For a buyer, this turns a supplier’s licence status into a commercial risk question. A route that depends on an aggregator whose enlistment is withdrawn does not degrade gradually; it stops. Ask your supplier which Bangladeshi aggregator terminates your traffic, and whether that party is currently enlisted. The BTRC publishes the list, so the answer is checkable rather than a matter of trust.

Sender IDs

Alphanumeric sender IDs are used in Bangladesh, and behaviour differs by operator and by the path traffic takes. The two failure modes to test for are replacement, where your brand name is swapped for a numeric long code, and inconsistency, where the same sender ID survives on one network and not another.

Confirm with your supplier who registers sender IDs, how long it takes, and whether registration is per operator. Then verify on a handset on each network rather than trusting the confirmation email.

Bangla script and message length

A large share of A2P traffic into Bangladesh is written in Bangla, which is not in the GSM-7 character set. That means UCS-2 encoding, and it changes the economics: a single-part Unicode message holds 70 characters against 160 for GSM-7, and concatenated Unicode parts hold 67.

Two consequences. First, your cost per message is roughly double what a GSM-7 assumption suggests, so model it properly before comparing quotes. Second, Unicode support has to be tested on the route, not assumed from the platform. A route that silently transliterates Bangla into Latin characters is useless for local-language traffic even when the delivery receipt says the message arrived.

Grey routing and why it ends badly here

Bangladesh has been a persistent target for SIM-box and grey termination, and enforcement against it is active. Traffic delivered outside the licensed chain is cheap for the same reason it is fragile: nobody in the path is paying the operator what the operator expects.

The failure mode is abrupt. A route closes, traffic stops, and sender ID reputation built over months goes with it. If you are running one-time passwords or transactional alerts into Bangladesh, that is not a risk that a lower per-message rate compensates for.

A practical checklist

• Get per-operator rates and per-operator test results, not a country average.
• Ask which enlisted aggregator terminates your traffic, and check the BTRC list.
• Test Bangla script end to end on every network before committing volume.
• Model your cost using 70-character Unicode parts, not 160-character GSM-7.
• Verify sender ID arrival on a real handset per operator.
• Keep a tested second supplier for the destination.

Regulatory detail in this market changes, and enlistment lists are updated. Treat the specifics above as the shape of the problem rather than a current compliance position, and confirm the present state with the BTRC and your supplier before you commit.

See current Bangladesh route status, or read about our A2P SMS routes and voice OTP as an alternative delivery channel.