VICIfast
All posts
Tag

answering-machine-detection

50 posts.

AM Message Wildcards: A Different Voicemail Per Lead

AM Message Wildcards let VICIdial play a different answering-machine message based on a value in the lead record. Here is how to turn it on and use it.

Read post

The KHOMP Settings Container: Per-Campaign KHOMP Options

How the KHOMP_SETTINGS container lets you apply one set of KHOMP detection options to a single campaign without touching the rest.

Read post

How to Switch On AMD for an Outbound VICIdial Campaign

A step-by-step walkthrough for enabling Answering Machine Detection on a VICIdial outbound campaign, from the dialplan check to the VDAD exten change.

Read post

AMD vs a Longer Dial Timeout: Which Dodges Voicemails Best

Answering Machine Detection and a tuned Dial Timeout both cut voicemail pickups. Here is how to choose the right one for your outbound campaign.

Read post

Why AMD Does Nothing in MANUAL and INBOUND_MAN Modes

Set everything up correctly and AMD still does nothing? If your dial method is MANUAL or INBOUND_MAN, detection never runs. Here is why and what to do.

Read post

VICIdial AMD send to Action: What It Decides on a Machine

AMD send to Action tells VICIdial whether a detected machine gets a message or an instant hangup. Here is what each value does and how to set it.

Read post

What Campaign VDAD Exten Does and Why AMD Needs 8369

The Campaign VDAD exten field decides which call processor handles your dialed calls. Setting it to 8369 is what actually turns AMD on.

Read post

VICIdial AMD: Hang Up the Machine or Leave a Message

Detected a machine? You can drop the call instantly or play a voicemail. Here is how to choose the AMD outcome and configure each path.

Read post

VICIdial NOAUDIODATA-Hangup: Drop Silent Dead Calls Fast

The NOAUDIODATA-Hangup option ends calls that reach the AMD routing script with no audio at all, so dead lines never tie up your dialer or an agent.

Read post

VICIdial NOTSURE Calls: What They Are and How to Route Them

NOTSURE means detection could not decide. By default these go to agents. Learn what causes them and how to route them on your own terms.

Read post

VICIdial AMD: Auto-Hang Up Fax and False-Answer Calls

FAX and FAS hangup options in AMD route options end fax and false-answer calls instantly, keeping junk off your agents and your stats clean.

Read post

ViciAMD Agent Display: Show Machine Status to Agents

ViciAMD Agent Display surfaces the AMD status, cause, and a transcript of the call opening to the agent the instant a call lands, so they pick up with context.

Read post

ViciAMD vs Standard Asterisk AMD: What's Different

ViciAMD and the built-in Asterisk AMD both spot answering machines, but they differ in output, agent-facing data, and how you set them up. Here is the comparison.

Read post

Wait For Silence Options: Holding the Message Until the Beep

Wait For Silence Options tells VICIdial to listen for quiet on a machine before playing your message, so the recording does not start over the greeting.

Read post

How to Record an Answering-Machine Message with 8168

Dial 8168 from a registered VICIdial phone, enter PIN 4321, and record your answering-machine prompt. Here is the full process and the formats to use.

Read post

Why You Should Record Your Voicemail Message Twice in VICIdial

Recording your answering-machine prompt twice in one file keeps a clipped greeting from eating your message. Here is why it works and how to do it.

Read post

How to Leave a Pre-Recorded Voicemail on Answering Machines

Set AMD send to vm exten to Y and point the Answering Machine Message field at a recorded prompt to leave a clean voicemail on every detected machine.

Read post

VM Message Group: Let Agents Pick Which Voicemail to Drop

VM Message Group gives agents a panel of voicemail messages to choose from when they transfer a call to a voicemail box, instead of one fixed drop.

Read post

The VICIdial Voicemail Message Daily Limit and Why You Cap It

The Voicemail Message Daily Limit stops the same lead from getting your message over and over in one day. Here is how the cap works and when to use it.

Read post

Leave VM No Dispo: Keep the Agent on the Talk Screen

Leave VM No Dispo keeps the agent on the talk screen after dropping a voicemail, instead of jumping straight to the disposition screen. Here is when to use it.

Read post

Manual VM Status Updates: Track Voicemail Drops on Hand-Dialed Calls

Manual VM Status Updates brings answering-machine message statuses to hand-dialed calls in VICIdial, so voicemail drops on manual calls get logged the same way.

Read post

How to Tune VICIdial AMD Accuracy When It Is Wrong Too Often

AMD is not perfect out of the box. Here is how to tune VICIdial answering machine detection to your leads and lines and cut the wrong calls.

Read post

Why VICIdial AMD Flags Real People as Machines and How to Fix It

AMD false positives send live customers to a voicemail message or hang up on them. Here is why VICIdial does it and how to stop losing real answers.

Read post

The AMD() Asterisk Parameters and What Each Number Controls

The AMD() line in your VICIdial dialplan has eight numbers that decide human versus machine. Here is what each one controls and how to tune them.

Read post

Reading the AMD Log Report to See What AMD Actually Decided

