Send SMS to Hong Kong
from $0.0200/msg

Hong Kong Mobile Operators: Direct Interconnect and Coverage

SmarTone (30% market share): Hong Kong's largest network operator, with strong coverage in urban and semi-urban areas. SmarTone specializes in premium data and enterprise services. smsroute.cc maintains a direct SS7 link to SmarTone, guaranteeing sub-50ms delivery latency to this network.

Hong Kong Telecommunications (HKT, 28% market share): A legacy operator with comprehensive fixed-line and mobile integration. HKT's mobile subscriber base is stable and skews toward business customers. Our direct interconnect ensures that HKT subscribers receive SMS within 50–70ms.

China Mobile Hong Kong (CMHK, 26% market share): A subsidiary of China Mobile, offering competitive data rates and international roaming. CMHK's network quality is high, and delivery success to CMHK numbers averages 99.3%. smsroute.cc routes to CMHK via a dedicated SMPP gateway.

CSL/Citic Telecom Vodafone (16% market share): A smaller but important carrier, historically known as CSL Mobile and now operating as Citic Telecom Vodafone. Our interconnect to this network carries 99.1% delivery success. Message delivery to CSL numbers typically completes within 60–80ms.

Combined, these four operators control 100% of Hong Kong's mobile market. smsroute.cc's routing logic automatically selects the optimal carrier for each recipient based on the dialed number prefix. You submit a single API request with a +852 E.164 number, and our platform handles routing transparently.

Pricing Comparison: smsroute.cc vs. Twilio, Vonage, and Others

The table below compares smsroute.cc's per-SMS price to six competitors for Hong Kong delivery:

For a 100,000-message campaign to Hong Kong:

• smsroute.cc: 100,000 × $0.0200 = $2,000
• Twilio: 100,000 × $0.0417 = $4,170
• Savings: $2,170 (52% cheaper)

smsroute.cc's pricing advantage stems from our direct SS7 interconnect with Hong Kong operators, elimination of platform overhead, and crypto-native payment processing (no processor fees). We pass these savings directly to you. All prices are per SMS segment; concatenated messages (those exceeding 160 GSM-7 or 70 UCS-2 characters) are charged at the segment rate, not the message rate.

No setup fees, no monthly minimums, no hidden surcharges. Payment is crypto-only: Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5.

GSM-7 vs. UCS-2 Encoding: Impact on Hong Kong SMS Costs and Delivery

GSM-7 encoding supports the 27 letters of the Latin alphabet, digits, basic punctuation, and a small set of accented characters. A single SMS in GSM-7 holds up to 160 characters; concatenated SMS allow up to 153 characters per segment (7 bytes reserved for concatenation headers). In Hong Kong, English-language messages—such as "Your verification code is 123456"—use GSM-7 and fit in 1 segment.

UCS-2 encoding supports all Unicode characters, including Traditional Chinese, Cantonese tone marks, emoji, and multi-byte symbols. A single UCS-2 SMS holds 70 characters; concatenated UCS-2 SMS allow 67 characters per segment. Any message containing Chinese, accented Latin, or emoji automatically triggers UCS-2 encoding. A customer notification in Cantonese, "您的帳戶已成功認證，可以開始交易。" (Your account has been verified and you may begin trading), is 22 characters but requires 1 UCS-2 segment. However, combining both English and Chinese in one message still results in UCS-2 encoding for the entire message.

smsroute.cc's API automatically detects the character set and applies the correct encoding—you do not need to specify it. Our dashboard displays the segment count as you compose your message. For bulk campaigns, we recommend composing separate messages for English and Cantonese where possible, to avoid the character-count penalty of UCS-2.

Latency and Delivery Performance to Hong Kong

