You need a campaign first. If you have none, follow Build a campaign or start from the Get started checklist in the console, which builds one from a template.
Before you start
- A campaign in your workspace. Any status will do; it does not need to be launched.
- A browser with a working microphone. Chrome, Edge and Safari work. The browser will ask for microphone permission once.
- Headphones, if you can. The attacker’s voice plays through your speakers and your microphone is open, so headphones stop an echo.
Steps
1
Open the test call page
In the console, open the Get started pill at the top of the screen and choose Run your first test call. It opens the test call for your newest campaign.You can also open it by address:
https://deepblocker.ai/red-team/campaigns/<campaign id>/test-call. The campaign id is the last part of the campaign’s own address.The page is titled Talk to this persona. While it says Preparing the caller… this takes a few seconds, the attacker is being set up.2
Answer the call
When the button Answer the call appears, click it. The caller speaks first. If your browser asks for the microphone, choose Allow.The page shows Connecting… allow the microphone if your browser asks for a moment, then the call is live.
3
Talk, and listen for what matters
Speak as one of your staff would. Push back, ask questions, stall. Listen for three things:
- Does the opening line land the way you wrote it?
- Does the voice sound like the person it is meant to be?
- Does the background sound fit the story (an office, a car, silence)?
4
Call again, or go and fix the campaign
After the call ends you get two buttons. Call again starts a fresh call with the same campaign. Edit the campaign takes you back to change the opening line, the voice, the tone or the background sound. Come back and call again until it sounds right.
What happens next
Nothing is recorded against any member of staff, and the call does not appear in your campaign results. If this was your first test call, the Get started checklist marks its last step done. When the call sounds right, go to the campaign and launch it. See Authorise and launch.Problems
I hear nothing after I answer
I hear nothing after I answer
Check that your browser allowed the microphone and that the tab is not muted. In Chrome, click the lock icon next to the address and set Microphone to Allow, then click Call again.
The page says it could not start the test call
The page says it could not start the test call
The attacker’s voice may be unavailable. Open the campaign, check that the attacker has a voice with consent recorded (see Clone an executive’s voice with consent), then try again. If it still fails, write to contact@deepblocker.ai with the campaign name.
I hear myself with a delay
I hear myself with a delay
That is your speakers feeding your microphone. Use headphones, or lower the speaker volume.
The caller interrupts me
The caller interrupts me
The attacker is built to react, and will talk over you if you pause. That is deliberate: it is what a real caller does. If it is too aggressive for your staff, lower the attack level on the campaign’s Who calls step.