Country Summary

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

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
Message length-----
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. Message templates of both transactional and marketing SMS must be whitelisted and is subjected for approval; marketing SMS is subjected to heavier filtering. Normally, membership marketing content is allowed whilst marketing content related to stocks, real estate, education, taobao, and wechat is not allowed. Approval depends largely on the SMS content/template you would send. Delivery is normally fine as long as the message templates are approved but expect certain new keywords to be blocked or filtered without warning. Unapproved template is subjected to manual screening which could result in either delivery latency or failure. Delivery report is supported and reliable over the whitelisted template route.

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, particular 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

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot SupportedNot SupportedNot SupportedNot SupportedNot Supported
Twilio supported --- --- --- Supported---
Sender ID preserved --- --- --- No---
Provisioning timeN/AN/AN/AN/AN/A
UCS-2 supportN/AN/AN/ASupportedN/A
Use case restrictions

N/A

N/A

N/A

N/A

N/A

Best practices

N/A

N/A

N/A

Whitelisted templates would be delivered with China mobile operator approved '+106%' long numbers. Non-whitelisted message templates would have their sender ID overwritten with random numeric sender outside the Twilio platform and delivery would be on best-effort basis only. Twilio highly recommends whitelisting message templates for increased deliverability.

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

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

Whitelisted templates would be delivered with China mobile operator approved '+106%' long numbers. Non-whitelisted message templates would have their sender ID overwritten with random numeric sender outside the Twilio platform and delivery would be on best-effort basis only. Twilio highly recommends whitelisting message templates for increased deliverability.

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

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.