Create & launch a vishing campaign
A vishing campaign places AI voice-phishing calls to a list of targets to test who picks up, who complies, and who reports, then routes outcomes into training. This page walks the full flow, from building a scenario to reviewing results.
Prerequisites
Before you can launch, you need:
- A phone number provisioned for the destination country (see Buying & managing phone numbers).
- For regulated destinations, an approved compliance bundle: see Country compliance. This is enforced at dispatch, so it must be in place before the campaign fires.
- A target audience: an eligible employee list (see Target audience & eligibility).
How to use it
The campaign builder is a step-through wizard:
- Scenario: pick or generate a scenario (persona + script + variables). Edit the variable chips inline to tailor names, companies, and other details.
- Target audience: choose who receives the simulation; the builder shows eligibility and coverage for each country.
- Call settings & pacing: assign the caller number per country and set the dialing pace.
- In-call education: configure what the target hears after the simulation (the compliance/teachable moment).
- Summary: a go/no-go pre-flight of what will happen; review and launch.
When you launch, the platform stores the schedule; at fire time it places the calls through the AI calling engine, streams status and transcript back as each call progresses, and surfaces the results in reporting.
Configuration & options
| Setting | What it does | Where |
|---|---|---|
| Scenario | Persona, script, and variables for the call | Step 1 |
| Variables (chips) | Per-target values (name, company, …) resolved at call time | Step 1 |
| Target audience | Eligible recipients + per-country coverage | Step 2 |
| Caller number | The number presented per destination country | Step 3 |
| Dialing pace | How fast calls are placed | Step 3 |
| In-call education | The post-simulation teachable moment | Step 4 |
Gotchas & limitations
- Regulated countries block at dispatch, not at create. EU "disintermediation" destinations (France, Germany, Iceland, Ireland, Italy, Portugal, Spain) require an approved regulatory bundle before a number can be used. You can build the campaign, but it will be gated at fire time until the bundle clears. Plan bundle approval ahead of launch.
- Italy presents caller ID differently. Italy enforces CLI blocking at the originating carrier, so the presented caller ID must be configured accordingly.
- The test voice is not the production voice. In non-production environments, calls use a built-in test voice, so the voice you hear while testing differs from the voice a real campaign uses.
Best practices
- Verify your destination's compliance state and number before scheduling, so a campaign doesn't stall at dispatch.
- Keep the first run small so pacing and outcomes are easy to observe before scaling up.
Troubleshooting / FAQ
My campaign launched but no calls went out, why? The most common cause is a compliance gate at dispatch (an unapproved bundle for a regulated country) or a missing/ineligible caller number for the destination. Check the destination's country compliance state and its assigned number.