BroadNet
Regulation BroadNet answer

How do I register an alphanumeric sender ID?

Last reviewed 2 min readReviewed by BroadNet engineering
Quick answer

Most regulators require alphanumeric sender IDs to be pre-registered before any A2P SMS is accepted, so registration is a prerequisite, not an option. The general path is: choose a compliant sender ID (up to 11 GSM-7 characters), submit your brand, use case, and sample content, then wait for regulator/operator review. Requirements and lead times differ by country — see the country guides for the exact process in each market.

Plain-language definitionVendor-neutralReviewed July 22, 2026
DiagramSender ID registration, step by step
  1. Submit your KYC packTrade licence, authorisation letter and sample messages
  2. BroadNet files the applicationWith the operators or the regulator, as the market requires
  3. Review and approval
  4. Send under your brandYour approved sender ID on every message
The long answer

Everything worth knowing, nothing that isn't.

§01

Why registration is required

In most markets the regulator and operators mandate that every alphanumeric sender ID be pre-registered and tied to a verified brand. Unregistered sender IDs are dropped by the operator's SMS firewall, and because the SMS 'from' field is trivially spoofable, registration is how networks tell a legitimate brand sender from a fraudulent one. See /answers/what-is-sender-id and /answers/what-is-sender-id-spoofing.

§02

Choose a compliant sender ID

A sender ID is limited to 11 characters using the GSM-7 alphabet, with no spaces in most markets. It should match your brand name so it passes verification — generic strings like INFO, ALERT, or OTP are commonly rejected because they can't be tied to a specific brand. Decide up front whether the ID is transactional or promotional, since some markets classify and even prefix them differently.

§03

The general steps

Submit an application (through BroadNet as your licensed aggregator) that includes your brand identity, the exact sender ID string, the use case (transactional vs promotional), and sample message content — plus proof of recipient opt-in for marketing. The regulator and/or operators then review and either approve, ask for clarification, or reject. Once approved, the sender ID is provisioned and you can send with it.

§04

Requirements differ by country

Documents, fees, allowed character sets, and review timelines vary market to market. See the country-specific guides: /answers/sender-id-registration-uae-tdra, /answers/sender-id-registration-ksa-cst, /answers/sender-id-registration-egypt-ntra, and /answers/sender-id-registration-jordan-trc. For the wider regulatory picture see /regulations/uae and /regulations/saudi-arabia.

§05

Lead times and enforcement

Registration typically takes several business days to a couple of weeks depending on the country and operator. Enforcement is strict: once your ID is registered, sending content that doesn't match its declared classification (for example promotional content under a transactional ID) can get the sender ID suspended by the operator firewall — often within hours. Classify correctly the first time. See /answers/how-to-register-sender-id linked country guides for specifics.

BNWritten by the BroadNet engineering team·Operating carrier-grade messaging since 2003, headquartered in Dubai·Editorial standards
Build with this

Need help wiring this up?

The pages below are the products and integration guides that put this concept on the wire. If you'd rather walk through it live, our engineering team takes calls same-day during MENA working hours.

Talk to our engineering team
Feedback

Was this answer helpful?

Your vote helps us prioritise which answers to expand with examples, diagrams, and code snippets.

Was this answer helpful?
Thanks — noted. We'll keep this answer maintained.
Got it. Tell us what was missing — send a quick note.

How we write and review content

Still need help?

Talk to a real engineer about your build.

We reply within one business day, and production accounts get 24/7 support. Our solutions engineers ship code, not scripts.

$ curl -X POST https://api.broadnet.me/sms/sendSms
Response SLA
Test-access requestsReply within 1 business day
Production24 / 7 · < 15 min
Operator NOC24 / 7 · pager