I have a IPCC Express (CRS 3.5(1)) implementation together with CCM 4.0(1) cluster.
All works fine for > 1 year now, but I have one question from the business that I could not answer, and I can't seem to find the answer anywhere online.
Business asked me if it would be possible to send a pop-up alert to the agent's computer if they are not ready for a certain amount of time.
The reason for this is that within the callcenter agent;s sometimes have to leave their space and forget to put their agent desktop to work or not ready. Since they are ready in the system they can get a call routed, which put's them in reserved, then after 10 seconds the system will tray the next agent because of the no answer and will set the agent to "not ready" (this makes sense, of course, and is the system default). Upon return at their desk the only indication they have is the missed call, which should trigger the agent to check their status, but get's forgotten sometimes.
Rather then diciplinairy measurements we look to implement the above mentioned to prevent agents from forgetting to put theirself on ready.
I realize this is not possible with IPCC Express as a standard option, which is the very reason why I post this in the developer forum.
Allthough your tip is good, it is not exactly what I am looking for, as this will show up on all agents. I only want to show a pop-up on an agent desktop if that particular agent is not ready for x minutes.
I had a similar request and never found a resolution. Is it possible to do something like light the MWI if an agnet is unavailable for a certain amount of time. This type of feature would also be handy for CMAC users as the online/offline indicator is somewhat off to the side of the screen and is easily missed if the agent isn't looking for it.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.