Overview
Answering Machine Detection (AMD) enables your AI agents to automatically detect when outbound calls reach voicemail instead of a live person. When voicemail is detected, the agent hangs up and logs the outcome, allowing you to retry at different times to maximize chances of reaching a live person. This critical feature prevents wasted agent time talking to answering machines and optimizes campaign efficiency by focusing resources on live conversations rather than voicemail systems.Phone Calls Only: AMD applies to phone calls via SIP/PSTN connections. Web-based conversations without a phone leg do not support DTMF interaction.AMD configuration is accessed during campaign creation and test calls. Text-Based AMD is always active. You can optionally enable ML-Based AMD as an addon for faster detection (~1.5s vs 5-15s).
What is Answering Machine Detection?
The Challenge
When making outbound calls, you encounter two possible scenarios: Scenario 1: Live AnswerAMD Solution
AMD analyzes the audio in the first few seconds after call connection to determine if a human or machine answered: Detection process:- Efficiency: Don’t waste agent time on voicemail
- Better targeting: Focus retry attempts on different times to reach live person
- Higher connect rates: Optimize call timing based on voicemail patterns
- Better analytics: Separate “reached voicemail” from “no answer” in reporting
AMD Methods
Overview of Detection Types
Text-Based AMD
Keyword-based detection using transcriber and LLM - always active
ML-Based AMD (Optional)
Fast pattern recognition using Deep Neural Network - optional addon for speed
Text-Based AMD
Role: Base detection layer that always runs. Uses your agent’s transcriber and LLM to identify voicemail keywords. How it works:Speed
Speed
Slower: Waits for complete turn/utterance to finishMust wait for the entire voicemail greeting to complete (pause detected), then transcribe and analyze the full text. Typical detection occurs after 5-15+ seconds depending on length of voicemail message.Limitation: Long voicemail greetings mean longer wait times before detectionBest for: Campaigns where accuracy is more important than immediate detection
Accuracy
Accuracy
High accuracy when:
- Standard voicemail greetings with common phrases
- Clear audio quality
- Voicemail language matches transcriber language
- B2B environments with professional greetings
- Voicemail greetings in languages the transcriber doesn’t support
- Voicemail systems with no greeting (just beeps)
- Non-verbal voicemail indicators
- Custom greetings without standard keywords
- Short greetings (“Hi, leave a message” - very brief)
- Poor audio quality or background noise
- Background noise interfering with transcription
Best Use Cases
Best Use Cases
Ideal for:
- B2B campaigns - Business voicemails typically use standard phrasing
- Campaigns prioritizing accuracy - Reduces false positives by analyzing full utterance context
- Budget-conscious deployments - Lower computational cost
- English-language markets - Keyword detection optimized for English
- Sales outreach to business phone numbers
- Appointment reminders to office lines
- B2B lead qualification campaigns
Limitations
Limitations
May struggle with:
- Personal, creative voicemail greetings (“Hey, it’s Mike, you know what to do”)
- Very short greetings
- Voicemail language doesn’t match transcriber language
- Greetings that sound conversational (“Hello? Hello? Just kidding, leave a message”)
- Background music or noise in greeting
ML-Based AMD (Optional Addon)
Role: Optional fast detection layer you can enable for speed. Works in parallel with text-based AMD. How it works:Speed
Speed
Fast: ~1.5 secondsIdentifies live human responses within 1.5 secondsMuch faster than text-based AMD which must wait for complete utterance
Accuracy
Accuracy
Very high accuracy in real-world conditionsWhy enable ML-Based AMD:
- Language-independent: Works across all languages (text-based only works if transcriber language matches)
- Detects beep-only voicemail: Catches voicemail systems with no greeting (text-based cannot)
- Handles creative greetings: Detects personal/non-standard greetings without keywords
- Pattern-based detection: Doesn’t rely on specific voicemail keywords
- Fast detection: ~1.5 seconds vs 5-15+ seconds for text-only
- Better for multi-language campaigns: No language configuration needed
- Extremely short connections (< 0.5 seconds of audio)
- Highly degraded audio quality
Best Use Cases
Best Use Cases
Ideal for:
- Consumer campaigns - Personal voicemails with creative greetings
- Multi-language campaigns - Not dependent on English keywords
- Quality-focused campaigns - When accuracy is more important than speed
- Complex markets - Mixed business/personal numbers
- Consumer sales calls
- Political campaigns
- Non-profit fundraising
- Healthcare outreach
- Multi-language support campaigns
Advantages
Advantages
Handles well:
- Creative personal greetings
- Short greetings
- Non-English voicemails
- Greetings without standard keywords
- Background music or sound effects
- Natural conversational-sounding greetings
- Different languages
- Regional accents
- Various voicemail systems
- Custom greetings
How AMD Works
Text-Based AMD (Base Layer):- Always active
- Analyzes transcription for voicemail keywords
- Waits for complete utterance (5-15+ seconds)
- More conservative - rarely hangs up on live people
- You can optionally enable this for faster detection
- Analyzes audio patterns in ~1.5 seconds
- Works in parallel with text-based AMD
- Faster but may occasionally hang up on live people
- Only text-based detection active
- Slower detection (5-15+ seconds)
- Rarely hangs up on live people
- Trade-off: Might miss some voicemails and talk to them
- Best for: When you want to avoid hanging up on live people at all cost
- ML detects in ~1.5 seconds
- Text-based validates in parallel
- Very high accuracy
- Trade-off: Occasionally might hang up on a live person
- Best for: Campaigns where talking to voicemail incurs additional cost
Configuring AMD
AMD can be configured in two places:Test Phone Calls
Enable AMD when testing your agent with phone calls
Campaign Settings
Configure AMD for outbound campaigns
Test Phone Calls
Configure AMD when testing your agent via phone:

