# Create a workspace, register a sender, and send your first message from the same API you will scale on.

[How sender-ID registration works →](/products/sms/compliance/sender-id-registration)

## The rest of the SMS platform

One API, one set of keys. Explore the other capabilities.

- [Sender-ID registration](/products/sms/compliance/sender-id-registration): Pre-register alphanumeric and dedicated senders where countries require it.
- [Routing](/products/sms/routing): 190+ countries, 240 direct-to-carrier links, and automatic failover.
- [Numbers](/products/sms/numbers): Long codes, short codes, toll-free, and alphanumeric sender IDs.
- [Sending](/products/sms/sending): The send API: segments, Unicode safety, batch, and idempotency.
- [Two-way](/products/sms/two-way): Inbound SMS and conversational replies as HMAC-signed webhooks.
- [All destinations](/products/sms/destinations): Coverage, sender types, and rules for every country Bird reaches.

[Get started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fdestinations)

[Explore the SMS platform](/products/sms)

## Sending SMS to China

- Country code: CN (dialing +86)
- Channels available: sms, whatsapp, voice
- Two-way messaging: no

### Sender types

| Sender | Direction | Throughput (msg/s) | Registration | Timeline |
| --- | --- | --- | --- | --- |
| Alphanumeric Sender ID | one-way | — | required (alpha) | 14 |

### Rules

- Template pre-approval: yes
- Quiet hours: enforced

Custom alphanumeric Sender IDs are not supported in this country. Senders will automatically be replaced with a random numeric code starting with **106**.

- All message content must include a registered **【Signature】** at the beginning of the message. Messages without a registered signature will fail to deliver.
   - Pure English signatures are not supported.
   - Only companies with a local business license can register a signature.

- All templates must be whitelisted before sending, particularly those containing contact information or URLs.
   - Each template may contain a maximum of 2 fixed contact details and 1 URL.
   - Contact information and URLs cannot be included in OTP messages.
   - Top-level and second-level domains must be fixed values (not variables) and must match the registered signature.



## Related resources

- [SMS overview](/docs/guides/sms/overview) (docs)
- [SMS destinations](/products/sms/destinations) (product)

[Get an implementation brief](/learn/workspace?topic=sms-destinations)