Registering a # Sender ID in Hong Kong — a practical guide to the OFCA scheme

If you have received an SMS from a Hong Kong bank or securities firm, you will have noticed the sender name starts with a # — #BankA, for instance. That is not a typographic flourish. It is the marker of the SMS sender-registration scheme run by the Office of the Communications Authority (OFCA): only registered organisations have messages presented that way.

For a business the implication is direct: the recipient can tell at a glance whether the message really came from you. In an environment thick with SMS scams, that is the cheapest trust signal available.

This post walks through the process, including the parts that usually stall.

First, three things people conflate

Concept	What it is	Who decides
Alphanumeric Sender ID	An alphanumeric sender name, e.g. XLEAD	Per-region carrier rules
# Sender ID	The verified sender name under Hong Kong’s registration scheme, e.g. #XLEAD	OFCA registration
Do-not-call Register	The register on which recipients opt out of commercial messages	The Communications Authority

They are independent. You can send with an alphanumeric sender name and no #, you just do not get the verification marker. And whichever sender name you use, the Do-not-call obligations apply either way.

Step 1: Confirm the name meets the naming rules

This is where most applications get bounced. In practice:

• The name must have a genuine connection to your registered entity or brand. Picking a catchy English word usually does not pass.
• Avoid misleading generic words. Terms like Bank, Alert, Verify or Security — words that could be mistaken for a system notice — carry high risk.
• Length is capped. Alphanumeric sender names are typically 3–11 characters, and the # counts toward what is displayed, so leave room.
• Decide whether one name covers everything. If you run several brands, registering each separately is clearer, but that means another set of documents and another review.

When we help clients we usually prepare two or three candidate names before filing, so a rejection on the first choice does not restart the whole process.

Step 2: Assemble the corporate documents

Broadly you need proof of company registration, business registration, and evidence that you are entitled to use the name — a trade mark registration or proof of brand use, for instance. If the requested name does not exactly match the registered company name, that evidence gets particular scrutiny.

Practical advice: filing complete beats filing fast. A request for further documents sends the review back into the queue, and that round trip can cost weeks.

Step 3: Set up a compliant secure network

The scheme requires the sender to operate a secure network environment that meets its requirements. This is the step most businesses have not encountered before — it is not “apply for an account”, it is demonstrating that the path the messages travel is controlled and auditable.

It is also why most companies apply through a provider that already operates such an environment rather than building one. You bring the brand and the paperwork; the provider brings the technical environment.

Step 4: File, track, go live

After filing it is a matter of review. Once approved, the sender name has to be attached to your sending account before messages carry the verification marker.

Worth knowing: a sender name not registered on your account gets the send request rejected outright. On our API that returns an IS status code — invalid sender, or a Sender ID not registered to your account. The full code table is in the SMS API integration guide.

Questions that come up

How long does it take? It depends on how complete the documents are and the review queue. Applications where the paperwork was complete first time and the name passed first time are noticeably faster. Our approach is to eliminate the predictable rejection causes before filing.

Do I need one for Taiwan or mainland China? No. The schemes differ by region — when sending to Taiwan, for example, our API does not take a sender field at all. Build the payload per destination rather than hard-coding one shape.

Does a # Sender ID exempt me from the Do-not-call Register? No. The two are entirely separate. A verified sender name answers “who is this”; the register answers “does this number want to hear from you”. Commercial messages have to satisfy both — see our UEMO compliance checklist.

In short

The # itself has no magic in it. What it signals is that a company was willing to put its identity on record. For securities firms, banks, insurers and any brand that depends on being trusted, that cost is worth paying.

The time sink is not the form. It is choosing the wrong name, submitting incomplete documents, and not having the secure network in place. Handle those three up front and the rest moves.

If you want help, get in touch — we have filed a fair number of these and know where they stick.