The AMD Log Report shows the result detection returned on every call. Here is how to read it and use it to tune VICIdial answering machine detection.

Read post

VICIdial AMD Statuses Explained: HUMAN, NOTSURE and More

Understand the AMD statuses VICIdial assigns to answered calls and how those results decide which calls reach agents and which get diverted.

Read post

What VD_amd.agi Does After a Call Clears AMD in VICIdial

VD_amd.agi is the script that decides where a call goes once AMD has analyzed it. Here is what it does and where it sits in the dialplan.

Read post

VICIdial AMD Type: Built-in AMD vs Third-Party Engines

The AMD Type setting picks which detection engine routes your answered calls. Learn when to keep built-in AMD and when a third-party engine fits.

Read post

The Two Dialplan Entries VICIdial AMD Needs

AMD relies on two extensions in your VICIdial dialplan: 8369 for detection and routing, and 8320 for playing a message. Here is what each line does.

Read post

AMDMINLEN: Force VICIdial AMD to Run a Minimum Time

The AMDMINLEN variable makes the AMD routing script run for at least a set number of seconds before it ends a call. Here is when and how to use it.

Read post

What VICIdial Call Progress Detection Is vs AMD

Call Progress Detection classifies far more than answering machines. Here is what CPD does, how it differs from AMD, and where it fits in VICIdial.

Read post

VICIdial CPD AMD Action: DISPO, MESSAGE, INGROUP, CALLMENU

The CPD AMD Action setting decides what happens to a detected machine: dispose it, play a message, send it to a group, or route it to a call menu.

Read post

VICIdial CPD Unknown Action: Routing Calls That Defy Classification

When Call Progress Detection cannot tell what answered, the CPD Unknown Action setting decides where the call goes instead of an agent.

Read post

The VICIdial AMD Call Menu Setting: Sending Machines to a Menu

The AMD Call Menu field names the call menu that detected calls reach when your CPD action is set to CALLMENU.

Read post

How Call Progress Detection Lowers Your Dropped-Call Percentage

By labeling non-human answers, CPD lets you exclude them from your drop math, yielding a lower and more accurate dropped-call percentage.

Read post

The VICIdial AMD Inbound Group Setting and When Calls Use It

The AMD Inbound Group field tells VICIdial which inbound queue receives detected calls when your CPD action is set to INGROUP.

Read post

Sangoma NetBorder Call Progress Detection and Why It's End-of-Life

VICIdial once integrated with Sangoma NetBorder CPD, a paid high-accuracy engine. Sangoma retired it in 2017, so it is now end-of-life.

Read post

What Sangoma CPD Detected That Asterisk Can't: SIT Tones

Sangoma CPD classified pre-answer call progress like SIT tones, disconnects, and congestion that Asterisk's AMD cannot identify.

Read post

The Hidden Cost of VICIdial AMD: Extra Time on Every Call

AMD adds processing time to every answered call, not just the machines. Here is what that costs you and when Dial Timeout is the smarter trade.

Read post

The Dialer KHOMP Admin Tool: Coding Results to Statuses

How the Dialer KHOMP Admin Tool maps the gateway's raw call results onto the VICIdial statuses your reports and routing rely on.

Read post

The KHOMP SIP Gateway for AMD and Call Progress Detection

How the KHOMP SIP gateway gives VICIdial a dedicated AMD and call progress engine, and what you need to wire it into your dialers.

Read post

Why VICIdial AMD Misses Machines and Sends Them to Agents

AMD false negatives push answering machines straight to your agents. Here is why VICIdial misses machines and how to tighten detection to catch them.

Read post

Dialing Without Agents to Play a Message in VICIdial

Run a reminder or broadcast campaign that dials a list and plays a recording with no agent logged in. Here is how the auto-message setup works.

Read post

VICIdial AMD Agent Route Options: Which Calls Reach Agents

AMD Agent Route Options lets you decide exactly which detected statuses go to agents, overriding the default HUMAN and NOTSURE routing.

Read post

Play Now, Wait, or Wait for Silence: Three Message Methods

VICIdial gives you three ways to time a recorded message on an agentless campaign. Here is how play-immediately, set-wait, and wait-for-silence differ.

Read post

The Answering Machine Message Field: What to Put In It

The Answering Machine Message field tells VICIdial which prompt to play to a detected machine. Here are the values it accepts, from plain filenames to STC and LTT.

Read post

AMD and the UK OFCOM Drop Calculation: Changing the Math

OFCOM's 2015 drop formula factors answering machines into your abandon rate. Here is how it differs from the US method and how to switch it on.

Read post

The KHOMP Quick Stats Report: Spotting a Slow Gateway

How the KHOMP Quick Stats Report compares today's processing against past days so you catch a slowing detection gateway early.

Read post

Using Cepstral Text-to-Speech for Per-Lead Voicemail

How Cepstral text-to-speech lets VICIdial build personalized answering-machine messages from lead data instead of one static recording.

Read post

How VICIdial Detects Fax Machines and What to Do

How VICIdial flags fax answers during call progress detection and how to hang them up automatically instead of wasting dials.

Read post