Skip to main content

Country Summary

Country nameChina
ISO codeCN
RegionAsia
Mobile country code460
Dialing code+86

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
Message lengthWe recommend a maximum of 500 characters or 8 segments for UCS2 encoding for better delivery rate.
Twilio MMS supportNot Available
Sending SMS to landline numbersYou 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

Chinese networks have very strict regulations about the type of SMS content which can be sent to subscribers on their network. The networks impose heavy fines and cut off connections if these rules are breached. Customers that send messages to, from, and within China must follow all applicable laws and regulations. Broadly speaking, China messaging restrictions do not allow URLs in the content, content that is political, illegal, pornographic, fraudulent, or finance-related, including but not limited to marketing content from banks or insurance companies, loans, credit cards, securities, stocks, crude oil, futures, gold, and cryptocurrency. Restrictions include messages that violate basic principles of the China Constitution, the Ministry of lndustry and Information Technology’s “Nine Prevention Rules”, and the Ministry of Public Security’s “Five categories”. 

Twilio is currently unable to ensure that messages sent to mainland China are reliably delivered because of restrictions around content, encoding, signatures, and use case. These restrictions have resulted in the blocking of seemingly legitimate and registered customer traffic. Due to this, Twilio is currently unable to support China message registration and messages sent through Twilio would be delivered on a best-effort basis with limited support only.

General guidance

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:

  1. Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications.
  2. Only communicate during an end-user’s daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language.
  4. Do not contact end-users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

Toll FreeLong CodeShort Code
DomesticInternationalDomesticInternational
Operator network capability --- --- Not SupportedNot SupportedNot Supported
Twilio supported --- --- --- Supported---
Sender ID preserved --- --- --- No---
Provisioning time------N/AN/AN/A
UCS-2 support------N/ASupportedN/A
Use case restrictions------

N/A

N/A

N/A

Best practices------

N/A

Generic signatures may be appended and Sender ID may deliver from random local longcodes.

N/A

Toll Free - Domestic
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Toll Free - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

Generic signatures may be appended and Sender ID may deliver from random local longcodes.

Short Code
Operator network capabilityNot Supported
Twilio supported---
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Pre-registration
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Phone Numbers & Sender ID (continued)

Alphanumeric
Pre-registrationDynamic
Operator network capabilityNot SupportedNot Supported
Twilio supported --- ---
Sender ID preserved --- ---
Provisioning timeN/AN/A
UCS-2 supportN/AN/A
Use case restrictions

N/A

N/A

Best practices

N/A

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.