- Joined
- Sep 19, 2015
- Messages
- 106
- Reaction score
- 19
Some of my co-workers experienced the issue, that they where not logged into our main queue after the update to SP2 (i might be wrong about the first time of occuring), even if their clients status button (the Q-Button) was active.
Changing the status via the Client won't help at all.
Only logging the Clients in via the Q-Manager would work.
So basicly, the Q-Manager login and the client login seem to be two different things now, where the Q-Manager status always overrides the client setting.
The client setting can be automated by some rules, where the q-manager setting can not.
This causes a lack of control of every agent and turns the q-manager setting option into a double edged sword.
Sure, every user (at least on a windows machine >> e.g. won't work for my mobile android users) could just open the manager window and log themselves on. But this is not what user convenience is about, is it? Also, the Q-Status Button would still be no valid indicator.
Changing the status via the Client won't help at all.
Only logging the Clients in via the Q-Manager would work.
So basicly, the Q-Manager login and the client login seem to be two different things now, where the Q-Manager status always overrides the client setting.
The client setting can be automated by some rules, where the q-manager setting can not.
This causes a lack of control of every agent and turns the q-manager setting option into a double edged sword.
Sure, every user (at least on a windows machine >> e.g. won't work for my mobile android users) could just open the manager window and log themselves on. But this is not what user convenience is about, is it? Also, the Q-Status Button would still be no valid indicator.
