Genesys Cloud - Main

 View Only

Sign Up

Expand all | Collapse all

Customer First Callbacks

  • 1.  Customer First Callbacks

    Posted 09-21-2026 15:53

    New Feature: Agent Reservation for Customer First Callbacks

    We're expanding Agent Reservation capabilities for Customer First Callbacks (CFC), giving organizations more flexibility in how an agent is secured before a callback is placed.
    With this enhancement, administrators can configure Customer First Callbacks to reserve the next eligible agent before the system dials the customer. While reserved, the agent is held for the callback and is not assigned other interactions. This helps reduce the time customers may spend waiting for an agent after answering a callback.
    This builds on our existing Agent Reservation with Ownership capability, which reserves a specific agent for an Agent-Owned Customer First Callback.
    With these capabilities, organizations can support two different reservation models:
    • Agent Reservation with Ownership (Released earlier this year) : When a callback is owned by a specific agent, Genesys Cloud reserves that agent before dialing the customer. This is designed for use cases where continuity with a particular agent is important.
    • Agent Reservation without Ownership (THIS FEATURE): When ownership is not required, Genesys Cloud reserves the next eligible agent before dialing the customer. This provides the benefits of pre-dial reservation while allowing Genesys Cloud routing to determine which agent should handle the callback.
    Configuration
    Administrators can enable Agent Reservation for Customer First Callbacks through the queue configuration. When enabled, Genesys Cloud attempts to reserve an eligible agent before the system dials a Customer First Callback associated with that queue.
    For Agent-Owned callbacks, Agent Ownership takes precedence over the queue's Agent Reservation setting. Genesys Cloud reserves the owned agent before dialing. If Agent Ownership expires, the configured Agent Reservation setting is then used to determine how the callback is delivered.
    Key benefits:
    • Reduced customer wait after answer: Reserving an agent before dialing helps minimize the time between the customer answering and being connected to an agent.
    • Flexible callback delivery: Organizations can use a specific owned agent when continuity is required or allow Genesys Cloud to reserve the next eligible agent.
    • Improved high-touch callback experiences: Support callback use cases where securing agent capacity before contacting the customer is important.
    • Efficient agent reservation: Agents are reserved as part of callback delivery and released when the callback connects, the attempt is unsuccessful, or the reservation otherwise ends.
    We will share additional details, including availability, as we get closer to General Availability. Stay tuned!

    #Outbound
    #Roadmap/NewFeatures

    ------------------------------
    Rini Rajan
    Staff Cloud Product Manager
    Genesys - Employees
    ------------------------------


  • 2.  RE: Customer First Callbacks

    Posted 09-22-2026 09:09

    Hi Rini,

    What happens if an agent is successfully reserved but the customer does not answer the callback for the customer first callback scenario? Is the agent immediately released, and are there any configurable timeout settings associated with the reservation period?


    ------------------------------
    Thanks!
    Ganesh S
    ------------------------------



  • 3.  RE: Customer First Callbacks

    Posted 09-22-2026 16:40

    Hi Ganesh,

    If an agent is successfully reserved but the callback does not result in a customer connection, the reservation is released once the callback attempt reaches an unsuccessful outcome.

    Similarly, if the customer answers but disconnects before being connected to the reserved agent, the reservation is released and the agent becomes available for other interactions.

    We also have an internal reservation timeout that provides an additional safeguard to prevent an agent from remaining reserved if the normal release process does not occur. 

    If the callback is eligible for a retry, a new agent reservation is established before the next callback attempt is dispatched.



    ------------------------------
    Rini Rajan
    Staff Cloud Product Manager
    Genesys - Employees
    ------------------------------



  • 4.  RE: Customer First Callbacks

    Posted 09-22-2026 10:27

    Rini Rajan waiting for this feature thank you for sharing.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 5.  RE: Customer First Callbacks

    Posted 09-22-2026 10:34
    Thanks for sharing this update! Agent Reservation for Customer First Callbacks is a great enhancement that should help reduce customer wait time after answering while providing more flexibility in callback routing. Looking forward to seeing this available in General Availability!


    ------------------------------
    Francis Guo
    ------------------------------



  • 6.  RE: Customer First Callbacks

    Posted 09-22-2026 11:35

    Hi Rini, thank you for sharing!



    ------------------------------
    Erika Giraldo
    Consultant
    ------------------------------



  • 7.  RE: Customer First Callbacks

    Posted 09-22-2026 14:42

    Thanks for sharing.

    What's the difference between Agent First call backs and Customer First with Agent Reservation?

    I understand that Agent First means that the agent is the one that initiates the callback to the customer, but when Agent First is used with the "Automatically start and end callbacks" enabled, what are the differences between the two? They both accomplish the same thing that neither the agent or the customer should have to wait.



    ------------------------------
    Levy
    Communications Manager
    ------------------------------



  • 8.  RE: Customer First Callbacks

    Posted 09-22-2026 16:45

    Great point Levy. 

    Both Agent First Callback with Automatically start and end callbacks and Customer First Callback with Agent Reservation help reduce wait time by having agent capacity available before connecting the customer. The key difference is how the outbound callback attempt is managed.

    With Agent First Callback, the callback is first assigned to an agent and the customer call is then initiated.

    With Customer First Callback with Agent Reservation, an eligible agent is reserved while Genesys Cloud manages the outbound attempt. The system uses call progress detection to determine the outcome of the attempt, rather than requiring the agent to listen to the dialing process or make decisions based on what occurs. This provides consistent handling of outcomes across the agent pool.

    For unsuccessful attempts, CFC can also manage retries based on configured routing and retry rules, releasing the reserved agent between attempts as appropriate.

    This combines the benefit of having agent capacity secured before dialing with the automated call detection, consistent outcome handling, and retry capabilities of the Customer First Callback model.



    ------------------------------
    Rini Rajan
    Staff Cloud Product Manager
    Genesys - Employees
    ------------------------------



  • 9.  RE: Customer First Callbacks

    Posted 10-09-2026 17:26

    Thanks for the update. Are you able to share admin configuration screenshots and / or functional video for this new feature so we can train both admins and agents?



    ------------------------------
    Darshan
    ------------------------------



  • 10.  RE: Customer First Callbacks

    Posted 29 days ago

    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
    ------------------------------



  • 11.  RE: Customer First Callbacks

    Posted 28 days ago

    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
    ------------------------------