Overview

When engaging customers through SMS messages in France, you are legally required to give end-users the ability to opt out from all promotional messages via a short code. You can choose to use a dedicated short code or a shared short code through a local French partner for your opt-out/STOP messages. Be aware that these processes can differ by aggregator, such as mGage or Infobip.

Timeframe considerations

Before you get started, it's important to note that marketing messages are not allowed in France before 08:00 AM or after 08:00 PM on weekdays, before 10 am or after 6 PM on Saturdays, anytime on Sundays, or national holidays. During these time frames, all promotional message traffic is blocked by either the local vendor or carrier and will fail. If you send messages between these time frames, Acoustic is still charged for this traffic and bills your organization. It is important for you to periodically review the latest SMS regulations in France for their requirements and impact on you and your users.

To avoid sending messages during blocked hours, make sure that you plan to send any large bulk early in the day so all messages are delivered before the French mobile carriers blocked hours. If an SMS send is started too late, it can create a situation where only a portion of the messages is delivered while the balance of outgoing SMS messages fails. Again, you are still charged for failed messages.

How opts-out are managed

It's important to note that because the aggregator enforces opt-outs at the Sender ID level, all messages from that opted out Sender ID are blocked. The aggregator opts out the Sender ID by using the last message that is sent before the opt-out request. Because this contact is added to the suppression list that is maintained by the aggregator, if the contact wants to rejoin your SMS program, then you must provide clear evidence of the contact's request to Acoustic. Acoustic then forwards their request to the SMS partner who will then follow the required processes. If approved, the aggregator removes the requested mobile user from the suppression list.

Using a dedicated short code

With a dedicated code, you must provide details of how to opt-out, such as STOP <your code> in your messages. Dedicated French codes function in every way as normal dedicated codes.

SMS partners (such as mGage and Infobip) do not check for opt-out requests or do any local suppression. This is your responsibility.

Using a shared short code

Shared short code for SMS messages in France works a little differently than in other countries. For a French shared code, you must obtain SMS consent through a web service such as Acoustic Campaign web forms or your own. If you use your own web forms, you then import consent into Acoustic Campaign. You cannot obtain consent by keyword text from a handset.

Shared short codes:

• Opt-in via mobile originated (MO) messages is not supported for shared short codes. Only opt-in by web form is supported.
• Campaign pre-approval is not needed as long as spam does not run through it.
• STOP MO messages to the designated stop short code have an automated confirmation in French provided directly by the local vendor. Customers will not be able to respond to the confirmation.

Note: When a contact submits a STOP MO message, the opt-out is in direct relation to the last MT message received from the last sender ID.

• Include your opt-out text STOP <your code> at the end of each outbound message. If you use a shared short code with one of our SMS Partners, then you must specify the designated shared short code:
• mGage: STOP 36184
• InfoBip: STOP au 36173

For mGage users

The following details apply to mGage users only.

French mobile operators do not notify the SMS Campaign Manager of STOP requests in the same way as other operators. As a result, the STOP requests do not appear in the SMS Campaign Manager Messages area. Instead, the STOP request is forwarded to your mGage, where the mobile number is added to a local suppression table. If you try to send new SMS messages to the same mobile number with the same sender ID, the message will be cross-checked and suppressed.

How sent message move from your campaign to an end-user in France

1. When you create and send an SMS campaign and program, Acoustic Campaign uses API to deliver outgoing SMS messages to the SMS Campaign Manager and to mGage USA. You must use text STOP 36184 at the end of each outbound message.
2. For each outgoing SMS message, mGage checks the designated mobile number to determine if the end user's mobile number is associated with France. mGage does not have direct connections to mobile carriers in France, so it sends outgoing messages to its local French partner. mGage uses its local routing logic to forward the messages to the French partner.
3. The local French aggregator forwards the SMS messages to the carriers’ SMS gateway for delivery.
4. The French mobile carrier then delivers the outgoing SMS to the end-user and generates a Delivery Receipt (DR) and forwards the DR to the local aggregator.
5. The local aggregator then forwards the DR to mGage and the Delivery Receipt acknowledgment (in the form of a Universal Behavior) is added to the Acoustic Campaign database. The SMS Campaign Manager Messages report shows that the Delivery Receipt is received after the message is delivered to the end-user.

