Locale Summary
Locale name | Thailand |
---|---|
ISO code | TH |
Region | Asia |
Mobile country code | 520 |
Dialing code | +66 |
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. Thailand's telecom regulator has very strict regulations about the type of SMS content which can be sent to mobile subscribers. They may impose heavy fines and cut off connections if these rules are breached. Customers that send messages to Thailand must follow all applicable laws and regulations and must avoid sending content that is associated with pornography, politics, religion, gambling, and money.
|
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Required | Not Supported | Supported | Not Supported | Not Supported |
Twilio supported |
Required
Learn more | Not Supported | Not Supported | Supported | Not Supported |
Sender ID preserved | Yes | --- | --- | No | --- |
Provisioning time | 2 weeks | N/A | N/A | N/A | N/A |
UCS-2 support | Supported | N/A | N/A | N/A | N/A |
Use case restrictions | Customers who intend to register and send loan related content must be able to provide a license from the Bank Of Thailand. | N/A | N/A | Delivery of messages submitted with Numeric Sender IDs is on a best-effort basis and will be overwritten with a random Numeric or Alphanumeric Sender IDs. Pre-registration of Alphanumeric Sender IDs is required. | N/A |
Best practices | Local network operators tend to deactivate Sender IDs which were registered in the past but are not used for a considerable period of time. We suggest our clients make sure that they keep sending traffic periodically to the specific destination once they register their Alpha Sender IDs. If the Sender ID is deactivated due to inactivity then the customer needs to reinitiate the registration procedure. | N/A | N/A | N/A | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Required |
Twilio supported |
Required
Learn more |
Sender ID preserved | Yes |
Provisioning time | 2 weeks |
UCS-2 support | Supported |
Use case restrictions | Customers who intend to register and send loan related content must be able to provide a license from the Bank Of Thailand. |
Best practices | Local network operators tend to deactivate Sender IDs which were registered in the past but are not used for a considerable period of time. We suggest our clients make sure that they keep sending traffic periodically to the specific destination once they register their Alpha Sender IDs. If the Sender ID is deactivated due to inactivity then the customer needs to reinitiate the registration procedure. |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Long Code - Domestic | |
---|---|
Operator network capability | Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Long Code - International | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | Delivery of messages submitted with Numeric Sender IDs is on a best-effort basis and will be overwritten with a random Numeric or Alphanumeric Sender IDs. Pre-registration of Alphanumeric Sender IDs is required. |
Best practices | N/A |
Short Code | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | 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.