Country Summary

Country nameJordan
ISO codeJO
RegionMiddle East & Africa
Mobile country code416
Dialing code+962
Major carriersOrange, Zain, Umniah

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

The operators Zain and Orange are currently blocking any generic sender IDs. Pre-registered sender IDs: Due to filtering for Zain, traffic needs to be pre-registered for proper delivery. Application-to-person (A2P): Carriers in Jordan have implemented spam filters to prevent A2P traffic reaching their network. Spam filters can return fake delivery receipts in some cases and don’t discriminate between spam and legitimate traffic. Marketing: Please note that advertising/marketing messages require you to add the prefix “adv” before the sender ID (for example, FROM=”adv xxxx”) to be in line with the Telecom Regulation Commission of Jordan. Also these promotional messages should not be sent after 9:00 PM Amman time (GMT + 3:00).

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 capability --- --- Not SupportedNot Supported
Twilio supported --- --- SupportedNot Supported
Sender ID preservedYes --- NoNo
Provisioning time1 week------
UCS-2 support --------
Use case restrictions --------
Best practices --Alpha sender ID registration is available.----
Preregistered
Operator network capability ---
Twilio supported ---
Sender ID preservedYes
Provisioning time1 week
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices Alpha sender ID registration is available.
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
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.