Inaccurate Queue call distribution
When queue call distribution is set to Longest Idle, the logic appears to interpret an outbound call as "idle" or "longest idle" and sends the next inbound call to that agent despite others being idle for a longer period of time. Additionally, the system considers an agent as "longest idle" when their status changes from "Opt-out" to "Available." Perhaps the system assigns 'disconnecting from an outbound call' as moving from "Opt-out" to "Available." That would explain the behavior. Regardless of the cause, this results in uneven call distribution and makes it more difficult for agents to complete documentation of the first call before another call rings to them. I've increased our "Wrap-up Time" to help with the latter, but it still causes problems with workflow. In general, we prioritize availability over documentation when all agents are busy, so I can't simply extend Wrap-Up time to the maximum. The only workaround I have found is for agents to hit "Skip" so that the call goes to others, but agents don't know whether others are available when they make that choice. Are there any other settings which might alter this bug? Other workarounds? Is there somewhere I should submit this for consideration by developers? Thanks in advance!
Show less