Skip to main content
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 uses the same wizard with one step swapped.
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.

Before you start

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.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.
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: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. 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.The Cost Estimation card is a rough guide only:What really counts is Est. Minutes against your licence. See How minutes work.
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 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, and read the results once the calls end. See Read your results.

Problems

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.
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.
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.
Your licence minutes are used up. See When you run out.