|
Locale Summary |
|
|---|---|
|
Locale name |
Hong Kong |
|
ISO code |
HK |
|
Region |
Asia |
|
Dialing code |
+852 |
|
Reachability |
Inbound |
Outbound |
|---|---|---|
|
Domestic |
Yes |
Yes |
|
International |
Yes |
Yes |
|
Toll-Free |
Yes |
N/A |
|
Outbound restrictions |
High volumes of outbound calls (e.g., exceeding 5,000 calls per day from a single entity/campaign) characterized by short average call durations (e.g., under 48 seconds) or repetitive dialer patterns may trigger automated carrier-level network blocking as they are automatically seen as potential spam or robocalls. Outbound calls from Toll Free numbers are not allowed. From March 2023, for outbound calling to Hong Kong destinations from Hong Kong caller IDs, please use Twilio numbers as the caller ID (From number). Making calls using non-Twilio phone numbers via the Verified Caller ID service will no longer be supported in alignment with the measures introduced by the Office of the Communications Authority (OFCA) to strengthen protection against scams. |
|
|
Outbound requirements |
N/A |
|
|
Best practices |
Customers should design outbound calling workflows to avoid repetitive, high-frequency, or short-duration call patterns that mimic automated robocalls or suspicious calling behavior. Customers operating high-frequency calling campaigns to Hong Kong should actively monitor answer rates and call duration metrics. A sudden drop in connection rates often indicates carrier-level filtering due to perceived spam thresholds. Distribute high-volume traffic responsibly across appropriate calling windows and legitimate caller IDs rather than concentrating short call bursts through single originating channels. |
|
|
Caller ID |
Inbound |
Outbound |
|---|---|---|
|
Domestic |
+E.164 |
Local |
|
International |
Anonymous |
+E.164 (calling to mobile) Anonymous (calling to local numbers) |
|
Toll-Free |
+E.164 |
N/A |
|
DTMF |
Inbound |
Outbound |
|---|---|---|
|
RFC.2833 format |
Yes |
Yes |
|
Emergency Calling |
Outbound |
|---|---|
|
Emergency services |
No |
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.