# Plan a market launch in one screen. - Canonical URL: https://www.broadnet.me/tools/launch-planner - Language: en - Last updated: 2026-09-26 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. Free planning tool Pick a market, a channel, a sender type and a use case. The planner returns the regulator and the documents you need, the sender-ID lead time, the direct operators, the price band, the billing currency and the fallback path, and turns it into a launch brief you can download. ## Your launch Channel Sender type Use case ## Launch brief: SMS in UAE **Regulator** TDRA **Sender-ID lead time** 5-7 business days **Operators** 2 of 3 on a direct bind **Indicative from** $0.0123 per SMS SMS · Live Sub-3-second median; two-shot OTP supported with DLR confirmation. ### Regulator and documents TDRA · Telecommunications and Digital Government Regulatory Authority Documents to prepare - UAE trade licence - signed authorisation letter on company letterhead - sample message templates (EN + AR) - traffic-type declaration **TDRA · Etisalat / e&** **Allowed format** Alphanumeric (Latin or Arabic), up to 11 chars. AD- prefix mandatory on promotional senders. **Pre-registration** Required — one sender ID per legal entity per use case **Renewal** Annual (AED 500 / year) **Common rejection causes** Generic IDs (INFO, ALERT, UPDATE), brand mismatch with the trade licence, missing AD- prefix on promotional sends, or templates that blend promo and transactional intent. **TDRA · du** **Allowed format** Alphanumeric (Latin or Arabic), up to 11 chars. AD- prefix mandatory on promotional senders. **Pre-registration** Required — registered alongside Etisalat through the operator portal **Renewal** Annual **Common rejection causes** Templates that don't match the registered category, brand collisions on the operator white-list, or non-AD- prefixed promotional senders. ### Sender-ID lead time 5-7 business days From complete paperwork to an approved sender ID. BroadNet files it with the operators on your behalf. Time to launch: Live in 5–15 business days from test-access request to production ### Price band and billing Indicative from $0.0123 per SMS SMS price band: AED 0.0452 Billing currencies: AED · USD · SAR Indicative list rate, reviewed September 24, 2026 Volume pricing available ### Operators 2 of 3 on a direct bind - Etisalat / e& Direct - du Direct - Virgin Mobile Operator-grade ### Fallback path Recommended chain: SMS (primary) → WhatsApp Business OTP after 25s no-DLR → Voice OTP after 45s. Arabic-template fallback registered alongside English. SMS · Live WhatsApp · Live RCS · Available Voice · Live ### Your launch steps 1. 01Collect the documents listed above. 2. 02File the sender ID. BroadNet submits it to TDRA and the operators. 3. 03Send test messages to your own number while the sender ID is reviewed. 4. 04Go live on the direct routes and watch every message in your console. [Coverage page](https://www.broadnet.me/coverage/uae) [Regulation guide](https://www.broadnet.me/regulations/uae) [Pricing](https://www.broadnet.me/pricing/sms) [Talk to a launch specialist](https://www.broadnet.me/contact?country=uae&topic=route-availability) From request to production ## One path to your first message, with the clock on every step. 1. 01 Request test access Reply within 1 business day A messaging engineer replies with your test credentials and books a 30-minute call on your countries, volumes and use case. 2. 02 First test message About 5 minutes after credentials Send a test message to your own verified number with the quickstart code. The delivery receipt comes back to your webhook. 3. 03 Integration 2–5 business days Build and test with your test credentials against the same endpoint as the code samples. A BroadNet engineer pairs with you on REST or SMPP. 4. 04 Approval 3–10 business days Sender identity, traffic purpose and destination rules are reviewed, and sender IDs are registered with each regulator, in parallel with your integration. 5. 05 Production Cutover day Production access and routes are switched on for your account. Your integration already calls https://api.broadnet.me. Overall: 5–15 business days from request to production for most markets; longer where a regulator's sender-ID lead time is longer. Planning guidance, not legal advice. Rules change: we confirm the current requirements with the operators before you file. ### For AI agents The same data is available to software. This page registers three read-only WebMCP tools (check_coverage, sender_id_rules, estimate_price) in browsers that support WebMCP, and the rate card is published as Markdown at /pricing.md. To send and track messages from an agent, use the BroadNet MCP server. This browser does not expose WebMCP. Nothing is registered. [BroadNet MCP server](https://www.broadnet.me/developers/mcp) [/pricing.md](https://www.broadnet.me/pricing.md) ## Questions about launching in a new market ### What do I need to send SMS in a new country? Usually three things: a sender ID registered with the regulator or the operators, the company documents they ask for (commonly a trade licence, an authorisation letter and sample templates), and content that matches the category you registered. The planner lists the exact documents and lead time for each market. ### How long does sender ID registration take? It depends on the market: from no registration at all in open markets to about two weeks where the regulator approves every sender ID. The planner shows the typical lead time from complete paperwork to an approved sender ID. ### Are the prices in the planner a quote? No. They are indicative list rates with the date they were reviewed. Volume pricing is available, and your quote confirms the per-operator price and billing currency. ### Can an AI agent use this data? Yes. In browsers that support WebMCP the page registers read-only tools (check_coverage, sender_id_rules, estimate_price), the rate card is published at /pricing.md, and the BroadNet MCP server lets an agent send and track messages with your token.