UNITED ARAB EMIRATES (AE)

Country Summary

Country nameUnited Arab Emirates
ISO codeAE
RegionMiddle East & Africa
Mobile country code424
Dialing code+971
Major carriersEtisalat, du

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
Message length-----
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 preregistering a sender ID to bypass carrier filters and improve delivery. Unregistered sender IDs will be replaced with generic alpha sender IDs and may be blocked by the carriers. For marketing/promotional traffic, it is mandatory to include the necessary information on how to opt-out of receiving SMS by using the 7726 short code, which protects subscribers from receiving unwanted SMS. Any messages sent without the STOP instructions will be blocked. The recommended format for STOP instructions is as follows: To stop receiving SMS reply “b [senderID] to 7726."

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

PreregisteredAlphanumericLong CodeShort Code
Operator network capabilityRequiredSupportedNot SupportedNot Supported
Twilio supportedRequiredNot SupportedSupportedNot Supported
Sender ID preservedYes --- No ---
Provisioning time1 week------
UCS-2 support --------
Use case restrictions Only transactional traffic allowed.Alphanumeric is only supported through pre-registrationNumeric senderId would be overwritten into generic alphanumeric outside Twilio's platform--
Best practices ----You may use a global SMS-capable number to reach mobile phones in the United Arab Emirates.--
Preregistered
Operator network capabilityRequired
Twilio supportedRequired
Sender ID preservedYes
Provisioning time1 week
UCS-2 support --
Use case restrictions Only transactional traffic allowed.
Best practices --
Alphanumeric
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions Alphanumeric is only supported through pre-registration
Best practices --
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform
Best practices You may use a global SMS-capable number to reach mobile phones in the United Arab Emirates.
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --

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.