Skip to main content

UNITED ARAB EMIRATES (AE)

Locale Summary

Locale nameUnited Arab Emirates
ISO codeAE
RegionMiddle East & Africa
Mobile country code424
Dialing code+971

Guidelines

Two-way SMS supported No
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

Carriers in the United Arab Emirates are heavily filtering SMS traffic, so Twilio recommends pre-registering an Alphanumeric Sender ID to improve delivery. Unregistered Sender IDs will be replaced with generic Alphanumeric Sender IDs and may be blocked by carriers.

All promotional Alphanumeric Sender IDs must carry an AD- prefix, and this counts towards the 11-character limit. Promotional messages to the UAE can not be sent between 09:00pm to 07:00am local time. Messages sent during the restricted time period will be queued outside the Twilio platform and will only be processed for delivery during the allowed time period.

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, particularly 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 SupportedNot SupportedNot Supported
Twilio supported Required
Learn more
Not Supported --- Not Supported---
Sender ID preservedYesNo --- No---
Provisioning time2 weeksN/AN/AN/AN/A
UCS-2 supportSupportedN/AN/ASupportedN/A
Use case restrictions

Messages containing adult, gambling, or religious content are strictly forbidden. All promotional Alphanumeric Sender IDs must carry an AD- prefix. Promotional messages to the UAE can not be sent between 09:00pm to 07:00am local time. Messages sent during the restricted time period will be queued outside the Twilio platform and will only be processed for delivery during the allowed time period.

Please note that Promotional messaging is only supported for Domestic Entities and Promotional Content is not permitted for International Entities.

Alphanumeric Sender IDs are only supported through pre-registration.

N/A

Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside the Twilio platform and may be blocked by the operators. 

N/A

Best practices

For all health services related Sender ID registration requests, we will require an approval letter from the UAE health authorities.

URL shortners should be avoided as the local networks tend to filter messages containing them. 

Due to limitations related to the local infrastructure we suggest our clients to use UCS2 encoding when submitting messages containing the EURO symbol "€"

N/A

N/A

The UAE Telecoms Regulatory Authority requires the pre-registration of all customers sending to the UAE.

N/A

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

Messages containing adult, gambling, or religious content are strictly forbidden. All promotional Alphanumeric Sender IDs must carry an AD- prefix. Promotional messages to the UAE can not be sent between 09:00pm to 07:00am local time. Messages sent during the restricted time period will be queued outside the Twilio platform and will only be processed for delivery during the allowed time period.

Please note that Promotional messaging is only supported for Domestic Entities and Promotional Content is not permitted for International Entities.

Best practices

For all health services related Sender ID registration requests, we will require an approval letter from the UAE health authorities.

URL shortners should be avoided as the local networks tend to filter messages containing them. 

Due to limitations related to the local infrastructure we suggest our clients to use UCS2 encoding when submitting messages containing the EURO symbol "€"

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

Alphanumeric Sender IDs are only supported through pre-registration.

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 capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside the Twilio platform and may be blocked by the operators. 

Best practices

The UAE Telecoms Regulatory Authority requires the pre-registration of all customers sending to the UAE.

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.