> ## 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. # Build a campaign > Walk through the four wizard steps for a standard single call, from choosing who calls to pressing Launch. A campaign is one simulated call to each person you choose. You pick the attacker, the people, the number and the timing, then record who authorised the test. This page walks the standard single call. The [help desk test](https://docs.deepblocker.ai/vishing/campaigns/help-desk.md) uses the same wizard with one step swapped. > [!NOTE] > > You need the Member role or above, at least one attacker, at least one person with consent recorded, and written authorisation to test these people. See [Before you test anyone](https://docs.deepblocker.ai/before-you-start.md). ## Before you start * An attacker with a voice. See [Create an attacker](https://docs.deepblocker.ai/vishing/attackers.md) and [Add a voice](https://docs.deepblocker.ai/vishing/voices.md). * The people you will call, with their consent fields filled in. See [Add the people you will call](https://docs.deepblocker.ai/vishing/people.md). * The name, email and reference of the person who authorised this test. * Minutes left on your licence. See [How minutes work](https://docs.deepblocker.ai/vishing/minutes.md). ## Steps **1. Choose how to run it** In the console, open **Red Team**, then **Campaigns**, then **New Campaign**. Under **Step 1 ยท Choose how to run it**, pick **Single call**. Leave **Single call type:** on **Standard script**. The other cards are covered in [Six ways to run a campaign](https://docs.deepblocker.ai/vishing/campaign-types.md). Under **Pick the campaign template**, choose a scenario card. The card brings the full script and the opening line. Click **Read "..." in full** to read the script before you commit. See [The scenario library](https://docs.deepblocker.ai/vishing/scenarios.md). **2. Who calls** The wizard opens below with four steps across the top: **Who calls**, **Who is called**, **From where and when**, **Authorise and launch**. Under **The attacker**, click one attacker card. Each card shows the name, role and voice. **+ New attacker** opens the attacker form if you have none. Once an attacker is picked, more blocks appear. All of them are optional: | Block | What it sets | Default | | - | - | - | | **Attack level** | How hard the test is: **Clean clone**, **Background noise** or **Researched pretext** | Follows your other choices | | **Tactics** | How the caller leans on the person. Pick one or two of six | **Helpfulness** plus **Urgency** | | **Research used on this call** | Whether the caller uses research on itself and on the person | Both on | | **Teach the employee at the end of a failed call** | Coaching when someone fails. See [Coaching](https://docs.deepblocker.ai/vishing/results/coaching.md) | Off | | **Before the call** | A warm-up notice by **Text**, **Email** or **Text and email**. See [Messages your staff receive](https://docs.deepblocker.ai/vishing/staff-messages.md) | **No warm-up** | | **The script this campaign follows** | **Opening line** and **Script**, prefilled from the template | From the template | Click **Next**. It stays grey until an attacker and a script are in place. **3. Who is called** This step lists your people. Tick each person to call, or tick **Select All**. Use the search box or **Filters** to narrow the list by **Tags**, **Consent Status** or **Last Contact**. A green tick next to a name means consent is recorded. A red cross means it is not. The banner at the top updates as you tick: **TCPA Compliance Verified**, **Partial Consent** or **No Valid Consent**. People without consent are left out of the campaign. **Add new target** lets you add a person without leaving the wizard. Click **Next**. It needs at least one person with consent ticked. **4. From where and when** Pick **The number to call from**, or leave it unpicked for the platform default. Then choose when the calls happen: **As soon as I launch**, **On a date** or **Repeating**. Set **Only call between** two times, pick a **Background sound**, and set **Calls at the same time**. Every field on this step is explained in [Schedule, pacing and retries](https://docs.deepblocker.ai/vishing/campaigns/schedule.md). The defaults work for a first test: one call at a time, between 09:00 and 17:00, with the office background. **5. Authorise and launch** Under **Name this campaign**, the **Campaign name** is prefilled from the attacker and the date. Change it to anything you will recognise in the list. The **Note** is optional. Check the summary cards, then fill in **Engagement authorization**: **Authorized by**, **Authorizer email** and **Engagement / SOW reference**. Tick both confirmation boxes and click **Launch**. Every field is explained in [Authorise and launch](https://docs.deepblocker.ai/vishing/campaigns/authorise.md). The **Cost Estimation** card is a rough guide only: | Figure | How it is worked out | | - | - | | **Total Calls** | One per person with consent | | **Est. Minutes** | Three minutes per call | | **Cost per Call** and **Total Cost** | An internal estimate shown in dollars. Ignore it: your licence is charged in minutes, not money | What really counts is **Est. Minutes** against your licence. See [How minutes work](https://docs.deepblocker.ai/vishing/minutes.md). > [!TIP] > > Not ready to call anyone? Use **Save as draft** on any step, or **Save & rehearse first** on the last step. Then take a [test call in your browser](https://docs.deepblocker.ai/vishing/campaigns/test-call.md) before you launch. ## What happens next The campaign is saved and started. You see **Campaign created**, then **Campaign started**. The calls begin on the schedule you set, inside your calling hours. Open the campaign from the **Campaigns** list to [watch it live](https://docs.deepblocker.ai/vishing/live.md), and read the results once the calls end. See [Read your results](https://docs.deepblocker.ai/vishing/results/overview.md). ## Problems > [accordion] Next is grey and I cannot move on > > Each step has one rule. Step 1 needs an attacker and a script. Step 2 needs at least one person with consent. Step 3 needs a start date and at least one call at a time. Step 4 needs a name and the authorisation. > [accordion] It says 'No script yet' > > The attacker you picked has no script of its own and you did not pick a template. Go back to the top of the page and pick a campaign template, or write the script under **Who calls**. > [accordion] It says 'Saved, but the campaign did not start' > > The campaign exists but a server check refused the launch. Open it from the **Campaigns** list. The reason sits next to the **Launch** button. See [Troubleshooting](https://docs.deepblocker.ai/vishing/troubleshooting.md). > [accordion] A window says we are out of minutes > > Your licence minutes are used up. See [When you run out](https://docs.deepblocker.ai/vishing/minutes-exhausted.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.