# SMS to France

Policy reference updated 2026-07-13T12:47:12.064706Z. Confirm current requirements, sender eligibility and your use case before launch.

[Contact sales](/demo?product=sms&source_page=%2Fsms-api%2Ffeatures%2Fdestinations%2Ffrance)

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

### Sender types

| Sender | Direction | Throughput (msg/s) | Registration | Sender ID | Timeline |
| --- | --- | --- | --- | --- | --- |
| Short code | two-way | — | none | preserved | — |
| Alphanumeric Sender ID | one-way | — | required (alpha) | preserved | — |

### Rules

- Consent model: opt-in
- Template pre-approval: no
- Quiet hours: recorded; the sending window is not stated
- Sender IDs: one segment per sender ID, marketing or transactional

#### Market Segments
This market operates with two distinct segments:
- **Marketing messages**
- **Transactional messages**

**Important:** Each sender ID can only be used for one segment type. If your company sends both marketing and transactional content, you'll need to register separate sender IDs for each.

#### Marketing Messages
- **Opt-out requirement:** All marketing messages must include an opt-out option
- **Compliance:** Without an opt-out, your messages may be:
  - Redirected to a Short code
  - Not delivered at all

#### Transactional Messages  
- **No opt-out required:** Transactional messages will be delivered with your registered sender ID
- **Usage policy:** Misusing the transactional segment (sending marketing content) will result in losing access to transactional messaging

#### What this market refuses

Any Spam, Adult content, Gambling/Casino Phishing, etc. messages case identified by MNOs in French and French Territories will incur in a penalty of €5,000 (five thousand euros) per operator that will be sent to the client, and the Local Police is involved in such cases. 
Some senders for this market are protected by the French Operators, and an Authorisation letter could be required for those.

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

## The rest of the SMS platform

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

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



## Related resources

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

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