smsroute.cc achieves 48 milliseconds median latency (p50) and 72 milliseconds at the 95th percentile (p95) for SMS delivery to Hong Kong. This means that if you send 100 messages simultaneously, 50 of them will be delivered to the mobile network within 48ms, and 95 of them within 72ms. The remaining 5% may take up to 150–200ms, typically due to transient congestion on the recipient's carrier network.

Delivery success is 99.2%, measured as the percentage of SMS that reach the recipient device or carrier-side storage (for temporarily powered-off phones). This figure is calculated from 30 days of production traffic across all four Hong Kong operators. The remaining 0.8% of non-delivered messages fall into two categories:

• Invalid or deactivated numbers (0.5%): The phone number is syntactically valid but the carrier reports that no subscriber is associated with it, or the number has been disconnected.
• Network-side rejections (0.3%): The carrier network rejects the message due to originating-point code (OPC) filtering, content filtering (spam keywords), or rate-limit exceeded. These rejections are rare with smsroute.cc because our sender IDs are pre-registered with each carrier.

smsroute.cc maintains 99.9% platform uptime, backed by redundant message queues, multiple data centers, and automatic failover. If a message cannot be delivered on the first attempt (e.g., temporary carrier congestion), it is automatically retried up to 5 times over a 24-hour window. Retries respect quiet hours and frequency limits per the Hong Kong Code of Practice.

For time-sensitive messages (OTP codes, payment confirmations), use the `/sms/send?priority=high` parameter to route through our highest-quality, lowest-latency paths. High-priority messages incur no additional charge and complete within p95 of 50ms.

Personal Data (Privacy) Ordinance and Hong Kong SMS Consent Rules

Hong Kong's Personal Data (Privacy) Ordinance (PDPO, Cap. 486) regulates the collection, use, and disclosure of personal data, including phone numbers. For SMS marketing (unsolicited promotional messages), you must obtain explicit, documented consent from the recipient before the first send. Consent must be "opt-in": the recipient must actively agree to receive marketing SMS from your organization. General consent to receive communications does not automatically grant permission for SMS marketing.

The Hong Kong Code of Practice for SMS Advertising, published by the industry self-regulatory body, imposes additional restrictions:

• Quiet hours: Marketing SMS must only be sent between 08:00 and 21:00 Hong Kong Time (HKT). No sends outside these hours, regardless of recipient time zone.
• Holiday restrictions: No marketing SMS on Sundays or public holidays, including Lunar New Year, Mid-Autumn Festival, Christmas, and other statutory holidays recognized by the Hong Kong government.
• Frequency limits: No more than one marketing SMS per recipient per day, except where the recipient has explicitly agreed to higher frequency.
• Opt-out right: Every marketing SMS must include a clear, unambiguous opt-out instruction (e.g., "Reply STOP to unsubscribe"). You must honor opt-out requests within one working day.

smsroute.cc's dashboard includes a "quiet hours" scheduler that automatically defers marketing sends to 08:00 HKT if you schedule a message outside permitted hours. For transactional SMS (password resets, OTP codes, delivery notifications), these restrictions do not apply—transactional SMS are not considered "marketing" under PDPO, though explicit prior consent for transactional messages is still recommended.

The Office of the Communications Authority (OFCA, https://www.ofca.gov.hk/) enforces PDPO compliance for telecom carriers and has published enforcement actions against bulk SMS senders who violate consent or quiet-hour rules. Penalties include cease-and-desist orders and carrier-level blocking of repeat offenders. smsroute.cc requires that you certify consent compliance at account signup; we reserve the right to suspend accounts that violate PDPO or the SMS Advertising Code.

Frequently Asked Questions

Related

import os, requests

resp = requests.post(
    "https://api.smsroute.cc/v1/sms/send",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+8525551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.json())

curl -X POST https://api.smsroute.cc/v1/sms/send \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+8525551234567",
    "from": "smsroute",
    "text": "Your verification code is 384921"
  }'

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/sms/send", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+8525551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+8525551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/v1/sms/send",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+8525551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/v1/sms/send');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);