Locale Summary
Locale name | Taiwan |
---|---|
ISO code | TW |
Region | Asia |
Mobile country code | 466 |
Dialing code | +886 |
Guidelines
Two-way SMS supported | No |
---|---|
Number portability available | Yes |
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 | Sending gambling-related content is strictly prohibited in Taiwan. Sender IDs will be overwritten with random numeric equivalents and delivery reports are not guaranteed.
|
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Not Supported | Not Supported | Not Supported | Not Supported | Not Supported |
Twilio supported | Not Supported |
Supported
Learn more | Supported | Supported | --- |
Sender ID preserved | --- | No | No | No | --- |
Provisioning time | N/A | N/A | N/A | N/A | --- |
UCS-2 support | N/A | Supported | --- | Supported | --- |
Use case restrictions | --- | --- | Non-local Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio’s platform. Local Numeric Sender IDs will be delivered intact. | --- | --- |
Best practices | --- | You may use an Alphanumeric Sender ID to reach mobile phones in Taiwan. 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 Taiwan. | You may use a global SMS-capable number to reach mobile phones in Taiwan. However, the number will be overwritten with a long code outside Twilio’s Platform. | --- |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | --- |
Best practices | --- |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported |
Supported
Learn more |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | --- |
Best practices | You may use an Alphanumeric Sender ID to reach mobile phones in Taiwan. 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 | N/A |
UCS-2 support | --- |
Use case restrictions | Non-local Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio’s platform. Local Numeric Sender IDs will be delivered intact. |
Best practices | You may use a global SMS-capable number to reach mobile phones in Taiwan. |
Long Code - International | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | --- |
Best practices | You may use a global SMS-capable number to reach mobile phones in Taiwan. However, the number will be overwritten with a long code outside Twilio’s Platform. |
Short Code | |
---|---|
Operator network capability | Not Supported |
Twilio 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.