We have some odd things happening with our main ACD queue. Occasionally operators who should be next in the queue to receive calls are skipped by the system.
The queue has been looked at by our SP and by ourselves and there are not any problems with the set up. But still occasionally the next operator in the queue does not receive the next call.
We wondered if we found out why this was happening.
Our operators use the quick disconnect on their headsets. If a call is forced to them by the queue when they are disconnected the set will "beep" them. We noticed visually that one of our operators ended a call that was waiting for him to reconnect before he did reconnect his headset. But it did not appear in the call logger.
I have checked the set up of the RDB and the FTR, and they apparently set up correctly for receiving information about abandoned calls. It is allowed on per set basis for the operator in question.
Does any one have any ideas or experience of CDR on ACD's to help configure this (if it is possible)?
The queue has been looked at by our SP and by ourselves and there are not any problems with the set up. But still occasionally the next operator in the queue does not receive the next call.
We wondered if we found out why this was happening.
Our operators use the quick disconnect on their headsets. If a call is forced to them by the queue when they are disconnected the set will "beep" them. We noticed visually that one of our operators ended a call that was waiting for him to reconnect before he did reconnect his headset. But it did not appear in the call logger.
I have checked the set up of the RDB and the FTR, and they apparently set up correctly for receiving information about abandoned calls. It is allowed on per set basis for the operator in question.
Does any one have any ideas or experience of CDR on ACD's to help configure this (if it is possible)?