03-16-2017 12:34 PM - edited 03-14-2019 05:09 PM
UCCE 10.5 environment with integrated Egain and ICM picks the agent. 15 agents in a chat skill, 10 set to handle 3 chats at a time, 5 set to handle 2 chats at a time.
Sending the task (Chat) to a skill group in the ICM script. The problem is: agents set to handle 3 chats get all the chats until they are maxed out and then the agents set to handle 2 chats start getting chats.
I believe it should work as follows: with ICM picking the agent (IPTA), the chat should go to the LAA - Longest available Agent. Then when all agents have one chat, the longest available agent with only one chat should get the next chat.
Not understanding why.
Any thoughts here?
03-16-2017 05:32 PM
The problem is likely in either the Skill Group configuration in Skill Group Explorer and/or how you have it configured in the routing script. Can you post some screen shots?
03-29-2017 11:33 AM
03-30-2017 08:17 AM
Can you double click the Select node and screen shot the properties of it?
To be honest though, you really don't need the Select node... the Queue to Skill Group node routes to LAA by default
03-30-2017 11:32 AM
Yes I agree. Thanks Omar. It should be using LAA, however it seems to stack up some agents with all the chats and some get no chats.
03-30-2017 12:38 PM
Can you post a screen shot of the properties of the Select node?
04-14-2017 04:29 AM
04-14-2017 08:39 AM
What does your routing script look like?
04-14-2017 08:44 AM
Omar,
Its just a queue to skill group. We are not using LAA or select node.
Regards,
Das
04-14-2017 10:18 AM
Hi Omar,
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCur46587/?reffering_site=dumpcr
Do you think this Bug matches us , if yes is there any chance to overcome by an enhancement.
Regards,
Das
04-14-2017 11:09 AM
Wow... great find. I'm guessing this is fixed with an ES either on the WIM/EIM side or on the ICM side. 9.0(4) has a ton of Engineering Specials. I'd open a TAC case and go from there
04-14-2017 11:16 AM
Hi Omar,
Is there any workarounds to route chat/email to next agent instead of waiting for concurrent task limit to be reached.? do we have any settings in CIM or a script change can overcome this behavior? In stead of queue to skill group , do we have any chance to use any other nodes?
Regards,
Das
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide