|
|
|
Hey Damian,
Ok, but there doesn't seem to be any other way of doing it. Your suggestion of chaining in another auto-attendant was the first thing I tried. To make it work that way, an auto-attendant would need to have the ability to play it's prompt once and then immediately execute a specified action. Apart from the fact that the prompt is played 3 times and this can't currently be changed on a per auto-attendant basis, the only default-action on timeout currently possible is a transfer to another extension, which would force the user to define an extension in the dial-plan for every auto-attendant that needs to be jumped back to in this way. As far as I can tell, playing a prompt in response to a menu-choice and then returning to that menu can't be done in the current UI. Anyways, I'll post this to the list as well, as per your request. Grtz, Oliver Ok. From your response on the mailing-list, I gather that the easiest way of implementing this might be as an option in the existing auto-attendant that makes it play it's prompt once and then immediately execute a specified action. The other way of doing it would basically be what I already described when opening this issue: Adding it as a menu-action.
Contrary to what I said on the list, the option of making the prompt interruptable by DTMF should probably be selectable by the user. If interrupted, control should proceed as if the prompt had played out completely. "play once" option would be a REALLY NICE improvement for current AA implementation and a replacement for missing "play prompt action".
:D Is this on the Roadmap now or just hanging here ?
I think that "play once" workaround for this is implemented already - you can set Replay Count to 0 from the UI.
My inderstanding is it's kept open to track adding new action ("Play Prompt") for AutoAttendant without necessity of chaining AutoAttendants. There are many applications for a "Play Prompt" action, such as "Press 1 to get directions to our location" and other announcements a user would like to make to callers. Using a hierarchical AA construct for this seems overkill. Therefore, adding this as an action would make sense.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
I am pretty sure you can chain attendants (select extension of another attendant as an action of current attentdant) but maybe documentation and/or user interface needs updating to make it more obvious. Let's discuss it first and then we can open JIRA issue.