Bangladesh gives its two SMS traffic categories names you will not find in any other market covered in this series. What most markets call an alphanumeric sender ID, Bangladesh calls masking SMS. What most markets call a numeric sender, Bangladesh calls non-masking SMS. The distinction is not just terminological. It determines whether your messages can reach NDNC-registered numbers, whether you can send outside business hours, which BTRC-licensed aggregator route is appropriate, and whether your brand name appears in the sender field at all. Getting the category wrong means either your messages reach the wrong numbers through the wrong route, or they fail to reach anyone reliably.
Sending business SMS in Bangladesh requires routing through an aggregator listed by the Bangladesh Telecommunication Regulatory Commission (BTRC) as an authorized A2P SMS service provider. Masking SMS, which displays your brand name in the sender field, is generally reserved for transactional and service communications and can reach NDNC-registered numbers. Non-masking SMS, which shows a numeric sender, is the standard route for promotional messages and is subject to sending-hour restrictions and NDNC filtering. Standard A2P channels in Bangladesh do not support two-way messaging. BTRC has encouraged promotional bulk SMS targeting Bangladeshi consumers to be delivered in Bengali, and current operator practice generally expects this for mass consumer campaigns.
Bangladesh is a market of approximately 180 million mobile subscribers, one of South Asia's largest, and a country where SMS remains the foundational channel for reaching populations outside Dhaka, Chittagong, and other major urban centers. For development sector organizations, NGOs, microfinance programs, health initiatives, and agricultural outreach programs, Bangladesh is a critical operating environment. The compliance framework reflects the scale and diversity of the messaging ecosystem, and several requirements have no equivalent in neighboring markets.
Four operators serve Bangladesh's mobile market. Grameenphone, operating as Telenor Bangladesh, holds the largest subscriber share at approximately 45%. Robi Axiata holds approximately 25 to 30%. Banglalink holds approximately 20 to 22%. Teletalk, the state-owned operator, holds the remainder. Grameenphone's market dominance means its network quality and routing characteristics are the primary planning consideration for any program requiring broad national reach.
All four operators are served through BTRC-licensed aggregators. Unlike markets where you can connect to a reputable international SMS API and reach local subscribers through a grey route, Bangladesh requires that all A2P SMS traffic flow through aggregators specifically listed by BTRC. Connecting through an international provider that is not BTRC-listed creates deliverability risk and regulatory exposure regardless of how reputable that provider is in other markets. Your SMS provider's BTRC compliance status should be confirmed before any Bangladesh program goes live.
The masking versus non-masking distinction is the most operationally significant structural feature of Bangladesh's SMS environment.
Masking SMS displays a brand name in the sender field, what other markets call an alphanumeric sender ID. The brand name (such as BKASH, DARAZ, or HEALTH) appears where the sender number would otherwise appear. Masking SMS is generally reserved for transactional and service communications: OTPs, banking alerts, account notifications, appointment confirmations, and operational messages arising from an existing service relationship. Masking SMS can reach numbers registered on the National Do Not Call (NDNC) registry and can generally be sent around the clock, since transactional messages arising from user-initiated actions are not subject to the same time restrictions as promotional messages.
Non-masking SMS shows the actual numeric sender rather than a brand name. Recipients see a phone number, not an organization name. Non-masking SMS is the standard route for promotional and marketing messages. It is subject to sending-hour restrictions, generally expected to be sent between 9 AM and 9 PM Bangladesh Standard Time (GMT+6), and is filtered by NDNC so that registered numbers do not receive promotional messages.
The category classification is not simply a cosmetic choice. Using masking SMS for promotional content, or routing promotional messages through a transactional category to bypass NDNC filtering, is the type of misclassification that BTRC monitors and that can result in route suspension. Establishing clear internal classification rules before building automation around either category is the discipline that keeps programs from degrading over time.
Bangladesh maintains a National Do Not Call registry managed by BTRC. Mobile subscribers can register to block promotional messages, and BTRC enforces compliance through monitoring and carrier cooperation. Organizations must ensure their promotional contact lists are checked against the NDNC before campaigns are sent.
Friday is Bangladesh's weekly day of rest, as the country has a Muslim-majority population. Even where not mandated by specific regulation, many organizations avoid promotional messaging during Friday prayer periods as both a cultural and customer experience consideration. During Ramadan, sending during prayer times carries similar sensitivity, and well-operated programs account for this regardless of whether there is a specific regulatory rule on point.
The BTRC's A2P messaging framework was strengthened significantly in 2022 when the Commission encouraged that all types of bulk SMS targeting Bangladeshi consumers should be delivered in Bengali. This guidance was issued in the context of finding that promotional messages were still arriving in English despite the policy direction. For international organizations building programs for Bangladeshi audiences, this means promotional messages should generally be prepared in Bangla for mass campaigns targeting general consumers. Technical and transactional messages for professional audiences have more flexibility in practice, but organizations should confirm current operator expectations for their specific use case.
Bengali text requires Unicode encoding, which reduces the per-segment character limit from 160 characters to 70 characters. This affects message structure: content that fits in a single SMS in English may require multiple segments in Bengali, which affects cost and message structure. Testing message length before campaign launch is more important in Bangladesh than in markets where Latin character encoding applies.
Standard A2P SMS channels in Bangladesh do not support inbound replies. Recipients cannot reply to messages sent through BTRC-licensed aggregator routes on major networks. This is the same constraint documented in Rwanda and Uganda, and it has the same design implication: any workflow built around reply-based opt-outs, acknowledgment logging, inbound keywords, or survey response capture needs an alternative architecture.
For development sector programs running field surveys, longitudinal research studies, microfinance payment acknowledgment programs, or health programs where beneficiary response matters, this is not a minor constraint. The Telerivet Android Gateway provides the practical architecture: an Android device with a local Bangladeshi SIM routes through P2P traffic rather than A2P, which the standard carrier-level restriction on inbound replies does not apply to. Recipients can reply to the local number and those replies are processed in real time by the platform workflow.
This architecture is particularly relevant for the research and development sector programs that characterize much of Telerivet's South Asian account base. A field research program coordinating with survey respondents in rural Bangladesh, a microfinance program where borrower acknowledgment of payment reminders matters for loan administration, or a health program tracking participant response to appointment reminders: all of these have genuine interactive requirements that the standard A2P route cannot satisfy. The Android Gateway was built for exactly these markets.
Design for one-way SMS by default in Bangladesh, and add interaction deliberately. The question before building any reply-based workflow is which channel that interaction actually belongs on: USSD, voice, WhatsApp where smartphone penetration allows, or the Android Gateway for SMS-based reply. Building a reply dependency into a workflow that runs on standard A2P and discovering the limitation after deployment is the most common avoidable design failure in this market.
USSD is deeply embedded in Bangladesh's mobile ecosystem, particularly for mobile money. bKash, the country's dominant mobile financial service, operates on USSD and has normalized menu-based interaction across the population. For interactive workflows where a recipient needs to choose between options, USSD is the channel most of the population has already used for financial services and is comfortable navigating.
Bangladesh's data protection framework is still developing. The country does not yet have a comprehensive general data protection law in full force. A Personal Data Protection Act received in-principle cabinet approval in November 2023 but had not been enacted by mid-2026. The Cyber Security Ordinance 2025, which replaced the Cyber Security Act 2023, governs certain aspects of data handling in digital contexts. The Bangladesh Telecommunication Act 2001 grants BTRC regulatory authority over telecommunications services including data handling by licensed operators.
Organizations running SMS programs in Bangladesh should operate on the basis that a comprehensive data protection framework is approaching, and that building GDPR-comparable consent documentation and data handling practices now is a better approach than retrofitting after the legislation is enacted. The proposed Bangladesh Data Protection Board, expected to be established when the Act is enacted, is expected to have registration and oversight powers that would apply to organizations processing Bangladeshi personal data both domestically and from abroad.
For the development sector, NGO, and research communities that form a significant part of the Bangladesh SMS operator base, maintaining documented consent, clear purpose limitation, and data subject access processes is consistent with the ethical data governance standards that donor agencies and international partners expect regardless of local law.
Bangladesh sits alongside India as the two major South Asian markets in this compliance series. The two markets differ significantly in regulatory architecture. India's three-layer DLT registration system with real-time template scrubbing is the most technically complex compliance environment in the entire cluster. Bangladesh's BTRC-licensed aggregator requirement and masking/non-masking classification are more straightforward operationally, but share India's unavailability of standard two-way A2P and the importance of using a locally compliant aggregator rather than an international API with no local operator relationships.
For organizations already operating in India under the DLT framework, Bangladesh's masking registration process will feel familiar in concept. The practical difference is that Bangladesh does not have a template-level scrubbing system. Message content is not checked in real time against registered templates in the way India's DLT system operates. The compliance risk in Bangladesh is more around misclassification of traffic type and the use of non-BTRC-listed routes than around template matching.
BYOC architecture applies in Bangladesh for the same reason it applies across Asia and Africa. The BTRC-listed aggregator carries the traffic in Bangladesh. Your consent records, suppression lists, workflow logic, delivery history, and reporting remain with your organization while only the transport layer changes. When you need to update your BTRC-listed provider or adjust routing, nothing in your program logic, consent documentation, or delivery records is disrupted.
What is the difference between masking and non-masking SMS in Bangladesh? Masking SMS displays a brand name in the sender field, similar to an alphanumeric sender ID in other markets. It is generally used for transactional and service messages and can reach NDNC-registered numbers. Non-masking SMS displays a numeric sender and is the standard route for promotional messages, subject to sending-hour restrictions and NDNC filtering. The classification determines routing, NDNC eligibility, and sending-hour rules.
Why must I use a BTRC-licensed aggregator? All A2P SMS in Bangladesh is required to flow through aggregators specifically listed by the BTRC as authorized providers. Using an international SMS API that is not BTRC-listed creates deliverability risk and regulatory exposure regardless of that provider's standing in other markets. Your provider's BTRC compliance status should be confirmed before any Bangladesh program goes live.
Can recipients reply to SMS messages I send in Bangladesh? Standard A2P channels in Bangladesh do not support inbound replies. This is a carrier-level constraint on the A2P routing infrastructure. For programs requiring two-way interaction, the Telerivet Android Gateway routes through a local SIM as P2P traffic, which supports full two-way messaging. USSD is also widely used for interactive workflows given its deep integration with Bangladesh's mobile money ecosystem.
Do promotional SMS messages need to be in Bengali? BTRC has encouraged promotional bulk SMS targeting Bangladeshi consumers to be delivered in Bengali, and current operator practice generally expects this for mass consumer campaigns. Bengali text requires Unicode encoding, which reduces the per-segment character limit to 70 characters. Message content should be tested for length before launch. Technical and transactional messages for professional or service contexts have more flexibility in practice, and organizations should confirm current operator expectations for their specific use case.
Does NDNC apply to all SMS messages? The NDNC registry filters promotional non-masking SMS. Transactional masking SMS messages, such as OTPs and account alerts arising from an existing service relationship, are generally not subject to NDNC filtering. Organizations should check their promotional contact lists against the NDNC before campaigns are sent.
This article provides general operational information and should not be considered legal advice. Organizations should consult qualified legal or data protection professionals regarding their specific compliance obligations under Bangladeshi telecommunications law and applicable data protection frameworks.
Talk to our team about building SMS programs for Bangladesh and across your South and Southeast Asian markets from one platform.