- Joined
- Sep 9, 2024
- Messages
- 2
- Reaction score
- 0
I have a feature request regarding the polling logic for agents who are logged into multiple queues simultaneously (e.g., Queue A and Queue B). We are currently using the "Longest Idle" polling strategy.
The Scenario:
We need the "Longest Idle" strategy to consider the agent's global activity, not just their activity per specific queue.
The Scenario:
- An agent is logged into both Queue A and Queue B.
- The agent receives and answers a call from Queue A.
- While talking on Queue A, the agent's idle timer in Queue B continues to increase (or remains at a high value indicating they haven't taken a call from Queue B specifically).
- As soon as the agent finishes the call in Queue A, the system immediately routes a call from Queue B to them. This happens because the system sees the agent as "Longest Idle" in the context of Queue B, ignoring their recent activity in Queue A.
We need the "Longest Idle" strategy to consider the agent's global activity, not just their activity per specific queue.
Upvote
5