SAUDI ARABIA (SA)

Country Summary

Country nameSaudi Arabia
ISO codeSA
RegionMiddle East & Africa
Mobile country code420
Dialing code+966
Major carriersZain, STC, Mobily

Guidelines

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

Saudi Arabian networks have implemented strong filtering. These filters will block most messages that come from numeric sender IDs, messages that contain objectionable content, and messages that contain URLs. Furthermore, if a message is sent that has identical content to a recent message, this message will be blocked. We encourage customers who wish to deliver messages to users in Saudi Arabia to use preregistered sender IDs. 

Twilio is unable to register Sender IDs on behalf of domestic brands based in Saudi Arabia

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 Transactional messages only. Promotional messages are not permitted. Twilio is unable to register Sender IDs on behalf of domestic brands in Saudi ArabiaAlphanumeric is only supported through pre-registrationNumeric senderId would be overwritten with generic alphanumeric senderId outside Twilio's platform--
Best practices Local license and the preregistered sender ID need to be shared to deliver the SMS.Preregistration required.----
Preregistered
Operator network capabilityRequired
Twilio supportedRequired
Sender ID preservedYes
Provisioning time1 week
UCS-2 support --
Use case restrictions Transactional messages only. Promotional messages are not permitted. Twilio is unable to register Sender IDs on behalf of domestic brands in Saudi Arabia
Best practices Local license and the preregistered sender ID need to be shared to deliver the SMS.
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 Preregistration required.
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Numeric senderId would be overwritten with generic alphanumeric senderId outside Twilio's platform
Best practices --
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.