AA — Auto Answering Machine

What AA Means

Answering machine detected automatically by the AMD system — the system identified the call as a machine without agent involvement. Distinct from A (manual) to allow separate reporting on AMD accuracy.

When This Status Is Set

The AA status is assigned exclusively by VICIdial’s AMD (Answering Machine Detection) engine when it classifies a connected call as a machine without any agent involvement. Unlike the A status — which can be set manually by an agent — AA is always system-generated, providing a clean data point for measuring AMD accuracy. The classification occurs within the first few seconds of the call based on audio analysis of greeting length, speech cadence, and silence gaps. If the campaign has amd_send_to_vmx disabled, calls classified as AA are simply dispositioned and the trunk is released; if enabled, the call may be routed to a voicemail-drop extension before the AA status is written to the vicidial_list table.

Impact on List Management

AA leads should always be included in your dial_status_filter for recycling because they represent active numbers with confirmed voicemail systems — a strong indicator that a real contact owns the line. Tracking AA separately from A gives you a built-in accuracy benchmark for your AMD configuration: if the AA-to-A ratio is heavily skewed toward AA and your live contact rate is declining, AMD is likely generating false positives and routing live answers away from agents. When configuring lead_recycling rules, treat AA identically to A in terms of attempt limits and delay intervals, but use the separate status code to run divergence reports. High AA volumes during specific hours feed directly into the hopper fill algorithm, so monitor whether your hopper_level is being consumed by recycled AA leads at the expense of fresh NEW leads.

Best Practices

• Compare AA to A ratio to measure AMD false positive rate — a healthy operation typically sees AA at 2-4x the manual A count

• Include AA in dial_status_filter for recycling with time-of-day rotation to catch contacts live

• Use AA rate trend to detect AMD tuning needs after carrier changes, codec switches, or SIP trunk migrations

• Run a weekly report comparing AA counts against vicidial_carrier_log answer durations to identify calls where AMD fired on short human greetings

• If AA rate spikes suddenly, check whether a carrier changed their ringback tone or added a pre-connect announcement that AMD is misinterpreting

Admin Configuration

The AA status is defined in Admin → System Statuses and is not agent-selectable by default. AMD behavior that produces AA dispositions is controlled at the campaign level under Campaign Detail → AMD/VM Settings, where you configure cpd_amd_action, AMD sensitivity thresholds, and the amd_send_to_vmx toggle. Lead recycling parameters for AA — including attempt delay and maximum attempts — are set in Campaign Detail → Lead Recycling alongside other recyclable statuses.

ViciStack’s List Management module monitors disposition distribution in real time — automatically adjusting recycling logic, dial_status_filter priorities, and hopper fill strategies based on how your dispositions are trending. No manual SQL, no spreadsheet audits.