Skip to main content
Find the message you see on screen below. Each entry says why it appears and what to change.

Launch is blocked

The campaign page lists what still stands between you and Launch. The wizard shows the same checks, one step at a time.
The campaign has nobody to make the call. Open the Who calls step and pick an attacker from your list. If the list is empty, create one first. See Create an attacker.
A single-call campaign needs a script. This one has none, and the attacker has no script of its own to fall back on. Pick a campaign template at the top of the page, or write the script under Who calls. The server makes the same check, so an older campaign can show this on launch even when the wizard let it through. See Build a campaign.
No one is selected on the Who is called step. Open it and tick the people to test, or add them under People first. A help desk test does not need this, because it calls your help desk numbers instead. See Add the people you will call.
This appears only when the campaign uses the Vapi calling system, which needs a number of its own. Open From where and when and pick one of the numbers allocated to your workspace. The default calling system picks a number for you, so most campaigns never see this. See Your caller numbers.
A scripted single call must start with a fixed sentence. Set it on the campaign under Who calls, or give the attacker an opening line of its own, which the campaign uses when it has none. Sequences, autonomous campaigns, help desk tests and call-back traps write their own opener, so they never show this. See Create an attacker.
Launch needs three things on the Authorise and launch step: the authoriser’s name, a valid email address, and the scope tick. A help desk test or a call-back trap also needs its own scope tick and a short note. The server refuses a launch without them, whatever the wizard showed. See Authorise and launch.
The help desk step is incomplete. It needs one to five help desk numbers in international format, opening hours, and at least one employee who has agreed to be impersonated. See Run a help desk test.
A call-back trap needs the message your staff receive and the objective the caller works towards. Fill both on the Call-back trap step. See Build a campaign.
The From where and when step needs a start date and at least one call at a time. Set both and the message goes. See Schedule, pacing and retries.
The name is on the Authorise and launch step. It must be between 1 and 100 characters, and the optional note at most 500. See Build a campaign.
The executive whose cloned voice this campaign uses has withdrawn consent. The clone was deleted, a draft campaign is blocked and a running one was paused. Open the campaign, choose a different voice, save, then launch again. See Clone an executive’s voice with consent.
The cloned voice the campaign points at no longer exists in your workspace. Open the campaign, pick another voice on the attacker or the campaign, and launch again. See Add a voice.
You can only launch a campaign that is a draft, failed or cancelled. This one is in progress. Pause it or wait for it to finish, then edit and launch again. See Pause, resume, stop everything.
Your workspace has used all of its simulation minutes for the current licence period, so no more calls can run. The window shows your licence, the minutes left and the price of extra minutes. Email hello@deepblocker.ai to top up or extend; minutes are not bought in the app. See When you run out.

Nothing is dialling

Someone pressed Stop all calls on the Campaigns page. No new call goes out for your workspace until you press Resume calling; calls already in progress finish on their own. After resuming, launch or re-run the campaign. See Pause, resume, stop everything.
An immediate campaign still waits for the calling hours set on From where and when, so nobody is called at night. Tick Call right now, even outside my hours to dial straight away. A scheduled campaign waits for its start date, and a help desk test waits for the help desk’s opening hours. See Schedule, pacing and retries.
These are your Fair testing rules. Excluded means the person is on the excluded list or has a do-not-call date. New joiner means they were added less than the set number of days ago and have never been tested. Cooling off and Quarterly limit mean another campaign called them too recently, or too often in the last 90 days. The campaign skips the person; change the rule on the Fair testing page or wait. See Fair testing rules.
Quiet hours hold the call rather than skip it. The campaign tries again as soon as the quiet period ends, in the timezone you set. See Fair testing rules.

The test call

Your browser has not allowed the microphone, or the tab is muted. In Chrome, click the lock icon next to the address, set Microphone to Allow, then press Call again. Use headphones to stop your speakers feeding your microphone. See Take a test call in your browser.
The caller could not be set up, most often because its voice is unavailable. Press Call again once. If it fails again, check that the attacker has a voice with consent recorded, then try once more. See Take a test call in your browser.

Results

The person did not pick up, or the call reached voicemail, so there was no conversation. This counts as Not reached, not as a pass or a fail. With Try again when nobody answers on, the campaign makes up to three attempts, 60 minutes apart. See Read your results.
The call could not be completed at all. Check the person’s number under People: it must be a real number in international format. If the number is right and it fails again, write to contact@deepblocker.ai with the campaign name. See Read your results.

Importing people

Every row needs a name, a phone number and a role. If any row lacks one, the whole file is refused and nothing is imported. Fill the gaps and upload again. See Add the people you will call.
A row fails with Invalid phone number or Duplicate phone number. A number without a leading plus sign is read as a US number, so write every number in international format, for example +44 20 7946 0000. A number already in your workspace is skipped. See Add the people you will call.
The limit is 10 MB per file. Split the file and upload the parts one at a time. See Add the people you will call.

Research

Research needs a search service that DeepBlocker switches on per deployment. Yours does not have it yet. Ask us to turn it on. See Support and contact.
An attack angle can only be chosen on a profile you have confirmed. Open the profile, check it is the right person, confirm it, then choose the angle and launch the pre-filled campaign. See Build a campaign.
An invite only works for the email address it was sent to. Sign out, sign in with that address, then open the link from the email again. See Invite your team and roles.
Signing in does not bring you back to the invite. Once you are signed in, open the link from the email again and it completes on its own. See Sign in, password reset, staying signed in.
Still stuck? Write to contact@deepblocker.ai with the campaign name and the message you saw. See Support and contact.