I know of several ways to do this but I don't like any of them for numerous reasons.
I do not have any licensed ports for intelligent Queue
I do have access to RAD ports via EMEM
[ul]
[li]I don't like creating ACD Paths in front of ACD paths due to the way it clutters reports.[/li]
[li]I don't like having a Phantom ACD group as the primary group that overflows to the secondary main group as I've seen calls get stuck on the phantom group when no agents are available in the secondary[/li]
[li]I know I can have rads associated with Hunt Groups and Ring Groups but that needs an actual device to queue against to work.[/li]
[/ul]
All these just feel Kludgy. Why can't Mitel add a pre-announce function that doesn't cost $1000 per port.
To complicate things, all of this needs to integrate with Voicemail as dial out of queue and Night directly.
**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.
I do not have any licensed ports for intelligent Queue
I do have access to RAD ports via EMEM
[ul]
[li]I don't like creating ACD Paths in front of ACD paths due to the way it clutters reports.[/li]
[li]I don't like having a Phantom ACD group as the primary group that overflows to the secondary main group as I've seen calls get stuck on the phantom group when no agents are available in the secondary[/li]
[li]I know I can have rads associated with Hunt Groups and Ring Groups but that needs an actual device to queue against to work.[/li]
[/ul]
All these just feel Kludgy. Why can't Mitel add a pre-announce function that doesn't cost $1000 per port.
To complicate things, all of this needs to integrate with Voicemail as dial out of queue and Night directly.
**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.