Hi everyone,
Just to close this loop off, I managed to get this working with Customer First callbacks.
I configured two separate Inbound Call Flows:
-
Live Voice: Transfers to a callback announcement flow, which retrieves the original queue from participant data and routes the customer back to that queue.
-
Answering Machine: Transfers to a dedicated voicemail flow that plays a prerecorded message before disconnecting.
During testing, I noticed that the carrier's default voicemail greeting was correctly detected as Answering Machine, but a custom voicemail greeting was sometimes detected as Live Voice, resulting in the callback reaching an agent.
To address this, I added a Collect Input action to the Live Voice flow, asking the customer to press 1 to connect to an agent. If no input is received within 10 seconds, or an invalid digit is entered, the flow plays a closing announcement and disconnects.
I've now successfully tested live-answer confirmation, no-input handling, default voicemail and custom voicemail scenarios.
This doesn't change AMD accuracy, but it provides an additional safeguard against voicemail calls reaching agents.
Hope this helps anyone implementing something similar!
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 10-20-2026 02:43
From: Phaneendra Avatapalli
Subject: Customer First Callbacks
Hi everyone,
I've been testing Customer First callbacks with Answering Machine Detection (AMD) and noticed some inconsistent behaviour.
When using the carrier's default voicemail greeting, Genesys correctly detects the answering machine and transfers the call to the configured voicemail flow.
However, when using a custom-recorded voicemail greeting, the callback is presented to an agent instead. The agent can answer the interaction while the customer's voicemail continues recording the callback audio.
I'm aware there's a Hangup option for answering machine detection, but I'm interested in using Transfer to Flow to leave a voicemail message.
Has anyone tested this scenario with custom voicemail greetings? Is this expected AMD behaviour, or are there any recommendations for improving detection accuracy?
Thanks!
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------