Settings and activity
3 results found
-
7 votes
An error occurred while saving the comment 
David
supported this idea
·
-
107 votes
An error occurred while saving the comment David
commented
Fleshing this out a little bit further, I can currently log an agent off. But, I cannot log an agent on to the CX System. I would also like to change the unavailable/available state of the agent to any of the available choices (Examples: Lunch, Away, Available, etc)
David
supported this idea
·
-
12 votes
An error occurred while saving the comment David
commented
The issue of headset signaling/controls not working with RingCX via Chrome browser is not limited to wired headsets. The bugs exists for wired and wireless headsets (blue tooth or DECT). Why would headset signaling/control work properly on MVP and not CX? The main difference we see is the use of Chrome for CX. MVP using your proprietary client works fine with most headsets we tested. Only CX is having a problem. Our company does not have desktop techs or a Dev Ops team. We are only observing symptoms. Hope this helps.
David
supported this idea
·
A straight round robin without any modifying math would work well for us as we have work tasks as un-available status which agents should not be effectively penalized for by giving them incoming calls ahead of staff who have not been working on such tasks.