Since August 11, 2026, commercial phone marketing is banned by default in France unless a company can clearly document that a legal exception applies. For sales teams, the question is no longer just "do we have the number?" but "can we prove, record by record, why this call was allowed?"
Official guidance now follows a simple logic: when a call relies on consent, the professional must be able to prove that consent was collected freely, with proper information, and through a clear affirmative action. That is the operational shift for call centers, CRM teams, and compliance owners.
What really changed after August 11, 2026
France moved from an opposition model to a prior-authorization model. Before that date, part of compliance centered on Bloctel. Now a commercial call is, in principle, prohibited if you cannot link the number to an applicable legal basis.
In practice, companies can still call in two broad situations:
- the call relates to an existing contract and stays connected to that contract's purpose;
- the company collected the consumer's prior consent for commercial phone prospecting.
The official Service Public summary of the rules in force since August 11, 2026 also confirms that Bloctel ended with this shift. If your teams still think compliance starts and ends with Bloctel suppression, your control set is already incomplete.
The required proof is not a slogan, it is a documentary chain
Official sources do not impose one single capture format, but they do require professionals to demonstrate that consent existed under the legal conditions. In other words, a vague CRM note such as "opt-in collected" is not enough on its own.
In practice, defensible proof should let you reconstruct at least the following:
- which professional asked for consent;
- which products or services were covered;
- which collection channel was used;
- the collection date and ideally a timestamp;
- the affirmative action that showed agreement;
- the validity period presented to the consumer;
- how withdrawal of consent is handled.
On that point, the official page "Abusive phone marketing, voice spam, or SMS spam: what can you do?" is explicit: the professional must be able to prove consent, the request must be clear and understandable, and the validity period cannot exceed one year.
What you should actually retain
If you want to move from declarative compliance to verifiable compliance, keep an evidence file that is usable per dialed number or per consent event. That may include:
- the screenshot or archived version of the form or collection screen used when consent was given;
- the exact wording shown to the user;
- the technical log associated with the validation action;
- the campaign, landing-page, or store identifier;
- the lead source when the record came from a partner;
- the start and end dates of the validity period used operationally;
- the withdrawal trace when the consumer changes their mind.
This extends the evidence mindset already needed in disputes or fraud incidents, as explained in our article on proof to retain after a fraudulent call. The difference here is that the proof must exist before a complaint or audit, not be rebuilt afterward.
The mistakes that expose teams the most
- Confusing possession of a number with permission to call. A number obtained through a quote, a purchase, or an old lead is not automatic authorization for commercial calling.
- Keeping only a binary status. A CRM field such as consent = yes without wording, date, source, or scope is too weak.
- Failing to bound validity. Official guidance states that consent cannot last more than one year and cannot renew tacitly.
- Ignoring withdrawal. If a consumer withdraws consent, the operational stop must be fast and traceable.
- Relying on a partner without auditing it. If a lead provider collects consent on your behalf, weak evidence on their side becomes your risk.
Before restarting a campaign, a strong practice is to run your list through a 12-point phone trust audit to review both reachability and the robustness of your evidence chain.
How to handle exceptions without stretching them
Many teams will try to rely on the existing-contract exception. That can be legitimate, but only if the call remains connected to the contract's purpose. Using that exception to revive an old list or push an unrelated offer is high risk.
You also need to separate consent rules from execution rules. Even when a call is allowed, calling windows still apply. Teams that want to industrialize this control should encode the rules in scripts, dialers, and internal knowledge bases, then point agents to a centralized FAQ for edge cases.
Operational checklist before dialing
- Confirm that the number is tied either to a relevant existing contract or to explicit consent.
- Retrieve the exact wording used to collect agreement.
- Check the collection date and the announced validity period.
- Confirm that the product or service being promoted matches the accepted scope.
- Verify that consent has not been withdrawn since then.
- Keep a simple export ready to produce in the event of a complaint or audit.
If a consumer perceives abusive solicitation, reporting can also go through SignalConso. That is the practical reminder: your consent evidence chain is not theoretical paperwork, it is a concrete defensive asset.
