An AI voice agent that speaks the moment a call connects will deliver its opening line to voicemail greetings, IVRs and call screeners. VM Hunter tells the agent what answered, about two seconds in, so it knows whether to talk, wait or hang up.
Outbound voice agents inherit the dialer's oldest problem in a new form. A human agent hears a voicemail greeting and hangs up. A bot hears nothing it was not told to listen for, so it starts the script. The call is billed, the conversation budget is spent, and if the script runs long enough the voicemail records a fragment of it.
The fix is the same one dialers use: decide what answered before anyone speaks. VM Hunter listens to the first two seconds of the callee's audio and returns a verdict with a reason. The agent gates on it.
On real campaign traffic, live people are a minority of answered calls. A typical mix from our logs:
| What answered | What the agent should do |
|---|---|
| Voicemail greeting (personal, business or carrier) | Hang up, or wait for the beep and leave a short message |
| IVR or hold prompt | Hang up, or navigate if that is the point of the call |
| Call screening (iPhone, Google, call blockers) | State who is calling and why, then wait for the person |
| Disconnected number (SIT tone) | Retire the number |
| No audio at all | Wait briefly, then hang up; usually a trunk problem |
| A live person | Start the conversation |
VM Hunter labels each of these, so the agent's first action can depend on which one it is.
AMDCAUSE with the call so you can see what your list is made of.On Asterisk or FreeSWITCH the bundled clients do the fork and set channel variables your agent logic can read. On Twilio the Media Streams bridge redirects the call to one TwiML for a person and another for a machine. Any other stack that gives you the raw audio can use the API directly; the clients are open source on GitHub as references.
Get a free key, fork one campaign's audio, and read the verdicts in your call logs. 5,000 calls a month on the free plan.