There are two scenarios when determining agent selection and Skill Competency Ratings only influence one of them (the one you're not facing). Let's recap:
There are multiple agents waiting in a Ready state and a single call arrives in a CSQ (i.e. surplus of agents).
This is where Skill Competency Ratings apply.
The Most Skilled agent in the CSQ the caller was placed into will be offered the call first. If multiple agents have the same Competency Rating, it will offer the agent who's been in a Ready state the longest. It proceeds to the next lower skill level only after exhausting all agents at the level.
There are multiple calls waiting, possibly across multiple CSQs, and a single agent becomes available (i.e. a shortage of agents).
Skill Competency Ratings play *no* role in this scenario.
The agent who becomes available will simply be offered the longest waiting call - at the highest priority - across all CSQs they are skilled in.
If the caller has been prioritized within the AEF script, this is a strict priority across all other callers waiting. Neither the agent nor the CSQ itself can be prioritized, only a caller.
So, if you want Bob to only receive HelpDesk_CSQ calls when there are no calls waiting in Support_CSQ then you'll need to define this inside the script and use simultaneous queueing. Here's an example:
Select Resource (HelpDesk_CSQ) --Connected ----Goto End --Queued ----Get Reporting Statistic supportCallersWaiting = Contacts Waiting in Support_CSQ ----If (supportCallersWaiting > 0) ------True --------[normal queued loop goes here] ------False --------Select Resource (Support_CSQ) ----------Connected ------------Goto End ----------Queued ------------[second queued loop here. be careful to keep your queued loops separate.]
In this scenario, it will put the caller into both CSQs if there are no callers waiting in Support_CSQ.
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.