THAILAND (TH)

Country Summary

Country name	Thailand
ISO code	TH
Region	Asia
Mobile country code	520
Dialing code	+66
Major carriers	DTAC, True Move, AIS

Guidelines

Two-way SMS supported	No
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	AIS in Thailand has a feature that prevents subscribers from receiving SMS from non-Thai numbers. Customers can opt-out of this feature by dialing *137. 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	Supported	Not Supported	---	Not Supported
Twilio supported	Supported	Not Supported	Supported	---	Not Supported
Sender ID preserved	Yes	No	No	---	---
Provisioning time	2 weeks	---	---	---	---
UCS-2 support	---	---	---	---	---
Use case restrictions	Only transactional traffic is allowed.	Alphanumeric is only supported through pre-registration.	Non-local Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio's platform. However, local Numeric Sender IDs will be delivered intact.	---	---
Best practices	---	To preserve your Sender IDs, be sure to pre-register them. If you don't, network operators may override your Sender IDs with generic Alphanumeric Sender IDs.	---	---	---

	Alphanumeric - Pre-registration
Operator network capability	Supported
Twilio supported	Supported
Sender ID preserved	Yes
Provisioning time	2 weeks
UCS-2 support	---
Use case restrictions	Only transactional traffic is allowed.
Best practices	---

	Alphanumeric - Dynamic
Operator network capability	Supported
Twilio supported	Not Supported
Sender ID preserved	No
Provisioning time	---
UCS-2 support	---
Use case restrictions	Alphanumeric is only supported through pre-registration.
Best practices	To preserve your Sender IDs, be sure to pre-register them. If you don't, network operators may override your Sender IDs with generic Alphanumeric Sender IDs.

	Long Code - Domestic
Operator network capability	Not Supported
Twilio supported	Supported
Sender ID preserved	No
Provisioning time	---
UCS-2 support	---
Use case restrictions	Non-local Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio's platform. However, local Numeric Sender IDs will be delivered intact.
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.