When the end-user wants to stop receiving messages and opts out of the program

The end-user creates a new message to the shared short code that is specified in the client’s original message. The end user specifies keyword (STOP) text and requests to unsubscribe from the SMS Campaigns.

The French mobile carrier forwards the end-user opt-out request to the local aggregator. The local aggregator processes the end-user request and sends an auto-reply to the end-user. For example:

M6 Boutique: Nous avons recu votre demande. Vous ne devriez plus recevoir de message de notre part. SMS non surtaxé.

The local aggregator forwards the mobile number to the mGage opt-out list to prevent any future SMS messages from being sent to this mobile number. mGage adds the mobile number and the last sender ID used to send to that number to its Suppression list.

From this point on, if you send an SMS message to the end-user’s mobile number using that same sender ID, mGage suppresses the send.

Updating the SMS Consent Status within the Campaign database

mGage has implemented conditional logic that will trigger an update to the SMS Consent Status within the Campaign database, the moment the client attempts to send to the number again using the same Sender ID. Here is the full flow:

• End-user receives a message from Acoustic Content provider.
• End-user replies STOP to a shared short code provided by a local vendor.
• Local vendor posts the STOP response to mGage, which adds the end-user/sender ID combo to an existing suppression table and prevents future messages from reaching the end-user on the same sender ID.
• Acoustic Content provider attempts another send to the end-user on the same sender ID and finds that the message fails to deliver. At the same time, an error response from mGage (061 Destination Blocked) is returned as a result of the suppression table insert.
• This error response triggers the new consent behavior to automatically update the SMS Consent Status to Opted-out within Acoustic Campaign.

For the time being, clients who wish to update their systems to reflect contacts who have opted out of the text to join program (and are now on the mGage controlled Suppression List) can request from Acoustic the opt-out list mentioned above. You can also use the report to update Acoustic Campaign SMS Consent Status so you do not send any new SMS messages to these users in the future.

For Infobip users

These details apply to Infobip users only.

When using a shared short code, French mobile operators will notify Infobip of opt-out requests; however, Infobip will not pass these to Acoustic Campaign. Instead, Infobip will add this mobile number to its local suppression table. So if you try to send a new SMS message to the same mobile number with the same Sender ID, your new outbound message will be cross-checked and suppressed.

When you create and send a campaign, Acoustic forwards the mobile terminated (MT) message to Infobip. Simultaneously, Infobip stores the information about the original sender and MSISDN to match mobile originated (MO) messages later. A delivery report is then forwarded to Acoustic SMPP.

If an end-user chooses to opt-out of SMS messages, they send the STOP request to Infobip through the shared short code. Infobip adds the phone number to their suppression list. When you send your next campaign to the same phone number, Infobip discards the requests and responds to Acoustic SMPP with an EC 2052 status code delivery receipt (DLR). Acoustic SMPP then looks for this status code from DLR and send the opt-out trigger for that user from the organization/program ID that was used for sending the campaign.

Once the end-user is opted-out, they will be removed from the subsequent campaign in that program from your organization. If you use a different program for a campaign, Acoustic will send an MT message to Infobip for that user number. Infobip will then discard the request and return an EC 2052 DLR for that phone number. Acoustic SMPP again looks for the status code from the DLR and opt-out the user's number from the second program. This process will continue for any new program that is used for the campaign for that user.

Infobip's online reporting portal shows whenever the end-user sends an opt-out request on the shared short code. You do not have to send a second SMS for the SMS consent to be automatically updated. You can use the opt-out data from the reporting portal and manually opt-out the end-users from your Acoustic Campaign database.