Genesys Cloud - Main

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Agent call to Queue A and blind transfer the call to Queue B - two queues waiting for each other and Total Queue time is bigger than Conversation duration

  • 1.  Agent call to Queue A and blind transfer the call to Queue B - two queues waiting for each other and Total Queue time is bigger than Conversation duration

    Posted 12 hours ago

    Hey all

    I encounter a weird situation and want to share with you so it might help someone

    Customer share Interaction that looks weird:

    I figure that the Agent Called Queue A and was waiting there, then he blind transfer the call to Queue B, so he is no longer part of the conversation and both Queues wait for each other.

    This is so horrible mishandling from the Agent side, and its can cause many anomalies, 
    the Total Queue time will be almost double than to Conversation duration time, and in my case when Agents tried to answer this call, they got an error, maybe because its Org with physical Edges and physical phones, when i replicate it in BYOC Cloud with WebRTC I was able to answer

    Total Queue bigger than conversation duration:


    maybe you will find this info useful

    Best regards


    #Implementation
    #Reporting/Analytics
    #Routing(ACD/IVR)
    #System/PlatformAdministration
    #Other

    ------------------------------
    Shahar Leonard
    Genesys Cloud Professional Certified
    ------------------------------


  • 2.  RE: Agent call to Queue A and blind transfer the call to Queue B - two queues waiting for each other and Total Queue time is bigger than Conversation duration

    Posted 7 hours ago

    Hi Shahar

    -

    I looked at several organizations and didn't find that scenario.

    If this is a "normal" scenario in your organization, I suggest opening a support ticket with Genesys to check.

    -

    I could be wrong, but I BELIEVE this shouldn't happen.
    "Conversation duration" is the calculation of the end - start time of the interaction.

    And the "total queue" is the time spent in the queue (whether it's 1, 2, or 3...etc).

    -

    I may be completely wrong, but considering the metrics and how they are calculated, it doesn't make sense for the total queue to be greater than the conversation duration, since it encompasses the entire "life" of the interaction, i.e., IVR, queue, conversation, ACW, etc.



    ------------------------------
    Kaio Oliveira
    GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM

    PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
    ------------------------------



  • 3.  RE: Agent call to Queue A and blind transfer the call to Queue B - two queues waiting for each other and Total Queue time is bigger than Conversation duration

    Posted 3 hours ago

    Hey @Shahar Leonard,

    I haven't seen this behavior before, but looking at the timeline it really looks like an unusual queue/transfer path.

    I would first try to understand if this was a one-time mishandling or if agents are commonly using blind transfers between queues in this way. If it is happening often, it may be worth reviewing the process with the agents, because this type of handling can create confusing timelines and strange reporting results.

    Also, if necessary, you can limit what agents are allowed to do with transfers through permissions. For example, you can control blind transfers by destination type, including blind transfers to queues.

    I agree with Kaio here: if this behavior is reproducible or if agents are getting errors when trying to answer these interactions, I would open a Customer Care case with the conversation ID and timestamps so Genesys can validate the backend behavior.



    ------------------------------
    Arthur Pereira Reinoldes
    ------------------------------



Related Content