One of the biggest misconceptions about ACD is the "Agent available the longest". Most people think that this means the person who logged in first should get the call first but in reality, what is used in the calculation is the "Time since last interaction".
So make this a bit more clear, we can use the following example:
Agent A receives an interaction at 4:00 PM on Day 1.
Agent B receives an interaction at 4:50 PM on Day 1.
-- New Day --
Agent B logs in at 8:00 AM on Day 2.
Agent A logs in at 8:30 AM on Day 2.
Normally you would assume that since Agent B logged in first, they'd be the first to receive an interaction. However, because the calculation utilizes "Time since last interaction" as the value, we would actually expect Agent A to receive the call since Agent B has received an interaction more recently.
Ultimately the best way to determine why an interaction is going to a specific agent is to turn up ACD Tracing to 60, with the subtopics of ACD and Selection to 80.
------------------------------
Tyler Hammer
Associate Software Engineer - Genesys
------------------------------
Original Message:
Sent: 09-23-2019 10:54
From: Rahul C Tyagi
Subject: Call is not going to longest available agent
Hi All,
I have custom work-group and I am transferring the call to this work-group so that if agents are available on this work-group will receive the call.
While testing this login, my call is going to that agent who is in available/ready state from short time. Ideally call should go to that agent who is in available/ready state from longer time.
Any assistance on this would be really appreciable.
Thanks.
#Routing(ACD/IVR)
------------------------------
Rahul C Tyagi
Accenture India
------------------------------