Guidelines

Egypt (EG)

We've compiled regulatory and compliance information to help ensure you're communicating effectively and compliantly around the world.

Back to Guidelines

Locale Summary
Locale name	Egypt
ISO code The International Organization for Standardization two character representation for the given locale.	EG
Region	Middle East & Africa
Mobile country code A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.	602
Dialing code The dialing prefix used to establish a call or send an SMS from one locale to the given locale.	+20

Guidelines
Two-way SMS supported Whether Twilio supports two-way SMS in the given locale.	No
Number portability available Whether number portability is available in the given locale.	Yes
Twilio concatenated message support Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one.	Yes* For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.
Message length How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.	160 Characters
Twilio MMS support Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.	Converted to SMS with embedded URL
Sending SMS to landline numbers How Twilio handles an SMS message destined for landline telephone number.	You 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 Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. This table lists some general best practices.	Message delivery to M2M numbers is on best effort basis only. Mobile operators in Egypt are known to block and filter messages, so it is highly recommended that you send messages using pre-registered Alphanumeric Sender IDs. Due to technical limitations with our partner mobile operator’s platform, delivery reports may be delayed for domestic registered traffic. However, actual delivery is not impacted. Moreover, although concatenated messages to domestic customers are supported and delivered properly, a DLR will be provided only for the first part of those concatenated messages. For Marketing messages: Message curfew for marketing campaigns: 21:00 -09:00 local time (GMT + 02:00). No messages should be sent on Fridays, Saturdays or official holidays. 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: Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications. Only communicate during an end-user’s daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language. Do not contact end-users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

Alphanumeric

	International Pre-registration	Domestic Pre-registration	Dynamic
Operator network capability Whether mobile operators in the given country support the feature.	Not Required	Required	Supported
Twilio supported Whether Twilio supports the feature for the given country.	Supported (Optional) Learn more and register via the Console	Supported Learn more and register via the Console	Supported
Sender ID preserved In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.	Yes	Yes	Yes
Provisioning time Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.	3 weeks	3 weeks	N/A
UCS-2 support	Supported	N/A	Supported
Use case restrictions	Sending gambling, political, medicine/drug related, religious, and adult-related, alcohol, tobacco content is strictly prohibited	Sending gambling, political, medicine/drug related, religious, and adult-related, alcohol, tobacco content is strictly prohibited	The following Sender IDs have been denylisted from Orange Egypt CloudOTP FACEBOOK Facebook facebook GOOGLE Google google META and Meta MICROSOFT NOTICE VerifyOTP WASMSOTP
Best practices	We suggest our custumers selecting simple sender IDs as the operators tend to reject requests to register sender IDs that icnlude special characters.	We suggest our custumers selecting simple sender IDs as the operators tend to reject requests to register sender IDs that icnlude special characters. 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 with the Etisalat network.

Long codes and short codes

	Long code domestic	Long code international	Short code
Operator network capability Whether mobile operators in the given country support the feature.	Not Supported	Not Supported	Not Supported
Twilio supported Whether Twilio supports the feature for the given country.	---	Supported	---
Sender ID preserved In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.	---	Not Yes	---
Provisioning time Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.	N/A	N/A	N/A
UCS-2 support	N/A	Supported	N/A
Use case restrictions	N/A	N/A	N/A
Best practices	N/A	N/A	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.