Country Summary

Country nameFrance
ISO codeFR
RegionEurope
Mobile country code208
Dialing code+33
Major carriersOrange, Bouygues Telecom, SFR, Free Mobile

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message lengthInbound: GSM 3.38=160, Unicode=70 Outbound: GSM 3.38=160, Unicode=70
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou 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:

  1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
  2. Only communicate during an end user's daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
  4. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot RequiredSupportedSupportedNot SupportedSupported
Twilio supported --- Supported
Learn more
SupportedSupportedNot Supported
Sender ID preserved --- YesYesNo---
Provisioning timeN/AN/AN/AN/AN/A
UCS-2 supportN/ASupportedSupportedSupportedN/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 capabilityNot Required
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
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 capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
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 capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
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 capabilitySupported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/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.