Skip to main content

Country Summary

Country nameJordan
ISO codeJO
RegionMiddle East & Africa
Mobile country code416
Dialing code+962

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

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 to ensure delivery.

Application-to-Person (A2P): Carriers in Jordan have implemented spam filters to prevent A2P traffic from reaching their networks. Spam filters can return fake delivery receipts in some cases and don’t discriminate between spam and legitimate traffic.

Marketing: When sending advertising/marketing messages, you are required to add the prefix “adv” before the Sender ID (for example, FROM=”adv xxxx”) to be compliant with the Telecom Regulation Commission of Jordan. You may not send these promotional messages after 9:00 PM Amman time (GMT+3).

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 --- --- Not SupportedSupportedNot Supported
Sender ID preserved --- --- --- No---
Provisioning time------N/AN/AN/A
UCS-2 support------N/ASupportedN/A
Use case restrictions------

N/A

N/A

N/A

Best practices------

N/A

Jordan mobile operarators do not support Numeric Sender ID and these are overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to attempt delivery on a best-effort basis. Twilio highly recommends pre-registering Alphanumeric Sender IDs to avoid blocking and filtering by mobile operators.

N/A

Toll Free - Domestic
Operator network capability ---
Twilio supported ---
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

N/A

Best practices

Jordan mobile operarators do not support Numeric Sender ID and these are overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to attempt delivery on a best-effort basis. Twilio highly recommends pre-registering Alphanumeric Sender IDs to avoid blocking and filtering by mobile operators.

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 capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time12 days
UCS-2 supportSupported
Use case restrictions

If you are using an Alphanumeric Sender ID for promotional purposes, you must add the prefix “adv” before the Sender ID (for example, FROM=”adv xxxx”) to be compliant with the Telecom Regulation Commission of Jordan.

You cannot send promotional messages after 9:00 PM Amman time (GMT+3). Failure to adhere to this rule will result in messages being blocked and the potential denylisting of the account.

Best practices

N/A

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 capabilitySupportedNot Supported
Twilio supported Supported Not Supported
Sender ID preservedYes ---
Provisioning time12 daysN/A
UCS-2 supportSupportedN/A
Use case restrictions

If you are using an Alphanumeric Sender ID for promotional purposes, you must add the prefix “adv” before the Sender ID (for example, FROM=”adv xxxx”) to be compliant with the Telecom Regulation Commission of Jordan.

You cannot send promotional messages after 9:00 PM Amman time (GMT+3). Failure to adhere to this rule will result in messages being blocked and the potential denylisting of the account.

N/A

Best practices

N/A

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.