Configuring Outbound Campaign Call Analysis (CPA) Tuning for Accurate AMD

How-To-Articles
1

Configuring Outbound Campaign Call Analysis (CPA) Tuning for Accurate AMD

Executive Summary & Architectural Context

In automated Outbound Campaigns (Predictive or Power Dialing), the critical moment of any interaction is the first 2 seconds after the call connects. The dialer must instantly determine who answered the phone: A Live Human, an Answering Machine, a Fax/Modem, or a Carrier Intercept message. This process is called Call Progress Analysis (CPA) or Answering Machine Detection (AMD).

If CPA is poorly tuned, the results are disastrous. If the dialer mistakes a live human for an answering machine, the call is dropped (an abandoned call violation). If it mistakes an answering machine for a live human, it routes dead air to a human agent, devastating agent productivity and morale.

This masterclass details how to architect and tune the CPA acoustic models in Genesys Cloud, adjust silence thresholds, and optimize the dialer for maximum agent utilization while remaining compliant with strict abandonment rate laws (like TCPA/Ofcom).

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 2 or 3 (Outbound Campaigns required).
  • Roles & Permissions: Outbound > Call Analysis Response > Edit, Outbound > Campaign > Edit.
  • Platform Dependencies: An active Edge Group or BYOC trunk capable of routing outbound media.

The Implementation Deep-Dive

1. Understanding the CPA Acoustic Engine

When a call connects, Genesys Cloud listens to the audio stream for specific patterns:

  • Live Voice: A short burst of speech (“Hello?”) followed by silence.
  • Answering Machine: A long, continuous burst of speech (“Hi, you’ve reached John Doe, I’m not here right now…”).
  • Silence: No audio detected (often means the network connected early before the handset was picked up).

2. Creating the Call Analysis Response Set

You must tell the dialer exactly what to do based on the acoustic analysis.

  1. Navigate to Admin > Outbound > Call Analysis Responses.
  2. Create a new Response Set (e.g., Standard_Consumer_AMD).
  3. Define the routing logic:
    • Live Person: Route to → Sales_Queue.
    • Answering Machine: Transfer to Flow → Drop_Voicemail_Flow (or simply hang up).
    • Busy: Hang up and auto-reschedule.
    • Fax: Mark contact as uncallable.
    • Silence: Route to → Sales_Queue (It is better to waste an agent’s time with silence than to drop a live human and violate abandonment laws).

3. Tuning the Edge / Media Tier CPA Settings

The actual sensitivity of the AMD engine is tuned at the telephony layer.

  1. Navigate to Admin > Telephony > Sites (or Edge Groups, depending on deployment).
  2. Locate the Outbound Routing or Media settings.
  3. Adjust the core CPA parameters:
    • Maximum Allowed Silence: Default is usually 2.0 seconds. If a human says “Hello… [1.5s pause]… Anyone there?”, the dialer might get confused.
    • Answering Machine Threshold: This is the duration of speech required to classify the audio as a machine. If set to 2.5 seconds, any continuous talking longer than 2.5 seconds flags as an answering machine.
      • Best Practice: For B2B campaigns (where receptionists answer “Thank you for calling Acme Corp, how can I help you?”), increase this threshold to 3.5 seconds, otherwise receptionists will be flagged as machines.

4. Applying the Response Set to the Campaign

  1. Navigate to Admin > Outbound > Campaigns.
  2. Select your active campaign.
  3. Under the Call Analysis Response dropdown, select Standard_Consumer_AMD.
  4. Ensure Call Analysis is actively toggled ON (if toggled off, the dialer connects everything directly to agents immediately).

Validation, Edge Cases & Troubleshooting

Edge Case 1: High “Abandoned” Rates (The 2-Second Rule)

Under TCPA/FCC laws, an automated dialer must connect a live human to an agent within 2 seconds of the human’s greeting.

  • The Trap: If your CPA analysis takes 3 seconds to definitively decide if the voice is a human or a machine, you have already violated the 2-second rule. The caller has likely hung up in frustration (“Hello? … Hello?? click”).
  • Solution: You must balance accuracy with speed. If your compliance team mandates strict 2-second routing, you must lower the CPA analysis window. The tradeoff is that more answering machines will “slip through” to your agents, because the engine didn’t have enough time to analyze the full greeting.

Edge Case 2: Pre-Connect Audio (Early Media)

Sometimes carriers send ringing tones or intercept messages (“The number you have dialed…”) before the SIP 200 OK connect message.

  • Troubleshooting: Genesys Cloud CPA officially starts analyzing audio after the SIP 200 OK. If the carrier sends audio via Early Media (SIP 183 Session Progress), standard CPA may miss it.
  • Solution: Ensure your BYOC Carrier/SBC is configured to handle Early Media correctly and pass the RTP stream to Genesys Cloud so the Call Progress Analysis engine can begin evaluating the audio immediately.

Official References