- Joined
- Dec 20, 2017
- Messages
- 24
- Reaction score
- 6
Hey there! I am a little frustrated with queues right now. We have a lot of queues and have assigned the required agents into each queue.
Is there a way to do any one of the following:
1) Disallow ability for agents to log out of individual Queues. Agents don't have access to their ability to sign out of individual queues.
2) Just an all or nothing on/off Queue button that logs in/out of ALL queues (ignoring 'explicit' rules). Its very misleading when an agent can see the signed in blue 'Q' button but if they have explicitly logged out in the past of individual queues they won't realize that -unless they remember to scroll through all the queues to check.
3) Any other method or fix that can prevent me from having to scroll through all of our queues each day multiple times to make sure everyone is explicitly logged in (in case someone forgets to sign back in to a queue, mistakingly signs out of a queue, or has intentionally signed out of a queue to get out of taking calls).
Its kind of frustrating for me as the designer of our call flow. I put agents into queues because I want them to answer calls in those queues. With more users it gets harder and harder to ensure that everyone is 'explicitly' logged in to all of their individual queues. I get why some companies would want this behaviour for their employees but this complexity should be an option not the default.
If this availability system is hard for me to understand (a lot of time spent scanning these forums) many of our agents are going to have a really hard time understanding it too. Which makes the complexity useless if people don't understand how it all works together.
I just think there are too many moving parts for the average user:
- User Status (which can or cannot be tied to Global Queue status)
- Global Queue Status
- Individual Explicit Queue Status
it would be nice if there was the option for just using 1 of these; User status:
Available = Available Everywhere
Unavailable = Unavailable everywhere.
Let the admin define where 'everywhere' is for each user, not the user. That would be way easier to explain to users and to manage.
Thanks for your time!
-Levi
Is there a way to do any one of the following:
1) Disallow ability for agents to log out of individual Queues. Agents don't have access to their ability to sign out of individual queues.
2) Just an all or nothing on/off Queue button that logs in/out of ALL queues (ignoring 'explicit' rules). Its very misleading when an agent can see the signed in blue 'Q' button but if they have explicitly logged out in the past of individual queues they won't realize that -unless they remember to scroll through all the queues to check.
3) Any other method or fix that can prevent me from having to scroll through all of our queues each day multiple times to make sure everyone is explicitly logged in (in case someone forgets to sign back in to a queue, mistakingly signs out of a queue, or has intentionally signed out of a queue to get out of taking calls).
Its kind of frustrating for me as the designer of our call flow. I put agents into queues because I want them to answer calls in those queues. With more users it gets harder and harder to ensure that everyone is 'explicitly' logged in to all of their individual queues. I get why some companies would want this behaviour for their employees but this complexity should be an option not the default.
If this availability system is hard for me to understand (a lot of time spent scanning these forums) many of our agents are going to have a really hard time understanding it too. Which makes the complexity useless if people don't understand how it all works together.
I just think there are too many moving parts for the average user:
- User Status (which can or cannot be tied to Global Queue status)
- Global Queue Status
- Individual Explicit Queue Status
it would be nice if there was the option for just using 1 of these; User status:
Available = Available Everywhere
Unavailable = Unavailable everywhere.
Let the admin define where 'everywhere' is for each user, not the user. That would be way easier to explain to users and to manage.
Thanks for your time!
-Levi