As far as I understand - next call will get next available agent. I understand, completely pointless answer. But look, the system does not have plans. If you think about it - it cannot have plans, because the situation can change any millisecond. Next agent will be determined when the call need to be assigned.
If you think about queuing and agent assignment algorithmically you will notice that actually there are two possible situations - "little load" or "heavy load".
In "little load" scenario, there is no call queue, there are lots of free agents (at least 2). In this case the call is agent picking initiator. The call will "usually" go to "longest available". You can have field showing "longest time in ready state". The agent at the top will be the one.
In "heavy load", the are calls in the queue and no available agents. In this case it is inconvenient to go through all the calls in the queue and ask "is there agent for me?" - the agent becomes "picking initiator". In this case it is like agent is picking suitable call for him. This way time spent looking for a call is not that dependant on queue depth. But, because of this - you cannot have prediction. Agent picking is just reaction to "agent ready" event.
Sorry for long post. Hopefully this explains things. I didn't write CCX or CCE, but that's how I think they work. Hopefully somebody smarter than me can explain it better... or prove me wrong.
On my part, your long post is appreciated. Well, in Supervisor Desktop - you are able to see who the longest available is in a CSQ... do you think it's possible to have that information shown on a WallBoard?
Agreed, the system can change at any given moment... hmmm, in your heavy load explanation - maybe showing the availability of the agents would cause confusion.
None the less, I wonder if you can show the states of agents from Supervisor Desktop on a WallBoard.
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...