Skip to main content

HONG KONG (HK)

Locale Summary

Locale nameHong Kong
ISO codeHK
RegionAsia
Mobile country code454
Dialing code+852

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
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

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 capabilityRequiredSupportedSupportedNot SupportedNot Supported
Twilio supported Supported Supported
Learn more
SupportedSupported---
Sender ID preservedYesYesYesNo---
Provisioning time18 daysN/AN/AN/AN/A
UCS-2 supportSupportedSupportedSupportedSupportedN/A
Use case restrictions

Pre-registration is only required on mobile operator China Mobile Hong Kong. Other Hong Kong mobile operators support non-generic Alphanumeric Sender ID

The mobile operator China Mobile Hong Kong does not support dynamic Alphanumeric Sender ID and requires Sender ID pre-registration. Sending non-registered Sender ID to this network will result in delivery failure. 

N/A

N/A

N/A

Best practices

N/A

Use only registered Alphanumeric Sender ID when sending messages to mobile operator China Mobile Hong Kong and non-generic Alphanumeric Sender ID to the other Hong Kong mobile operators.

N/A

Numeric Sender ID is not supported by mobile operators in Hong Kong and would be overwritten with either a generic Alphanumeric Sender ID or a random domestic Numeric Sender ID. 

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Supported
Sender ID preservedYes
Provisioning time18 days
UCS-2 supportSupported
Use case restrictions

Pre-registration is only required on mobile operator China Mobile Hong Kong. Other Hong Kong mobile operators support non-generic Alphanumeric Sender ID

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

The mobile operator China Mobile Hong Kong does not support dynamic Alphanumeric Sender ID and requires Sender ID pre-registration. Sending non-registered Sender ID to this network will result in delivery failure. 

Best practices

Use only registered Alphanumeric Sender ID when sending messages to mobile operator China Mobile Hong Kong and non-generic Alphanumeric Sender ID to the other Hong Kong mobile operators.

Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
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

Numeric Sender ID is not supported by mobile operators in Hong Kong and would be overwritten with either a generic Alphanumeric Sender ID or a random domestic Numeric Sender ID. 

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.