From "hello" to a decision in the first seconds of the call
AMDelete replaces the answering machine detection step in your VICIdial dialplan. Everything else about your campaigns stays the same.
1. The call is answered
When the carrier answers an outbound call, VICIdial sends it to the campaign's answering machine detection step. Campaigns you've switched to AMDelete enter AMDelete instead of VICIdial's AMD(); every other campaign is untouched.
2. We listen
The adapter on your dialer streams the called party's audio to api.amdelete.com over an encrypted keep-alive connection. From 500 ms in, every 250 ms, the service scores everything heard so far with a streaming neural detector.
3. A decision lands
- Live person: the call goes to an agent as soon as the detector is confident. It always hears at least 2.5 seconds first, so a quick "Hello?" isn't mistaken for the start of a greeting.
- Machine: voicemail greetings, beeps, fax tones, carrier messages and screeners close with an AMDelete status (
ADMAC,ADVM,ADBP,ADFX,ADRG) and the lead follows your normal recycling. - Not sure: at the end of the 8-second listening window the call goes to an agent. The one exception is a line that stayed nearly silent the whole time: no one is there, so it's closed rather than handed to an agent.
4. Your agents grade it
About half an hour after each call, the dialer looks up how the agent dispositioned it and reports VICIdial's meaning of that status. On your campaigns still using VICIdial AMD, it reports hourly counts of the same thing, so the console can show both detectors side by side on the same dialers and agents.
5. Something went wrong? Your local fallback takes over
If the service is unreachable, your credits run out, or a key is revoked, the adapter hands the call to the fallback route configured inside your dialer within the first probe and pauses AMDelete briefly. If you do not define a local override, the fallback defaults to VICIdial AMD. The portal and service never select or rewrite that route.
Next to what you run today
- AMDelete adds a route of its own and never edits VICIdial's AMD or any route your campaigns use
- You switch campaigns one at a time, in VICIdial's campaign settings
- The installer stops if your dialplan has edits Asterisk hasn't loaded yet, or if another product's files are where it would write
amdelete-ctl killsends every call to your dialer's fallback route instantly, with no dialplan reload
What leaves your dialer
- The called party's audio for the first seconds after answer
- An opaque per-call reference (an HMAC, not the call id or phone number)
- Your installation's key
- Later, how agents dispositioned AMDelete calls, as VICIdial's meaning of each status
- A daily dialer profile: hardware, versions and AMD settings
No phone numbers, lead data, agent names or agent audio. Decision logs stay on the dialer. Exactly what's reported