Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  ACW time for concurrent chats

    Posted 10-30-2025 09:00
    No replies, thread closed.

    We are sturggling with getting accurate AHT for concurrent interactions. We use ACW as optional, as we perform quite a lot of after call work and it's a valuable part of the AHT calculation for a good percentage of interactions.

    My understanding is that when a chat is "in focus" in Genesys, it shows as interacting in the timeline and the concurrent "out of focus" chat shows as on hold. If the agent switches chats, then the timeline reflects this.

    However, if the "in focus" chat is moved to ACW and the agent switches to the 2nd chat before completing  ACW, then the ACW timer on chat 1 is not paused. Nothing is shown on the time line in Chat 1, just an ever growing AHT

    The effect of this, is that we see some interactions with huge ACW times. 

    We are solving from a process perspective ,by asking agents to ensure ACW is completed before responding to chat 2,  but would love Genesys to pause the ACW timer if the interaction is out of focus. 

    Before requesting in Ideas portal, I wanted to check if our understanding was correct.


    #Reporting/Analytics

    ------------------------------
    Patrick Redford
    Product Owner: Service Center Solution (Genesys Cloud CX)
    ------------------------------


  • 2.  RE: ACW time for concurrent chats
    Best Answer

    Posted 10-30-2025 15:02
    No replies, thread closed.

    Hello Patrick,

    To my knowledge I believe that is working as intended. If you would like to have further options to customize how the times are calculated, you would need to request this via the Product Ideas Lab



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: ACW time for concurrent chats

    Posted 30 days ago
    No replies, thread closed.

    Hi Patrick 
    We have exactly the same issue but with Voice interactions.

    An agent can in ACW do a new outbound call and if the agent does not kill the ACW from the original call the ACW keeps council and the AHT blows out.

    We ask agents to follow the process, but when you have a few thousand agents there are always going to be agents who forget.

    There is no setting in Genesys to stop this currently to the best of my knowledge??

    This is a massive issue as it makes capacity planning very difficult because we are not measuring AHT correctly.



    ------------------------------
    Adrian Cunningham
    Head of Workforce Optimisation & Care Platform Operations
    ------------------------------