Quick answer: Marketing SMS to French recipients runs into a hard time gate before it runs into a sender-ID gate. French law bars promotional texts between 20:00 and 08:00, on Sundays, and on public holidays, and the CNIL enforces that window alongside GDPR-grade consent. The country accepts alphanumeric sender IDs and registration is only recommended, not required, but unregistered alphanumeric traffic is progressively filtered by French operators. A French program therefore registers its sender for stability, collects prior opt-in, respects the statutory quiet-hours window, and carries the STOP au 36111 opt-out wording. This post walks the consent layer, the time gate, sender-ID economics, the opt-out rule, and the FR row of Orbit's send gate.
Everything below is a tenant-owned onboarding playbook, not legal advice and not a delivery guarantee. Orbit carries the controls — consent records, quiet hours, opt-out handling, sender-ID registration — and the French posture on each is yours to set; the final reading of the French Consumer Code, the e-privacy framework, and GDPR sits with you and your counsel.
The consent layer: GDPR plus the French marketing-code rules
France transposes the GDPR through the Loi Informatique et Libertés and layers the e-privacy rules in the Code des postes et des communications électroniques. For marketing SMS, the practical standard is the same as elsewhere in the EU: prior, explicit, informed, and revocable consent, with the sender carrying the record. French consumer-protection and data-protection reviews treat a missing consent record as a program defect, not a platform defect.
The consent record a French program keeps mirrors the German and UK posture: who consented, when, through which wording, to which use case, and how they can revoke. Orbit stores that record per tenant through the consent management docs surface; the legal sufficiency of the wording and collection flow is yours to review with counsel. The sibling GDPR posture guide walks the lawful-basis, erasure, and data-residency surface that underlies the French lane.
The statutory quiet-hours window: 20:00–08:00, Sundays, and public holidays
The rule that most often surprises first-time French senders is the time window. Promotional SMS may not be sent:
- between 20:00 and 08:00 local time,
- on Sundays,
- on public holidays.
This is a statutory constraint, not a carrier convention, and it sits above the softer "harassment" standards applied in markets like Germany. The window is enforced by the Direction générale de la concurrence, de la consommation et de la répression des fraudes (DGCCRF) and is a routine check in CNIL-related reviews. Transactional messages — appointment reminders, delivery notifications, two-factor codes — generally fall outside the marketing rule, but the classification is fact-specific and the record should match it.
Orbit's quiet-hours control is tenant-configured: you set the window and the days the gate respects. For France the convention is not the platform default; it is the statutory window above. The quiet hours docs show the per-tenant surface where the window is set.
CNIL enforcement: what a French review actually looks like
The Commission nationale de l'informatique et des libertés (CNIL) is the data-protection authority that French SMS programs most often encounter. Its enforcement posture on SMS turns on three questions:
- Was the data collected lawfully? Consent must be freely given, specific, informed, and unambiguous; pre-ticked boxes and bundled consents do not survive scrutiny.
- Was the message itself lawful? Marketing traffic needs a consent basis; service traffic needs a basis tied to the contract or service step.
- Are retention and erasure respected? The consent record, the send log, and any profiling data must respect data-minimization and storage-limitation obligations.
CNIL fines are public and indexed to turnover, which makes the consent record and the opt-out audit trail the operational defenses. Orbit's audit logging and per-tenant consent ledger supply the evidence surface; the legal posture is tenant-owned.
The French sender-ID reality: recommended registration and operator filtering
On paper, France is generous. Alphanumeric sender IDs are accepted, long codes are accepted, and the FR registration row is recommended, not required. A dynamic alphanumeric sender can go on day one without waiting for an approval.
The wire reality is the same pattern as Germany and the UK: French operators filter dynamic alphanumeric senders they cannot attribute to a registered brand. Unregistered traffic tends to see sender replacement, relabeling, or reduced deliverability over time. So the operational rule is: register the sender ID for any sustained program, even though the gate does not hold the traffic.
Two practical notes:
- Alphanumeric is one-way. A branded alphanumeric sender cannot receive replies. Two-way traffic, including opt-out handling, needs a numeric long code.
- Short codes are scarce. France uses short codes for high-volume use cases, but they carry registration lead time and cost; most A2P programs start with alphanumeric for display and long codes for replies.
The registration flow is the same POST /api/v1/compliance/sender-id-registrations endpoint used in every market; the France-specific documents and rules are returned by the country-rules reference for FR on the sms channel.
The opt-out rule: STOP au 36111
French A2P SMS is expected to carry an opt-out path, and the convention is the STOP keyword routed to the short code 36111. The wording most often seen is `STOP au 36111` — concise, in French, and recognizable to recipients. The exact opt-out keyword alias is tenant-configured in the alias table; the opt-out keyword alias table docs show where to extend it for French traffic.
An opt-out must be honored across channels where the identity can be safely linked, and the consent ledger must reflect the revocation before the next marketing send. Transactional sends that are not marketing are outside the opt-out scope, but the classification of each message must be defensible.
The Orbit send gate for FR: registration recommended, quiet hours enforced
Orbit's send-time gate reads one field per country and channel: registration. The FR row for SMS is documented as recommended — below Singapore's required and on par with Germany and the UK. A send to a French destination is not held for lack of a registration, but the gate does enforce the tenant-configured quiet-hours window when the destination is France.
That split matters: the registration row is soft, but the time window is hard. The per-country row, with sender_types, two_way, content_restrictions, and stop_requirement, is published on the country requirements page; the gate behavior is described on the send gates page.
Two honest readings of the FR row. First, recommended is a gate posture, not a deliverability promise: register the sender to keep long-running traffic stable. Second, the gate enforces the controls you configure; it does not guarantee that your message content, consent basis, and opt-out wording satisfy French consumer-protection or data-protection law. The compliance posture is tenant-owned.
Launch checklist for a French program
The country-by-country launch loop lives in the sender-ID registration country playbook; the France lane adds these rows to its five steps:
- Read the FR row live. Call the country-rules reference for
FRon thesmschannel and readregistration,sender_types,content_restrictions, andstop_requirement. - Pick the sender for the job. Alphanumeric for one-way brand display; long code for anything that needs replies.
- Register for stability. Submit the alphanumeric sender through the sender-ID registration flow before the program scales, even though the gate does not require it.
- Set the statutory quiet-hours window. Configure 20:00–08:00, Sundays, and public holidays in the tenant quiet-hours control.
- Collect and record prior opt-in. Keep a controller-held consent record with the collection wording, timestamp, and use case.
- Add the French opt-out. Put
STOP au 36111in the tenant alias table and in marketing message templates.
Run those against the live country-rules reference, and the French program becomes a checklist instead of a statute reading.
Frequently asked questions
Do I need prior consent to send marketing SMS to France?
Yes. Marketing SMS to French recipients requires prior, explicit, informed, and revocable consent under GDPR and French e-privacy rules. The consent record is the operational defense in a CNIL or DGCCRF review.
What are the quiet hours for SMS in France?
Promotional SMS may not be sent between 20:00 and 08:00 local time, on Sundays, or on public holidays. Transactional messages generally fall outside the rule, but the classification must be defensible.
Is sender-ID registration required for France?
The FR gate row is recommended, not required. You can send a dynamic alphanumeric sender on day one, but French operator filtering makes registration the stable choice for any sustained program.
What opt-out wording should French SMS carry?
The convention is STOP au 36111. Configure the keyword alias in the tenant opt-out alias table and include the wording in marketing templates.
Does Devotel Orbit guarantee GDPR or French consumer-code compliance?
No. Orbit carries the controls — consent records, quiet hours, opt-out handling, sender-ID registration, and the FR send-gate row — and the compliance posture is tenant-owned. Statutory interpretation stays with you and your counsel.
Published 11 October 2026.