Voice phishing simulations in France
France regulates this more directly than anywhere else in Europe, and it reaches a different answer from its neighbours: the argument that a voice phishing simulation is not marketing, which carries most of this portal, does not rescue you here. The decision that shapes a French campaign is which category of number it originates from, and it belongs at the start rather than the end.
Phone numbers
Supplied by Callstrike
Local numbers in France, after a one-time approval.
Running a simulation
Permitted, and the number decides how
Ordinary geographic and mobile numbers are barred as the identity for automated calls.
Consent
The committee, not the individual
The works council must be consulted before you introduce this. It cannot veto it.
Getting a phone number in France
One approval per country, completed in the console.
Provisioned by Callstrike after approval
Your company files its regulatory details once for this country. Local rules require the order to be placed by the provider of record, so Callstrike provisions the number on your behalf once the filing is approved. Approval is a one-time, per-country step and usually takes 3 to 5 business days. We only ask for what the regulator requires.
France is one of the countries where local rules put the order in the provider's hands, so your company files its details once and Callstrike places the order against the approval. Expect the filing to be documentary rather than declaratory: an extract from the commercial register establishes who you are, and a second piece of evidence showing a French address establishes where. A post box is not accepted, and the address has to be genuinely in France.
The harder question is not the filing at all. French numbering rules forbid ordinary territorialised numbers, meaning the geographic and mobile ones a pretext would reach for first, from being presented as the caller identity for calls sent by automated systems, and operators are required to interrupt the routing of calls that break that rule. What permits automated outbound instead is a derogated category. Settle with your account team which category your campaign will run on before you design the scenario, because it constrains what the number can look like to the person answering.
- 01Complete the regulatory clearance formYour administrator, in the Callstrike console. The form asks only for what the regulator requires.
- 02Approval is granted against your workspaceTypically three to five business days, and once only for as long as you operate here.
- 03A dedicated number in France is assigned to youCallstrike
- 04Build and launch the campaignYour team
| What you provide | Accepted evidence, any one of |
|---|---|
| Proof of business identity | Excerpt from the commercial register |
| Proof of business addressMust be within France; a PO Box is not acceptable. | Excerpt from the commercial register showing french address, Utility bill, Tax notice, Rent receipt, Title deed |
These requirements are set by the carrier and can change. The form in the console is generated from their current rules, so treat it as authoritative and this table as a summary of what to have ready. Checked 2026-09-07.
Is it lawful to run a simulation in France?
The position in short, before your counsel reads the detail below.
Yes, and France is the country on this page where that answer needs the most care, because the constraint is a numbering rule rather than a consent rule and it does not care what your purpose is. The cold-calling prohibition everyone reaches for is scoped to direct prospecting and does not reach an internal exercise. The rule that does reach you is the regulator's power to forbid categories of number from being presented as the caller identity for automated calls, and it has used that power.
Then the finding that makes France genuinely different. In June 2024 the highest administrative court held that the legislature did not intend to limit that power to calls sent in the context of telephone cold calling. Pollsters challenging the rule got nothing. So the sentence that works in the United Kingdom, in Germany and in the Netherlands, that your calls are not marketing, does not do the same work here. Two honest qualifications: it is a single-chamber decision and it is not reported in the official collection, so it is authoritative rather than a leading case.
The employee side is a real step and it is not a gate. The works council must be informed and consulted before you introduce means or techniques permitting control of employees' activity, and that duty belongs to the fifty-employee regime even though the committee itself exists from eleven. It issues an opinion, and you report back on what you did and why. Somebody who must give reasons for departing from an opinion is somebody who may depart from it, so budget the consultation as a real cost and not as an approval you might not get.
On recording, France leaves you with a gap rather than a rule, and we would rather name it. The criminal provision punishes capturing or recording words spoken in private without the consent of the person concerned. The data protection authority's page on recording telephone calls is dated 2009 and is labelled obsolete on its own site, and we found no current replacement worth building advice on. The workable French design is therefore to capture what happened rather than the audio, and to take any appetite for recordings to French counsel.
What your company needs to do
6 items, in the order you will need them.
- Choose the category of number before anything elseFrance-specificThis is the French decision and everything else waits on it. Ordinary geographic and mobile numbers cannot carry an automated campaign, the derogated categories can, and the exceptions for very low volumes are switched off entirely for mobile. Ask your account team which category is available to you before you write a scenario around a number that will never be permitted to carry it.
- Do not plan to present a customer's or a client's numberFrance-specificThe regulator has addressed this exact arrangement: a principal lending its number to a call centre for automated calls cannot be allocated a polyvalent or a mobile number for that purpose. Operators must also verify that the caller is the number's assignee or holds its agreement, and drop what cannot be authenticated. Since January 2026 that has been a technical whitelist rather than a policy.
- Consult the works council, and write down what you did with itFrance-specificInform and consult before the technique is introduced, not before the first campaign of the second year. The output is an opinion and your reasoned reply, and the reply is the artefact worth keeping, because it is the evidence that the consultation was real rather than announced.
- Document the basis and the impact assessmentLegitimate interests, with the assessment and an impact assessment behind it. Be aware of the sourcing when you write it: there is no French regulator statement we could hand you saying that employee agreement fails in the context of call-based testing, so the argument rests on the Regulation's own definition and on European-level guidance.
- Capture the outcome rather than the conversationWhether the call was answered, whether a credential was disclosed and where in the script the person disengaged are all recordable as structured data. That design does not have to resolve a criminal provision against a regulator page that says of itself that it is out of date.
- Plan for the AI transparency duty rather than around itThe European duty to tell a person they are dealing with an AI system, and to disclose artificially generated audio, has applied since August 2026 and reaches France directly. The exception on the face of the text is for use authorised by law to detect or prosecute criminal offences, and management's own sign-off is not that. Take the timing question to counsel rather than assuming a covert design answers it.
The controls that do the work
How Callstrike is configured, and which provision in France each choice answers.
Auto-hangup before disclosure
The bot ends the call at the moment an employee starts to give up a credential or a piece of personal data, so the thing the pretext asked for is never spoken into the system and never stored.
In France the works council consultation and the impact assessment are where the programme is actually argued, and both turn on proportionality. The call ends the moment an employee begins to give up a credential, so the exercise measures susceptibility without the credential ever entering the system. That is the strongest single fact to put in front of a committee, because it converts an argument about how carefully sensitive data is handled into a statement that the sensitive data does not exist.
In-call debrief and follow-up
A second voice breaks character as soon as the call ends, explains what just happened and why it worked, and a follow-up email repeats it in writing while the moment is still sharp.
The employment code frames the consultation around means of controlling employees' activity, and the committee's opinion is written by people who will ask what the exercise does to their colleagues. A second voice that breaks character the instant the call ends, and vishing training that follows in writing the same day, is a different proposition from a monitoring technique. It is also the part of the design that survives being described accurately in the reasoned reply.
Consent Management
Two modes: collect consent now, over email, Slack or Teams with a full audit trail per employee; or record that your organisation already has this covered, by uploading the policy, handbook clause or agreement and confirming the scope it applies to. The document is hashed, the attestation is signed and timestamped, and an audit email is issued. Included on every plan.
France's employee instrument is a collective one, so this does not replace the consultation and nothing here pretends it does. What it produces is the individual layer underneath: a dated record of what staff were told about the programme, or the hashed policy and signed scope attestation where your organisation already covers this in its own rules. That is the evidence the impact assessment refers to and cannot itself create.
SCORM module
An interactive web presentation on voice-phishing risk, delivered through your own LMS, which then invites the learner to opt into a web call with the bot. A call the person starts themselves in a browser is not a telephone call, so telephony rules do not reach it.
This is worth more in France than almost anywhere, because the numbering rule is the binding constraint and this route does not touch it. Callstrike's vishing simulator can deliver the same deepfake voice through a web call the learner starts themselves after working through the module, and a call a person opens in their own browser is not a telephone call sent by an automated system, so the caller identity rules that decide everything above have nothing to attach to.
Consent Management is included on every plan. See AI voice phishing simulation and human-in-the-loop voice phishing for how each is delivered.