MitelInMyBlood
Technical User
System 2K
SW: 34.2.5.3
Application: ACD2000 (aka ACDII)
What timer (in what form) determines how long to ring the agent's phone before auto-logout occurs causing the path to go into path-unavailable mode? I'm thinking it's the AGENT's CLOS but wanted to ask someone with more ACD experience than me.
The question has come up regarding the timing relationship between the first rad playing and the ringing call "timing out" and going to the Path Unavailable answer point (voice mail)
What is occurring is the last agent of the day is sometimes forgetting to log out and the first rad is playing (fully or partially) then the call expires & goes to VM with the caller becoming utterly confused. Obviously the 1st rad says one thing and the P/U answer point says something entirely different. The client does not want to change the rad message nor the P/U message so the onus is on me to:
1) make sure the first rad is never heard before auto-logout occurs and the call falls thru to the P/U answer point when an idle agent fails to answer.
2) minimize the number of rings the caller hears when the queue is full (before playing the 1st rad)
3) still allow the agent a "reasonable" amount of time to answer - ie, 3 rings (11 secs)
I'm thinking I need to squeeze the CFNA timer in the agent's cos, but am not confident that 2 rings will be enough.
Thoughts appreciated.
SW: 34.2.5.3
Application: ACD2000 (aka ACDII)
What timer (in what form) determines how long to ring the agent's phone before auto-logout occurs causing the path to go into path-unavailable mode? I'm thinking it's the AGENT's CLOS but wanted to ask someone with more ACD experience than me.
The question has come up regarding the timing relationship between the first rad playing and the ringing call "timing out" and going to the Path Unavailable answer point (voice mail)
What is occurring is the last agent of the day is sometimes forgetting to log out and the first rad is playing (fully or partially) then the call expires & goes to VM with the caller becoming utterly confused. Obviously the 1st rad says one thing and the P/U answer point says something entirely different. The client does not want to change the rad message nor the P/U message so the onus is on me to:
1) make sure the first rad is never heard before auto-logout occurs and the call falls thru to the P/U answer point when an idle agent fails to answer.
2) minimize the number of rings the caller hears when the queue is full (before playing the 1st rad)
3) still allow the agent a "reasonable" amount of time to answer - ie, 3 rings (11 secs)
I'm thinking I need to squeeze the CFNA timer in the agent's cos, but am not confident that 2 rings will be enough.
Thoughts appreciated.