Locale Summary
Locale name | France |
---|---|
ISO code | FR |
Region | Europe |
Mobile country code | 208 |
Dialing code | +33 |
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 between 10pm and 8am, on Sundays, and on French public holidays. If messages are sent during these restricted times, they will be queued and sent the following day. Bouygues Telecom does not support Unicode body encoding for application-to-person (A2P) SMS. All Unicode characters will therefore 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 | Supported |
Sender ID preserved | --- | Yes | Yes | No | Yes |
Provisioning time | N/A | N/A | N/A | N/A | 8-10 |
UCS-2 support | N/A | Supported | Supported | Supported | Supported |
Use case restrictions | N/A | Bouygues Telecom does not support Unicode body encoding. All Unicode characters will be replaced with GSM characters to ensure delivery. Messages submitted to the NRJ Mobile and Truephone networks will be overwritten with random shortcodes outside the Twilio platform. | French domestic Long Codes can only be used for person-to-person (P2P) messages. Using it for any high volume messaging, or even for application-to-person (A2P) messages, will result in delivery failure and the domestic Long Code being blocked. | French mobile operators do not support message delivery via international Numeric Sender ID. Submission by International Long Codes will be attempted on a best-effort basis. The Long Code will be overwritten with a generic Alphanumeric Sender ID or Short Code outside the Twilio platform. | Refer to our FAQs for short code best practices. |
Best practices | N/A | You must use Alphanumeric Sender IDs to send A2P messages. | N/A | You must use Alphanumeric Sender IDs to send A2P messages. | Refer to our FAQs for short code best practices. |
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 does not support Unicode body encoding. All Unicode characters will be replaced with GSM characters to ensure delivery. Messages submitted to the NRJ Mobile and Truephone networks will be overwritten with random shortcodes outside the Twilio platform. |
Best practices | You must use Alphanumeric Sender IDs to send 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 Long Codes can only be used for person-to-person (P2P) messages. Using it for any high volume messaging, or even for application-to-person (A2P) messages, will result in delivery failure and the domestic Long Code being blocked. |
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. Submission by International Long Codes will be attempted on a best-effort basis. The Long Code will be overwritten with a generic Alphanumeric Sender ID or Short Code outside the Twilio platform. |
Best practices | You must use Alphanumeric Sender IDs to send A2P messages. |
Short Code | |
---|---|
Operator network capability | Supported |
Twilio supported | Supported |
Sender ID preserved | Yes |
Provisioning time | 8-10 |
UCS-2 support | Supported |
Use case restrictions | Refer to our FAQs for short code best practices. |
Best practices | Refer to our FAQs for short code best practices. |
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.