# 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 South Korea

- Country code: KR (dialing +82)
- Channels available: sms, whatsapp, voice
- Two-way messaging: yes

### Sender types

| Sender | Direction | Throughput (msg/s) | Registration | Timeline |
| --- | --- | --- | --- | --- |
| Alphanumeric Sender ID | one-way | — | not required | — |
| Long code (phone number) | two-way | — | not required | — |

### Rules

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

#### International Sender Prefix
`[국외발신]` or `[국제발신]` will be automatically appended to SMS on the operator's end. These phrases mean "Overseas Sending" or "International Sending" respectively. These words are **not** counted in the message length.

#### Character Limits
One SMS segment can contain up to **140 bytes** only, which is equivalent to:
- **140 characters** using GSM-7 encoding
- **70 characters** using UCS-2 16-bit encoding

#### Concatenated SMS (LMS)
Concatenated SMS is known as **LMS** in South Korea. By default, it is **not supported**. Messages may be:
- Trimmed
- Delivered with different parts
- Split into parts that are not received in the correct sequential order



## Related resources

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

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