> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run an autonomous campaign

> Set a goal, a cap on calls per person, a gap, the caller identity and your guardrails, then let the AI plan and adapt each call itself.

In an autonomous campaign the AI plans and adapts each call itself from the goal you set, learning from every conversation. The console calls it "the closest thing to a real, tireless attacker, run against your own team, safely and with consent." There is no fixed script. You set the objective and the limits.

> [!NOTE]
>
> The attacker is always a consented simulation. It stops the moment someone refuses. Your own guardrails are added on top of the built-in safety rules, never instead of them.

## Before you start

* An attacker with a voice. See [Create an attacker](https://docs.deepblocker.ai/vishing/attackers.md).
* The people to call, with consent recorded. See [Add the people you will call](https://docs.deepblocker.ai/vishing/people.md).
* A clear objective in one or two sentences.
* Optionally, a research profile on the person. A profile's suggested attack opens this page pre-filled. See [Research a person before a call](https://docs.deepblocker.ai/vishing/research.md).

## Steps

**1. Choose Autonomous**

Open **Red Team**, **Campaigns**, **New Campaign**. Under **Step 1 · Choose how to run it**, pick **Autonomous (AI-driven)**. The options appear below the cards.

**2. Set the objective and the limits**

| Field | What to enter | Limits and defaults |
| - | - | - |
| **Engagement objective** | What the attacker is trying to achieve across the calls, for example "Get an employee to read back a one-time verification code to complete an IT migration." | Required. Launch is refused without it |
| **Max calls per person** | A hard cap. The engagement always stops here | 1 to 10. Default 4 |
| **Gap between calls (minutes)** | How long to wait before the next call to the same person | Default 60 |

**3. Choose the caller identity**

Under **Caller identity across calls**, pick one.

| Option | What it means |
| - | - |
| **Same caller** (recommended) | One person keeps the same name, company and voice, and builds on every previous call. Learns from what already failed. |
| **Rotating callers** | A different person each call, with a fresh name and company. The voice also changes each call, unless you picked a specific voice in the voice step, which is then used on every call. Reuses facts, not the identity. |

**4. Add guardrails**

Under **Extra guardrails**, write one rule per line, for example "Never mention a specific real system by name." or "Do not reference the CEO by name." They are optional.

**5. Pick a purple-team target, or leave it off**

**Purple-team target** is optional. Leave it on the first option, **Off**, to call your people as normal. Or pick one of your own DeepBlocker-protected lines. The attacker then dials that line instead of contacts, to grade whether live detection catches the cloned voice. The campaign page then shows the detection rate, the time to detect, and whether the transfer gate held.

**6. Finish the wizard**

Pick the attacker, the people, the number and the timing, then record the authorisation. See [Build a campaign](https://docs.deepblocker.ai/vishing/campaigns/create.md) and [Authorise and launch](https://docs.deepblocker.ai/vishing/campaigns/authorise.md).

## What happens next

The attacker writes its own opening and adapts after each call, within the cap and the gap you set. What it learns on one call briefs the next. No person is called more times than the cap. Read the calls one by one in [One call in detail](https://docs.deepblocker.ai/vishing/results/call-detail.md).

## Problems

> [accordion] It says Set an engagement objective for the autonomous attacker before launching
>
> The objective is empty. Write one or two sentences under **Engagement objective** and launch again.

> [accordion] The voice changed between calls
>
> **Rotating callers** changes the voice each call. Pick **Same caller**, or pick a specific voice in the voice step, which then holds on every call.

> [accordion] The Autonomous card is missing
>
> Autonomous campaigns are switched on per deployment. Write to us. See [Support and contact](https://docs.deepblocker.ai/support.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.