Bulk SMS in Egypt: NTRA Rules, Sender ID and Arabic Tips

How do you register a sender ID in Egypt?

Alphanumeric sender IDs let customers see your brand instead of a number, and they are the norm for business SMS. Follow this sequence:

1. List your traffic. Classify each message as transactional (OTP, delivery, account alerts) or promotional.
2. Choose names. Keep them short, recognisable and tied to your legal entity or trademark. Our data allows Latin or Arabic names up to 11 characters; check with your provider which format each operator accepts.
3. Prepare documents. Expect company registration papers, an authorisation letter on letterhead naming the IDs and your provider, and proof of your right to use the brand name if it differs from your legal name.
4. Write sample messages for each ID, in Arabic and English where relevant.
5. Submit through your provider and ask which operators will be registered.
6. Track approval per network. An ID can be live on one operator before another.
7. Test delivery on all four networks before sending to customers.

One ID per use case per entity means you register transactional and promotional IDs separately. Our Egypt sender ID page summarises the current position, and the sender ID letter generator drafts an authorisation letter. If you want our team to prepare and file the registration with you, see registrations; approval decisions stay with NTRA and the operators.

How does Arabic change SMS length and cost?

Arabic characters are not in the basic GSM 7-bit alphabet, so Arabic messages are sent as Unicode (UCS-2).

The figures come from the 3GPP standard. A 140-character Arabic promotion becomes three parts, each billed as a segment. A single Arabic letter inside an English message also switches the whole message to Unicode. Practical rules:

• Keep Arabic promotions under 70 characters when possible, and put detail behind a short link.
• Avoid decorative symbols and emoji that add characters or cause variation across handsets.
• Use Western digits consistently for amounts, order numbers and OTPs so the code is easy to read.
• Check final copy with the SMS character counter and read our guide to SMS character limits and Unicode.

What consent and opt-out practice should you follow?

Treat verifiable opt-in as mandatory for promotions.

1. Ask clearly. Name your brand, say what messages the person will get and offer a simple tick box or SMS keyword.
2. Keep the evidence. Store source, timestamp, IP address, channel and the exact wording for every number.
3. Include an opt-out in every promotion, in Arabic and English (STOP or إيقاف).
4. Suppress across channels. An opt-out on SMS should also stop marketing on WhatsApp and email unless the person has separately opted in there.
5. Separate transactional from promotional. Do not add offers to OTPs or delivery notices.

The opt-in consent generator helps draft wording. Our guide to opt-in and consent covers records in more depth.

When should you send? Timing in Egypt

We have not found a regulator-published time-of-day window for promotional SMS in Egypt, so use judgement and agree hours with your provider. Sensible defaults: daytime and early evening in Cairo time, avoiding late night and early morning; plan around Friday and prayer times if your audience expects it; and avoid Ramadan nights unless the offer is relevant. Transactional traffic (OTPs, order updates) runs at any hour. The send time planner helps, and our Ramadan campaign guide covers seasonal patterns.

A worked example: a Cairo food delivery brand

"Nile Bites" (synthetic) delivers meals in Cairo and Giza and wants OTPs, order status and a weekly offer.

• It registers two sender IDs, one for transactional traffic and one for promotions, with separate sample messages.
• It tests an OTP and an offer on Vodafone, Orange, etisalat by e& and WE before launch.
• Its Arabic offer is 64 characters plus a short link, so it stays within one Unicode segment.
• Consent is captured at account creation with a tick box; the record stores timestamp, channel and IP.
• Offers go out at lunchtime and early evening; OTPs and order status use the transactional ID at any hour.

What are the common mistakes?

• One ID for everything. Mixed traffic risks the ID and the OTP route.
• Old operator names in documents. Use "etisalat by e&" and "WE".
• Unplanned Unicode. Long Arabic copy multiplies segments.
• No consent evidence. Without timestamp, source and IP you cannot prove opt-in.
• Treating lead times as promises. 7 to 14 business days is a typical range; plan buffer.

How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to all four Egyptian networks. We prepare and file sender ID registration with you, support Arabic and English, and give you per-operator delivery reports. For current rates, see our Egypt SMS pricing page, then book a demo to plan your Egypt launch.