Filter
Top Products
Chapter 7: Auto Attendant Configuration
94 AltiWare ACM 5.1 Administration Manual
record custom phrases, use pre-recorded phrases and use professionally recorded
phrases.
Example: AA Planning
Adding Auto Attendants
The first 16 AAs are provided with the menus blank. You can edit these as described in
“Editing Auto Attendants” on page 95. You don’t need to add a new AA if you’re going to
use 16 or fewer.
Auto Attendant ID: 100, Phrase 10
Main Menu for XYZ Office
Digit Meaning Action
1 Reserved
for
Extensions
(no
prompts)
Collect
Extension
2 Collect
Extension
3 Collect
Extension
4 Express
Support
Expand Tree
(No. 110)
5 Sales Expand Tree
(No. 120)
6 Technical
Support
Expand Tree
(No. 130)
7 Phone FAQs Expand Tree
(No. 140)
8
9
0 Operator To Operator
Auto Attendant ID: 110, Phrase 20
Express Support
Digit Meaning Action
1 Installation Call Extension
(Workgroup 350)
2 Board Support Call Extension
(Workgroup 360)
3 Version 5
Support
Call Extension
(Workgroup 370)
4 Version 6
Support
Call Extension
(Workgroup 380)
5
6
7
8
9
0 Operator To Operator
* Repeat Menu Repeat Level
# Main Menu GoTo Top Level
Auto Attendant ID: 120, Phrase 30
Sales
Digit Meaning Action
1 Hardware Call Extension
(Workgroup 310)
2 Applications Call Extension
(Workgroup 320)
3 Check Order
Status
GoTo Item 127
(Collect Order #)
4 Other:
Questions, etc.
Call Extension
(Workgroup 311)
5
6
7
8
9
0
* Repeat Menu Repeat Level
# Main Menu GoTo Top Level
Planning is essential in
organizing an AA menu structure
that makes sense. Planning also
helps you to identify needs for
custom prompts.
This simple example, using
sample work forms for each
menu, shows a beginning
structure: a main menu and two
of the four expansions.
When callers are routed to
workgroup extensions, the
workgroups have their own call
handling settings for greetings,
update phrases, rules for sending
to voice mail, and so on.
Timeout (not shown on forms):
after 7 seconds on first level, call
the operator; on any other level,
go to top level by default.