> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/advanced/vishing-campaigns.md).

# Vishing: campaigns

Call an employee with an AI voice agent that plays a realistic scam scenario, then send them a follow-up email asking for their credentials. Track what they do at each step.

## **Prerequisites**

* Human Security Advanced is active for your company.
* The employees you want to call have a phone number on their profile, in international format: starting with `+` and the country code (e.g. `+33 6 12 34 56 78`). With a [manual import](https://docs.stoik.io/human-security/phishing/manual-import.md), fill in the `phone` column of the CSV file.

## Create the campaign

{% stepper %}
{% step %}

### Start a new simulation

Go to `Simulation`, click `Create simulation` and choose `Vishing simulation`.
{% endstep %}

{% step %}

### Set up the campaign

Give your campaign a clear name to identify it later and choose when the calls start

* **Start date**: tomorrow by default. You can change it.
* **Email delivery distribution**: `Immediately`, within 24 hours, 7 days, 15 days or 30 days. Each employee receives one email, at a different time within the period.
  {% endstep %}

{% step %}

### Choose the scenarios

Pick one or more templates. Each template defines the call scenario and the email sent after it. On each template:

* `Test call` places a call to the phone number on your own profile, and shows the live transcript. You need a phone number on your profile to use it.
* `Preview email` shows the email sent after the call.
  {% endstep %}

{% step %}

### Start the campaign

Click `Start campaign`. The button is available once at least one employee and one template are selected. You can then `Pause` and `Resume` the campaign. It can’t be edited while it is active, so pause it first to make changes.
{% endstep %}
{% endstepper %}

## **After starting**

* Calls are placed automatically by the voice agent.
* After the call, the employee receives a follow-up email that asks them to submit their credentials. If they do, they are recorded as compromised.

## Results

**Results**

Open the simulation to follow its progress:

* **Pending**: the employee has not been called yet
* **Called**: the call was placed
* **Answered**: the employee picked up
* **Not answered**: the phone rang without a pickup
* **Voicemail**: the call reached the voicemail
* **Failed**: the call could not be completed
* **Compromised**: the employee submitted their credentials from the follow-up email

Employees without a phone number are not called.

Click an employee to read the call transcript, see the information they disclosed, and follow a timeline of every event and when it happened.

## What the employee sees

As soon as the employee submits their credentials, they are redirected to their [Employee app](https://docs.stoik.io/human-security/training/employee-app), on a debrief page. It tells them this was a simulation and shows the email that got them, so they can see the clues they missed. A lesson then covers how to recognize voice phishing and the reflexes to adopt, such as never sharing credentials by phone or email and calling the person back on a number you already know.

If the employee hasn’t completed the related training, they also receive a reminder email with a link to it.

## Data protection

### Roles

Your company is the data controller. Stoïk acts as data processor, or as sub-processor when you use Stoïk through an MSP.

### Data processed

* First name, last name and work phone number of the enrolled employees.
* The recording of the call, its transcript and the results of the automated analysis: call answered, conversation started, agreement given, email opened, link clicked.
* The fact that credentials were entered, never the credentials themselves.

### Purpose and limits

* Raising awareness and training employees against phone attacks.
* Results and indicators must not be used to sanction, assess or reward employees. No automated decision with legal effects is made (article 22 of the GDPR).

### Sub-processors and transfers outside the EU

* ElevenLabs (voice agent, recording, analysis) and Twilio (call routing, audio processed live with no retention), both in the United States.
* Transfer safeguards: Data Privacy Framework and standard contractual clauses for ElevenLabs, binding corporate rules (BCR) and standard contractual clauses for Twilio.

### Retention

Recordings, transcripts and analyses are kept for 6 months maximum from the date of the call.

### Before you launch a campaign

* Inform your employees beforehand (articles 13 and 14 of the GDPR), including that simulation calls may be recorded and analyzed.
* France: inform and consult the CSE (article L. 2312-38 of the Labor Code).
* Germany: involve the Betriebsrat (§ 87 Abs. 1 Nr. 6 BetrVG) and collect employees' consent to the recording (§ 201 StGB).

### Security

Individual results are only accessible to the administrators designated by your company.

### Right to erasure

Employees can ask you, as data controller, to erase their personal data. Stoïk assists you as data processor.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/human-security/advanced/vishing-campaigns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
