Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ausername on March 03, 2015, 02:57:01 PM
-
Hello,
I'd love to implement a new functionality for our receptionist that would allow the callers to be given an option while they're waiting: option 1- stay in queue option 2- leave voicemail message.
Can I make this work with ACD paths and interflow going to a multi nodes voicemail?
example:
a caller would call in to the ACD path, if our receptionits are busy or are on a call, after waiting 20 seconds, the caller will hear the ACD path's recording 1 rad message. After waiting 20 more seconds, the caller would then hear ACD path's recording 2 message saying that we appreciate his patience. After 20 more seconds, the caller would be presented to a voicemail menu node greeting. If he selects option 1, he will be transfered to a voicemail. If he selects option 2, he goes back to the queue while keeping his priority number.
Is this possible?
Let me know!!
thanks!
-
What you're wanting is called "Path Interflow Dialing List".
It's setup in each queue, so after the options are played via a RAD, the caller can press the options from the Interflow list. This way they never actually leave the queue.
-
What you're wanting is called "Path Interflow Dialing List".
It's setup in each queue, so after the options are played via a RAD, the caller can press the options from the Interflow list. This way they never actually leave the queue.
NICE NICE!
Now, I see an ACD Path interflow dialing lists menu in the category of "ACD" within the mitel interface. In that menu, I'm able to configure path interflow dialing list numbers that set "redirection digits". So far so good, I would configure Path Interflow Dialing list #1, Digit 1 - redirection digit: the voicemail would be here.
But now, what about the option of staying in the queue? Is that configured through a redirection digit in the menu I was refering or is that done by indicating to the caller to "stay on the line and an agent will be with them shortly" ?
-
or is that done by indicating to the caller to "stay on the line and an agent will be with them shortly" ?
Correct. By the caller not performing any action, they'll remain in the queue and in their position.
-
or is that done by indicating to the caller to "stay on the line and an agent will be with them shortly" ?
Correct. By the caller not performing any action, they'll remain in the queue and in their position.
thanks a lot :) Working on this now.
-
or is that done by indicating to the caller to "stay on the line and an agent will be with them shortly" ?
Correct. By the caller not performing any action, they'll remain in the queue and in their position.
thanks a lot :) Working on this now.
I have everything set up and running, thanks again!
-
or is that done by indicating to the caller to "stay on the line and an agent will be with them shortly" ?
Correct. By the caller not performing any action, they'll remain in the queue and in their position.
thanks a lot :) Working on this now.
I have everything set up and running, thanks again!
Here's the challenge that I'm currently facing:
Once a caller leaves a message by pressing 1 ( ACD interflow dialing list - digit 1 in the ACD path recording 2 interflow list) the message will go to a voicemail box. The voicemail box isn't associated with a physical phone, it's a voicemail mailbox type extension and its voicemail mailbox number is "3". 3 is also a hunt group type "nametag". This allows me to view "3" in the call rerouting table and change the day/N1/N2 values to our voicemail huntgroup. This allows me to use "3" as the ACD path interflow dialing list number.
Problem is, the receptionist won't know when a new message comes in the mailbox because the "message waiting indication" key feature doesn't allow me to use the value "3" in the field "Button directory number" because it's being used elsewhere it says.
I'm sure there's a proper way to do this, wondering what am I doing wrong.
-
Right, you can't have an MWI for a Hunt Group.
Three ways to fix this that I know of. In all three cases, you'll need to delete the hunt group.
1. Burn an IP license, and create an actual extension of 3. Then set your Call Routing as needed.
2. Waste an analog port, and create it as an extension 3, with a voicemail box. Then set your Call Routing as needed.
3. On a 5224/5324/5330/5430 somewhere on your system, program the extension to have a PKM. Add a single line key of extension 3 to this "phantom" PKM. Then set your Call Routing as needed.
After any of the above 3, you should be able to add your MWI button to the receptionist.
-
Right, you can't have an MWI for a Hunt Group.
Three ways to fix this that I know of. In all three cases, you'll need to delete the hunt group.
1. Burn an IP license, and create an actual extension of 3. Then set your Call Routing as needed.
2. Waste an analog port, and create it as an extension 3, with a voicemail box. Then set your Call Routing as needed.
3. On a 5224/5324/5330/5430 somewhere on your system, program the extension to have a PKM. Add a single line key of extension 3 to this "phantom" PKM. Then set your Call Routing as needed.
After any of the above 3, you should be able to add your MWI button to the receptionist.
thanks alot!
I opted for option #1 as this will be a permanent situation. Did some testing, everything working smoothly!
-
I think you could use a trusted extension for this also and not consume any license
-
I think you could use a trusted extension for this also and not consume any license
Interesting, I'll have to remember to try that.
-
I think you could use a trusted extension for this also and not consume any license
yup, this works! It free'd up my license.
-
Is there a timer on the length of a RAD message?
I have a billingual speech that I've recorded and when I listen back to it, it cuts short at the end
-
Is there a timer on the length of a RAD message?
I have a billingual speech that I've recorded and when I listen back to it, it cuts short at the end
Yes, 2 of them in the RAD COS. Answer Plus Expected Off-hook Timer and Answer Plus Message Length Timer.
With Off-hook needing to be slightly longer than Message Length.
-
Path Unavailable Answer Point Directory Number : how does this work?
In the ACD path, I've configured this field to be my personal extension. In call rerouting, the values for Day/N1/N2 for my extension are set to forward to the voicemail huntgroup for testing purposes. If I call my extension from an outside phone line, it goes straight to my voicemail. When I call the ACD and no agents are logged in, I would have thought that the calls would have been forwarded to my voicemail, but they aren't. Instead, they are fowarded to another greeting message which isn't my voicemail.
Any ideas why the calls would not be forwarded to my voicemail?
-
-
-
-
-
Figured out the problem.
forget my last post.
-
update on my current setup:
I have an ACD path that plays RAD recordings and I do make use of the ACD path interflow dialing list that allows a caller to press 1 to leave a message(gets sent to the voicemail of a phone type: trusted)
I have a Message Waiting Indicator key configured on a phone that is able to log into the ACD queue. This key gives access to the voicemail box that the callers use when they make use of the interflow dialing list number.
My ACD path's directory number has a voicemail configured with that same number. This allows me to configure the field "Path Unavailable Answer Point Directory Number :" in the ACD path with the value of our voicemail hunt group. If none of the receptionist are logged in the ACD queue to take calls, the Path Unavailable Answer Point will transfer the call to the voicemail hunt group and I have a voicemail that has the same number of the ACD path.
So essantially, there are 2 ways a caller can leave us a voicemail:
1- via the interflow dialing list
2- if no users are logged in the ACD path
Both methods of receiving voicemails don't use the same mailbox and only one of them allows me to configure a Message Waiting Indication key on a mitel phone.
Can I have all the voicemail messages go to the same mailbox preferably accessible via the Message Waiting Indicator key?
-
Do you have embedded voicemail or a NuPoint?
Sent from my iPhone using Tapatalk
-
Do you have embedded voicemail or a NuPoint?
Embedded I believe.
Simply because I've never heard of NuPoint and if I look here: http://mitel-tr.com/voicemail.html this seems to go hand in hand with our web interface options
-
and in our liscenses: system capacity window, under messaging it says:
Embedded voice mail
-
Ok, to do this you'll need to create a nametag type hunt group, the same as the voicemail box you want to use. Only put a * in front of it. I think you said it was 3 before, so make the hunt group *3.
Then call reroute that always to voicemail.
Finally, make the path unavailable point *3.
Sent from my iPhone using Tapatalk
-
Ok, to do this you'll need to create a nametag type hunt group, the same as the voicemail box you want to use. Only put a * in front of it. I think you said it was 3 before, so make the hunt group *3.
Then call reroute that always to voicemail.
Finally, make the path unavailable point *3.
This has worked on the first try and makes my whole acd path system much more professional as all voicemail go to the same mailbox and the messages are accessible via the Message Waiting Indicator key. Very nice!
I'm trying to research information about the * infront of the hunt group and what it does in the system. What should I be looking for?
-
I can't tell you of any real resources that give much detail into it. I've always been told its just a known trick. Back in the day it was the way to create the ability for people to transfer a caller directly into a users embedded voicemail box. So you'd end up with a *Ext Hunt Group for everyone in the system, all call rerouted always to voicemail.
The way it works, to my understanding anyway, is that voicemail will see the * in the digit string and essentially escape from the mailbox of the device that routed the call to voicemail, and then evaluate the EXT portion, and route the caller to that voicemail box instead.