Country Summary
| Country name | France |
|---|---|
| ISO code | FR |
| Region | Europe |
| Mobile country code | 208 |
| Dialing code | +33 |
| Major carriers | Orange, Bouygues Telecom, SFR, Free Mobile |
Guidelines
| Two-way SMS supported | Yes |
|---|---|
| Number portability available | Yes |
| Twilio concatenated message support | Yes |
| Message length | Inbound: GSM 3.38=160, Unicode=70 Outbound: GSM 3.38=160, Unicode=70 |
| Twilio MMS support | Converted to SMS with embedded URL |
| Sending SMS to landline numbers | You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged. |
| Compliance considerations | French mobile networks block marketing SMS traffic on Sundays, any nights after 10 PM, and public holidays. If messages are sent during these restricted times, they will be queued and sent out the following day. Bouygues Telecom do not support Unicode body encoding for application-to-person (A2P) SMS. All Unicode characters will be replaced with GSM characters to ensure delivery. Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:
|
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Not Required | Supported | Supported | Not Supported | Supported |
| Twilio supported | --- |
Supported
Learn more | Supported | Supported | Not Supported |
| Sender ID preserved | --- | Yes | Yes | No | --- |
| Provisioning time | N/A | N/A | N/A | N/A | N/A |
| UCS-2 support | N/A | Supported | Supported | Supported | N/A |
| Use case restrictions | N/A | Bouygues Telecom do not support unicode and will be replaced with GSM characters to ensure delivery | French domestic longcodes can only be used for Person-To-Person (P2P) messages. The use of French domestic longcode for Application-To-Person (A2P) messages would result in delivery failure | French mobile operators do not support message delivery via international Numeric Sender ID. These are overwritten into a random shortcode outside Twilio's platform. | N/A |
| Best practices | N/A | You must use alphanumeric sender ID to send Application-To-Person (A2P) messages | N/A | You must use alphanumeric sender ID to send Application-To-Person (A2P) messages | N/A |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Not Required |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | N/A |
| UCS-2 support | N/A |
| Use case restrictions | N/A |
| Best practices | N/A |
| Alphanumeric - Dynamic | |
|---|---|
| Operator network capability | Supported |
| Twilio supported |
Supported
Learn more |
| Sender ID preserved | Yes |
| Provisioning time | N/A |
| UCS-2 support | Supported |
| Use case restrictions | Bouygues Telecom do not support unicode and will be replaced with GSM characters to ensure delivery |
| Best practices | You must use alphanumeric sender ID to send Application-To-Person (A2P) messages |
| Long Code - Domestic | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | N/A |
| UCS-2 support | Supported |
| Use case restrictions | French domestic longcodes can only be used for Person-To-Person (P2P) messages. The use of French domestic longcode for Application-To-Person (A2P) messages would result in delivery failure |
| Best practices | N/A |
| Long Code - International | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | No |
| Provisioning time | N/A |
| UCS-2 support | Supported |
| Use case restrictions | French mobile operators do not support message delivery via international Numeric Sender ID. These are overwritten into a random shortcode outside Twilio's platform. |
| Best practices | You must use alphanumeric sender ID to send Application-To-Person (A2P) messages |
| Short Code | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | N/A |
| UCS-2 support | N/A |
| Use case restrictions | N/A |
| Best practices | N/A |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.