SYRIA (SY)

Country Summary

Country name	Syria
ISO code	SY
Region	Middle East & Africa
Mobile country code	417
Dialing code	+963

Guidelines

Two-way SMS supported	No
Twilio concatenated message support	Yes
Message length	-----
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	All traffic will be overwritten with numeric sender IDs to ensure delivery. The current political situation in Syria has left the telecommunications infrastructure in extreme disrepair. Message delivery rates in Syria are poor. Person-to-person (P2P) traffic is not permitted on our routes to Syria. Political and religious content is strictly prohibited in Syria. 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, particularly 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	Not Required	Not Supported	Not Supported	Not Supported	Not Supported
Twilio supported	---	Supported Learn more	Supported	Supported	Not Supported
Sender ID preserved	---	No	No	No	---
Provisioning time	---	---	---	---	---
UCS-2 support	---	Supported	---	Supported	---
Use case restrictions	---	---	---	---	---
Best practices	---	You may use an Alphanumeric Sender ID to reach mobile phones in Syria. However, the Sender ID will be overwritten with a long code outside Twilio’s platform.	You may use a global SMS-capable number to reach mobile phones in Syria.	You may use a global SMS-capable number to reach mobile phones in Syria. However, the number will be overwritten with a long code outside Twilio’s platform.	---

	Alphanumeric - Pre-registration
Operator network capability	Not Required
Twilio supported	---
Sender ID preserved	---
Provisioning time	---
UCS-2 support	---
Use case restrictions	---
Best practices	---

	Alphanumeric - Dynamic
Operator network capability	Not Supported
Twilio supported	Supported Learn more
Sender ID preserved	No
Provisioning time	---
UCS-2 support	Supported
Use case restrictions	---
Best practices	You may use an Alphanumeric Sender ID to reach mobile phones in Syria. However, the Sender ID will be overwritten with a long code outside Twilio’s platform.

	Long Code - Domestic
Operator network capability	Not Supported
Twilio supported	Supported
Sender ID preserved	No
Provisioning time	---
UCS-2 support	---
Use case restrictions	---
Best practices	You may use a global SMS-capable number to reach mobile phones in Syria.

	Long Code - International
Operator network capability	Not Supported
Twilio supported	Supported
Sender ID preserved	No
Provisioning time	---
UCS-2 support	Supported
Use case restrictions	---
Best practices	You may use a global SMS-capable number to reach mobile phones in Syria. However, the number will be overwritten with a long code outside Twilio’s platform.

	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.