MillTechNet
Technical User
Hi, can anyone shed some light on this problem please?
I have and ACD path that overflows to *410 which is a NameTag to a Multi-level Auto Attendant (410). This MLAA has one level of options. Each of these options places the caller into a new ACD path. This all works great with agents logged into the second ACD paths.
Now, what I need is that when the second set of ACD paths is entered, if there are no agents logged in then it needs to send the caller to a new MLAA (NameTag *400). This works fine if I start the call from a specific secondary ACD path, I get transferred to the second MLAA and on from there. However, If I try calling the original ACD path, I get all the way through the first MLAA, into the secondary ACD path, it hesitates then I get sent back to the first MLAA.
Any ideas how to break out of this so I can get to the second MLAA?
I have and ACD path that overflows to *410 which is a NameTag to a Multi-level Auto Attendant (410). This MLAA has one level of options. Each of these options places the caller into a new ACD path. This all works great with agents logged into the second ACD paths.
Now, what I need is that when the second set of ACD paths is entered, if there are no agents logged in then it needs to send the caller to a new MLAA (NameTag *400). This works fine if I start the call from a specific secondary ACD path, I get transferred to the second MLAA and on from there. However, If I try calling the original ACD path, I get all the way through the first MLAA, into the secondary ACD path, it hesitates then I get sent back to the first MLAA.
Any ideas how to break out of this so I can get to the second MLAA?