cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
716
Views
0
Helpful
3
Replies
Highlighted
Beginner

Agent State issues with conferencing active calls

We have a UCCE call center that has a challenging workflow.  The agents take inbound calls to their ACD lines, then from that line, they will make an outbound call to a doc's cell phone.  If the doc answers, they conference the calls together and all is well.  If the doc does not answer, they will leave their private number for call back.  When the doc calls back, they are currently parking that call, then going back to the ACD line and conferencing in the parked call.  

 

If they try to conference using the "Active Calls" feature while on an active ACD call, the agent state will stick at "On Hold" and when the call is completed, the phone must be restarted to release the agent from that state. 

 

If they try to conference using "Active Calls" while on a non ACD line and conference in an ACD call, the agent state sticks at "On Hold" but will release back to Ready when the call is complete.  This would skew their CUIC reporting. 

 

 

Any thoughts? 

 

UCCE 11.5.x

CVP 11.5

Finesse 11.6 (stock w/Live Data)

UCM 11.5

8811 phones

 

Everyone's tags (3)
3 REPLIES 3
Highlighted
Cisco Employee

Re: Agent State issues with conferencing active calls

Hi,

 

"the phone must be restarted to release the agent from that state." sounds to be an issue to me. I would suggest opening a TAC case for that.

 

Other than the above, is your issue the fact that the agent state is stuck in "On hold"?

 

Thanx,

Denise

Highlighted
Beginner

Re: Agent State issues with conferencing active calls

Correct, with the agent state showing as "On Hold" it would create inaccuracies in their reporting.   

Highlighted
Cisco Employee

Re: Agent State issues with conferencing active calls

If an agent is actively on a call, they should never be in "hold" state. The only time they should ever be in hold is when they have calls but are in "hold" state for each one. From your description, it doesn't sound like that is the case, so I would definitely go up the TAC route.

 

This widget could not be displayed.