> ## 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.

# Troubleshooting

> What to do when a launch is blocked, a test call is silent, nobody answered, an import is refused, research is off or an invite link fails.

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.

> [accordion] It says Choose an attacker, or Choose who calls: pick an attacker before launching
>
> 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](https://docs.deepblocker.ai/vishing/attackers.md).

> [accordion] It says Pick a campaign template or write the script for this campaign
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/create.md).

> [accordion] It says Add at least one person to call, or Pick at least one person to call before launching
>
> 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](https://docs.deepblocker.ai/vishing/people.md).

> [accordion] Who is called shows No Valid Consent and the wizard will not move on
>
> Every person you select must have a consent record. The panel says **None of the selected contacts have valid TCPA consent. Campaign cannot proceed.** when nobody selected has one. Open **People**, add the consent fields for each person, then come back and select them again. See [Add the people you will call](https://docs.deepblocker.ai/vishing/people.md).

> [accordion] It says Choose a number to call from, or Pick the number to call from before launching
>
> 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](https://docs.deepblocker.ai/vishing/caller-numbers.md).

> [accordion] It says Set an opening line, or This campaign has no opening line yet
>
> 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](https://docs.deepblocker.ai/vishing/attackers.md).

> [accordion] It says Record the authorisation, Confirm the authorisation before launching, or Campaign is not authorized
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/authorise.md).

> [accordion] It says Set up the help desk test before launching
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/help-desk.md).

> [accordion] It says Finish the call-back trap settings before launching
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/create.md).

> [accordion] It says Set when the calls happen before launching
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/schedule.md).

> [accordion] It says Give the campaign a name before launching
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/create.md).

> [accordion] It says Blocked: and then a name and the word withdrew
>
> 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](https://docs.deepblocker.ai/vishing/executive-voice-consent.md).

> [accordion] Launch says no consent is recorded for this cloned voice
>
> A cloned voice can only be used after someone attests, or the person records, their consent. Open **Voices**, find the voice, and record the consent on its card. A voice whose consent record is incomplete shows the same refusal. See [Add a voice](https://docs.deepblocker.ai/vishing/voices.md).

> [accordion] Launch says the voice could not be found
>
> 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](https://docs.deepblocker.ai/vishing/voices.md).

> [accordion] Launch says Campaign is already running
>
> 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](https://docs.deepblocker.ai/vishing/controls.md).

> [accordion] Launch shows Out of red-team minutes
>
> 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](mailto:hello@deepblocker.ai) to top up or extend; minutes are not bought in the app. See [When you run out](https://docs.deepblocker.ai/vishing/minutes-exhausted.md).

## Nothing is dialling

> [accordion] A red banner says Emergency stop is on
>
> 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](https://docs.deepblocker.ai/vishing/controls.md).

> [accordion] The campaign started but nobody has been called yet
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/schedule.md).

> [accordion] Some people were skipped and the page says Excluded, New joiner, Cooling off or Quarterly limit
>
> 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](https://docs.deepblocker.ai/vishing/fair-testing.md).

> [accordion] A person shows Quiet hours and has not been called
>
> 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](https://docs.deepblocker.ai/vishing/fair-testing.md).

## The test call

> [accordion] I answered the test call and hear nothing
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/test-call.md).

> [accordion] The page says Could not connect the test call
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/test-call.md).

## Results

> [accordion] The result says No answer or Voicemail
>
> 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](https://docs.deepblocker.ai/vishing/results/overview.md).

> [accordion] The result says Call failed
>
> 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](mailto:contact@deepblocker.ai) with the campaign name. See [Read your results](https://docs.deepblocker.ai/vishing/results/overview.md).

## Importing people

> [accordion] The import says CSV validation failed and rows are missing required fields
>
> 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](https://docs.deepblocker.ai/vishing/people.md).

> [accordion] The import finished but some rows failed
>
> 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](https://docs.deepblocker.ai/vishing/people.md).

> [accordion] The import says File too large
>
> 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](https://docs.deepblocker.ai/vishing/people.md).

## Research

> [accordion] Research says No research provider configured
>
> 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](https://docs.deepblocker.ai/support.md).

> [accordion] Research says Confirm this is the right person before choosing an attack angle
>
> 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](https://docs.deepblocker.ai/vishing/campaigns/create.md).

## Invite links

> [accordion] The invite says This invite is for a different email address
>
> 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](https://docs.deepblocker.ai/account/team.md).

> [accordion] The invite link says it is expired, already used, revoked or not valid
>
> A link works once and for seven days. After that, or if an owner revoked it, it is dead. Ask a workspace owner or admin to send a new one. See [Invite your team and roles](https://docs.deepblocker.ai/account/team.md).

> [accordion] I pressed Sign in on the invite page and landed on the dashboard
>
> 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](https://docs.deepblocker.ai/account/sign-in.md).

Still stuck? Write to [contact@deepblocker.ai](mailto:contact@deepblocker.ai) with the campaign name and the message you saw. 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.