Configure AMD
Find the Answering Machine Detection (AMD) settingChoose between:
- Text-based (default) - Avoids hanging up on live people at all cost
- ML-based - Fast detection (~1.5s) but may occasionally hang up on live people
Campaign Settings
Configure AMD for outbound campaigns:

Select AMD Strategy
Find Answering Machine Detection (AMD) dropdownChoose voicemail detection strategy for this campaignSelect one:
- Text-based - Avoids hanging up on live people at all cost (slower, 5-15s)
- ML-based - Fast detection (~1.5s) but may occasionally hang up on live people
- Navigate to campaign Settings tab
- Locate Answering Machine Detection (AMD) dropdown
- Select different strategy (Text-based or ML-based)
- Save changes
AMD Behavior
When AMD detects voicemail, the agent automatically hangs up and logs the outcome. The call is marked as MACHINE in campaign analytics, allowing you to schedule retries at different times to increase chances of reaching a live person.Testing AMD Configuration
AMD Test Plan
Test ML-Based AMD
Setup:
- Configure agent with ML-Based AMD enabled
- Prepare test phone number with voicemail
- Start test call to voicemail number
- Let call go to voicemail
- Monitor agent behavior
- Agent hangs up within ~1.5 seconds
- Call marked as MACHINE in logs
- No conversation attempt with voicemail greeting
Test Text-Based AMD
Setup:
- Configure agent with Text-Based AMD only
- Use same voicemail test number
- Start test call
- Let call go to voicemail with standard greeting
- Agent waits for complete greeting (5-15+ seconds)
- Agent hangs up after detecting keywords
- Call marked as MACHINE
Test Live Person Detection
Setup:
- Test with both AMD methods
- Answer call personally
- Start test call
- Answer and say “Hello?”
- Verify agent continues conversation normally
- Agent does NOT hang up
- Normal conversation proceeds
- Call NOT marked as MACHINE
Test Edge Cases
Scenarios to test:Silent answer:
- Answer but don’t speak
- Verify AMD doesn’t misclassify
- Answer with very brief “Hi”
- Verify conversation continues
- Test with non-standard greeting
- Monitor ML vs text-based performance
- Voicemail system with no greeting
- Verify ML-based detects, text-based may miss
Troubleshooting
Wrong AMD Method Selected
Wrong AMD Method Selected
Symptoms: Performance not matching expectationsCheck:
- Review campaign AMD setting
- Compare expected vs actual detection speed
- Check false positive/negative rates in logs
- Switch between Text-based and ML-based
- Test both methods with your call patterns
- Choose based on your priority (speed vs conservative)
High False Positive Rate
High False Positive Rate
Symptoms: Hanging up on live people frequentlyAnalysis:
- Review call recordings of false positives
- Check if ML-based AMD is being too aggressive
- Identify common patterns (background noise, specific greetings)
- Switch to Text-based AMD (more conservative)
- Improve call quality/reduce background noise
- Test from different phone numbers
- Contact support if persistent
High False Negative Rate
High False Negative Rate
Symptoms: Agent frequently talks to voicemailAnalysis:
- Check if voicemails have non-standard greetings
- Review if beep-only voicemail systems
- Verify transcriber language matches voicemail language
- Switch to ML-based AMD (better for non-standard greetings)
- ML-based detects beep-only systems
- Ensure agent speaks same language as target audience