Locale Summary |
|
---|---|
Locale name |
France |
ISO code |
FR |
Region |
Europe |
Dialing code |
+33 |
Guidelines |
|
---|---|
Use Cases |
Short codes are ideal for high-throughput programmatic messaging. Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes you may be a good candidate for short codes. Some of the most common use-cases for short codes in France are:
|
Restrictions |
Short codes can only message users on carriers within the countries in which they are provisioned. If your customers do not have French phone numbers on carrier networks that have approved that short code, you should not obtain a France short code. If you have customers in other countries, Twilio may be able to provision short codes in those countries. Short codes require express consent from end users before any SMS can be sent; if you cannot obtain consent you should not use a short code. Twilio and/or the carriers will not support certain types of campaigns, including but not limited to:
FTEU (Free to End User) Short Codes are not supported for this country. Minimum term commit for the Short Code is 3 months. If the Short Code does not have any traffic in France for 30 days or more, there is a high chance for it to be withdrawn due to absence of usage. Refer to this article for detailed explanation on France Short Code Best Practices. |
Other Options |
You can choose your France Short Code Throughput from the following MPS selection: |
Requirements |
To apply for France Short Code the following details are needed:
|
Timeframe |
Please expect delays on any applications submitted in August or December, as the carriers often experience an annual provisioning freeze period during these times. |
Regulatory Bodies |
|
Pricing |
Please refer to the following article: How much does a Short Code cost? |
Next Steps |
To apply for French Short Code please follow these steps:
|
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.