The issue we are having is either staff at the end of their shift get slammed when using "Fewest Sent to Agent " or when we use "Fewest Answered" those coming onto a shift get slammed. The real issu...
Hi jstrittmatter, currently I don't have a timeline for implementation of this feature.
Any progress on the Ring Strategies and the rolling 24 hour period?
Early this morning we had the following scenario happen:
Agent1 - worked a 10a - 6p shift on 10/16/2024 and then logged back into the queue from 12:03 am - 2:00 am this moring, 10/17/2024.Agent2 - logged in at 12:00 am - 7:00 am this morning, 10/17/2024.
Agent2 received all calls between 12:00 am - 2:00 am. There was one call at 1:11 am that waited in the queue for 50 seconds. Our connect timeout is 20 seconds so that call should have rolled over to Agent1 but it did not and it kept ringing Agent2 until she answered it.
The system should not be ringing the same agent after the first connect timeout unless we only have one agent in the queue. I understand the system ringing Agent2 for all new calls but once the call times out after 20 seconds it should ring a different agent, using the same ring strategy but ignoring Agent2 since the call timed out.
Hopefully there can be a solution to this issue sooner than later.
I've checked with the team, additional ring strategies are coming in Contact Center, as well as improvements. Having the current ring strategies consider the agent shift is being considered, but it's currently not on the timeline. We will continue to share your interest with the team. Thanks for sharing your use case, it's very helpful.
