SAUDI ARABIA (SA)

Country Summary

Country nameSaudi Arabia
ISO codeSA
RegionMiddle East & Africa
Mobile country code420
Dialing code+966

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

Saudi Arabian networks have implemented strong filtering that blocks messages coming from Numeric Sender IDs, messages that contain objectionable content, and messages that contain URLs. Messages sent with identical content to a recent message will also be blocked. To avoid the possibility of messages to users in Saudi Arabia being blocked, be sure to pre-register your Alphanumeric Sender IDs. Promotional messages should only be sent between 08:00am and 10:00pm local time. Messages sent to mobile numbers registered in the DND list will be filtered.

Twilio is unable to register Sender IDs on behalf of domestic brands based in Saudi Arabia because of a new regulation that prohibits the re-selling of domestic traffic. 

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

Toll FreeLong CodeShort Code
DomesticInternationalDomesticInternational
Operator network capability --- --- Not SupportedNot SupportedNot Supported
Twilio supported ---
Learn more
--- Not SupportedSupportedNot Supported
Sender ID preserved --- --- --- No---
Provisioning time------N/AN/AN/A
UCS-2 support------N/ASupportedN/A
Use case restrictions------

N/A

Due to strict regulations in Saudi Arabia, we strongly recommend avoiding the use of Numeric Sender IDs. Delivery by Numeric Sender ID or any non pre-registered sender is not guaranteed and on a best-effort basis only.

Twilio strongly recommends sending only with pre-registered Alphanumeric Sender IDs.

N/A

Best practices------

N/A

N/A

N/A

Toll Free - Domestic
Operator network capability ---
Twilio supported ---
Learn more
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Toll Free - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capabilityNot Supported
Twilio supportedNot 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 supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Due to strict regulations in Saudi Arabia, we strongly recommend avoiding the use of Numeric Sender IDs. Delivery by Numeric Sender ID or any non pre-registered sender is not guaranteed and on a best-effort basis only.

Twilio strongly recommends sending only with pre-registered Alphanumeric Sender IDs.

Best practices

N/A

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

N/A

Best practices

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

Twilio is unable to register Sender IDs on behalf of domestic brands in Saudi Arabia due to a new regulation that prohibits the re-selling of domestic traffic. 

If you use Alphanumeric Sender IDs for promotional purposes such as advertising or marketing, you must affix -AD to the Sender ID. For example, Twilio-AD instead of just Twilio

If you use an existing Alphanumeric Sender ID for transactional purposes, but choose to use it for promotional purposes too, then you have to register another Account SID and register a new Sender ID which will be dedicated to promotional traffic only. You must also affix -AD to the Sender ID: for example, Twilio-AD instead of just Twilio

Shortened URLs, adult content, and gambling or virtual gambling content is prohibited. Messages containing such content will be blocked, and the account may be blacklisted.

Best practices

URLs in the message content must first be allowlisted. Sending messages with URLs without adding them to an allowlist may result in delivery failure.

If the requested Sender ID is different to the name of or not affiliated with the company requesting the Sender ID, you must submit documentation that proves the company is allowed to use the Sender ID’s brand name. 

For example, Twilio owns the brand ‘Authy’. When Twilio submits a registration request for Authy, it needs to provide a document which proves that Twilio owns the rights to use the Authy brand name.

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

N/A

Best practices

N/A

Phone Numbers & Sender ID (continued)

Alphanumeric
Pre-registrationDynamic
Operator network capabilityRequiredNot Supported
Twilio supported Required
Learn more
Not Supported
Sender ID preservedYes ---
Provisioning time3 weeksN/A
UCS-2 supportSupportedN/A
Use case restrictions

Twilio is unable to register Sender IDs on behalf of domestic brands in Saudi Arabia due to a new regulation that prohibits the re-selling of domestic traffic. 

If you use Alphanumeric Sender IDs for promotional purposes such as advertising or marketing, you must affix -AD to the Sender ID. For example, Twilio-AD instead of just Twilio

If you use an existing Alphanumeric Sender ID for transactional purposes, but choose to use it for promotional purposes too, then you have to register another Account SID and register a new Sender ID which will be dedicated to promotional traffic only. You must also affix -AD to the Sender ID: for example, Twilio-AD instead of just Twilio

Shortened URLs, adult content, and gambling or virtual gambling content is prohibited. Messages containing such content will be blocked, and the account may be blacklisted.

N/A

Best practices

URLs in the message content must first be allowlisted. Sending messages with URLs without adding them to an allowlist may result in delivery failure.

If the requested Sender ID is different to the name of or not affiliated with the company requesting the Sender ID, you must submit documentation that proves the company is allowed to use the Sender ID’s brand name. 

For example, Twilio owns the brand ‘Authy’. When Twilio submits a registration request for Authy, it needs to provide a document which proves that Twilio owns the rights to use the Authy brand name.

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.