OMAN (OM)

Country Summary

Country name	Oman
ISO code	OM
Region	Middle East & Africa
Mobile country code	422
Dialing code	+968
Major carriers	Oman Mobile, Ooredoo

Guidelines

Two-way SMS supported	Yes
Number portability available	Yes
Twilio concatenated message support	Yes
Message length	160 Characters
Twilio MMS support	Converted to SMS with embedded URL
Sending SMS to landline numbers	You 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	We recommend you test unicode-encoded content before sending, although it should be generally supported. Sender IDs are overwritten with either random Alphanumeric or long numbers to avoid carrier blocking and filtering. 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: Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications. Only communicate during an end user's daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

	Alphanumeric		Long Code		Short Code
	Pre-registration	Dynamic	Domestic	International
Operator network capability	Supported	Not Supported	Supported	---	Not Supported
Twilio supported	Supported	Not Supported	Supported	---	Not Supported
Sender ID preserved	Yes	No	Yes	---	---
Provisioning time	3 weeks	---	---	---	---
UCS-2 support	Supported	---	Supported	---	---
Use case restrictions	No content restrictions.	---	---	---	---
Best practices	---	Alphanumeric Sender IDs will only be preserved through pre-registration.	---	---	---

	Alphanumeric - Pre-registration
Operator network capability	Supported
Twilio supported	Supported
Sender ID preserved	Yes
Provisioning time	3 weeks
UCS-2 support	Supported
Use case restrictions	No content restrictions.
Best practices	---

	Alphanumeric - Dynamic
Operator network capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	No
Provisioning time	---
UCS-2 support	---
Use case restrictions	---
Best practices	Alphanumeric Sender IDs will only be preserved through pre-registration.

	Long Code - Domestic
Operator network capability	Supported
Twilio supported	Supported
Sender ID preserved	Yes
Provisioning time	---
UCS-2 support	Supported
Use case restrictions	---
Best practices	---

	Long Code - International
Operator network capability	---
Twilio supported	---
Sender ID preserved	---
Provisioning time	---
UCS-2 support	---
Use case restrictions	---
Best practices	---

	Short Code
Operator network capability	Not Supported
Twilio supported	Not 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.