Country Summary

Country nameEgypt
ISO codeEG
RegionMiddle East & Africa
Mobile country code602
Dialing code+20
Major carriersVodafone, Etisalat, Orange, Telecom Egypt

Guidelines

Two-way SMS supported No
Number portability availableYes
Twilio concatenated message supportYes
Message length160 Characters
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.
Compliance considerations

Mobile operators in Egypt are known for blocking and filtering so it is highly recommended to send messages using pre-registered alphanumeric sender ID. 

Due to technical limitation on the mobile operator platform, delivery reports from the Vodafone network in Egypt may be delayed.

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

  1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
  2. Only communicate during an end user's daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
  4. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityRequiredNot SupportedNot SupportedSupportedNot Supported
Twilio supported Required
Learn more
--- --- Supported---
Sender ID preservedYes --- --- Yes---
Provisioning time3 weeksN/AN/AN/AN/A
UCS-2 supportSupportedN/AN/ASupportedN/A
Use case restrictions

Sending political, religious, and adult-related content is strictly prohibited.

Non-registered Alphanumeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside the Twilio platform and would be delivered at best effort.

N/A

N/A

N/A

N/A

Best practices

For local traffic, we suggest including the local brand or service name in the text, since we observe rejections of generic text (such as “Your verification code is XXXXXX”), particularly for  Etisalat. 

N/A

N/A

N/A

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Required
Learn more
Sender ID preservedYes
Provisioning time3 weeks
UCS-2 supportSupported
Use case restrictions

Sending political, religious, and adult-related content is strictly prohibited.

Non-registered Alphanumeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside the Twilio platform and would be delivered at best effort.

Best practices

For local traffic, we suggest including the local brand or service name in the text, since we observe rejections of generic text (such as “Your verification code is XXXXXX”), particularly for  Etisalat. 

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

N/A

Short Code
Operator network capabilityNot Supported
Twilio supported---
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.