Understanding Unified Messaging Auto Attendants
Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-04-28
Microsoft Exchange Server 2010 Unified Messaging (UM) enables you to create a single or multiple UM auto attendants, depending on the needs of your organization. Unlike other Unified Messaging objects, such as UM dial plans and UM IP gateways, you aren't required to create UM auto attendants. However, auto attendants help internal and external callers locate users or departments that exist in an organization and transfer calls to them. This topic discusses the UM auto attendant feature found in Exchange 2010 Unified Messaging.
Looking for other management tasks related to UM auto attendants? Check out Managing UM Auto Attendants.
In telephony or Unified Messaging environments, an automated attendant or auto attendant menu system transfers callers to the extension of a user or department without the intervention of a receptionist or an operator. In many auto attendant systems, a receptionist or operator can be reached by pressing or saying zero. The automated attendant is a feature in most modern Private Branch eXchange (PBX) and Unified Messaging solutions.
Some auto attendant systems use message-only information menus and voice menus so an organization can provide business hours, directions to the premises, information about job opportunities, and answers to other frequently asked questions. After the message plays, callers are forwarded to the receptionist or operator, or they can return to the main menu.
In more complex auto attendant systems, the menu system can be used to search for other auto attendant menus, locate a user in the system, or transfer to another outside telephone line. The menu system can also be used to let the caller interact with the system in certain situations, such as when a student enrolls for a college class or checks a grade, or when you activate a credit card over the telephone.
Although auto attendants can be very useful, if they aren't designed and configured correctly, they can confuse and frustrate callers. For example, specifically in large organizations, when auto attendants aren't designed correctly, callers can be led through a lengthy series of questions and menu prompts before they are finally transferred to a person to answer their questions.
Exchange 2010 Unified Messaging enables you to create one or more UM auto attendants depending on the needs of your organization. UM auto attendants can be used to create a voice menu system for an organization that lets external and internal callers move through the UM auto attendant menu system to locate and place or transfer calls to company users or departments in an organization.
When anonymous or unauthenticated users call an external business telephone number, or when internal callers call a defined extension number, they are presented with a series of voice prompts that help them place a call to a user or locate a user in the organization and then place a call to that user. The UM auto attendant is a series of voice prompts or .wav files that callers hear instead of a human operator when they call an organization that has Exchange 2010 Unified Messaging. The UM auto attendant lets callers move through the menu system, place calls, or locate users by using dual tone multi-frequency (DTMF) or voice inputs. However, for Automatic Speech Recognition (ASR) or voice inputs to be used, you must enable ASR on the UM auto attendant.
In some companies (especially in East Asia), office telephones may not have letters on the keys of the telephone. This makes the spell-the-name feature that uses the DTMF interface almost impossible to use, without a working knowledge of the key mappings. By default, Exchange 2010 Unified Messaging uses the E.161 key mapping. For example, 2=ABC, 3=DEF, 4=GHI, 5=JKL, 6=MNO, 7=PQRS, 8=TUV, 9=WXYZ.|
When inputting the combination of letters and numbers, for example Mike1092, the numeric digits are mapped to themselves. For an e-mail alias of Mike1092 to be entered correctly, the user must press the numbers 64531092. Also for characters other than A-Z and 0-9, there won't be a telephone key equivalent. Therefore, these characters shouldn't be entered. For example, the e-mail alias mike.wilson would be entered as 6453945766. Even though there are 11 characters to be input, only 10 digits are entered by the user because the period (.) doesn't have a digit equivalent.
A UM auto attendant has the following features:
It provides corporate or informational greetings.
It provides custom corporate menus. You can customize these menus to have more than one level.
It provides a directory search function that enables a caller to search the organization's directory for a name.
It enables a caller to connect to the telephone of, or leave a message for, members of the organization.
In the Active Directory directory service, each UM auto attendant created is represented as an object. There is no limit to the number of UM auto attendants you can create in Active Directory. Each Exchange 2010 Unified Messaging auto attendant can support an unlimited number of extensions. A UM auto attendant can reference one, and only one, UM dial plan. However, UM auto attendants can reference or link to other UM auto attendants.
An incoming call received from an external telephone number or an internal telephone extension is processed by a Unified Messaging server and then sent to a UM auto attendant that has been created. The UM auto attendant is configured by the system administrator to use prerecorded voice (.wav) files that are then played over the telephone to the caller and that enable the caller to move through the Unified Messaging menu system. You can customize all the .wav files used when you configure a UM auto attendant to meet the needs of your organization.
For more information about message flow with UM auto attendants, see Unified Messaging Auto Attendant Call Processing.
There are situations in which you may have to provide callers with auto attendants that have different languages. The language setting available on a UM auto attendant enables you to configure the default prompt language on the auto attendant. When you are using the default system prompts for the auto attendant, this is the language that the caller will hear when the auto attendant answers the incoming call. This language setting affects only the default system prompts provided after the Unified Messaging server role is installed. This language setting doesn't affect custom prompts configured on an auto attendant. The language selected as the default for the auto attendant is based on the version of Exchange 2010 installed.
When you install the U.S. English version of Exchange 2010, U.S. English is the only language available to configure on UM auto attendants. If you install a localized version of Exchange 2010, for example, Japanese, you can configure the auto attendant that you create to use Japanese or U.S. English for the default language. Additional UM language packs can be installed on a Unified Messaging server to enable you to use other default languages on an auto attendant.
|You cannot install UM language packs using the .msi file for the language.|
For example, if you have a business that's based in the United States but requires a menu system that gives callers the options of U.S. English, Spanish, and French, you must first install the UM language packs that you need. In this case, if you have installed the U.S. English version of Exchange 2010, you would install the UM language packs for Spanish and French. However, because a Unified Messaging auto attendant can have only one language configured at a time, you would create four auto attendants: a main auto attendant configured to use U.S. English and then one auto attendant for each language: U.S. English, Spanish, and French. You would then configure the main auto attendant to have the appropriate key mappings to access the other auto attendants that you created for each language. In this example, the main auto attendant would answer the incoming call and the caller would hear, "Welcome to Contoso, Ltd. For English, press or say 1. For Spanish, press or say 2. For French, press or say 3."
After you create a UM auto attendant, a default system prompt will be used for the non-business hours main menu prompt greeting heard by callers after the non-business hours welcome greeting is played. Although the system prompts mustn't be replaced or changed, you probably want to customize the greetings and menu prompts used with UM auto attendants. Frequently, in addition to configuring a customized non-business hours welcome greeting, you also want to create and configure a custom non-business hours main menu prompt greeting. After you configure a custom non-business hours main menu prompt greeting, you must enable key mappings on the UM auto attendant for non-business hours.
A custom non-business hours main menu prompt greeting is a list of options callers hear during non-business hours. To let callers hear a non-business hours main menu prompt greeting, you first must configure the business and non-business hours schedule by using the Times tab available on the Properties for a UM auto attendant. For example, "You have reached Trey Research after normal business hours. If you are experiencing a medical emergency, please hang up and dial 911. To leave a message for one of our doctors, press 1. To leave a message for one of our physical therapists, press 2. To leave a general message for one of our front office coordinators, press 3. To be connected with an after hours operator, press 0."
By default, when you create a UM auto attendant, the business and non-business hours greetings or prompts aren't configured and no key mappings are defined for business or non-business hours main menu prompts. To correctly configure customized non-business hours main menu greetings and prompts, you must:
Configure business and non-business hours on the Times tab.
Create the greeting file that will be used for the non-business hours welcome greeting.
Configure the non-business hours welcome greeting on the Greetings tab.
Create the greeting file that will be used for the non-business hours main menu prompt greeting.
Configure the non-business hours main menu prompt greeting on the Greetings tab.
Enable and configure the non-business hours key mappings on the Key Mapping tab.
If you use the default main menu prompt greeting and define a key mapping or multiple key mappings, the UM Text-to-Speech (TTS) engine will synthesize a main menu prompt. However, the TTS engine will only synthesize a main menu prompt if the default greeting is configured and at least one key mapping has been defined. The TTS engine will not synthesize a main menu prompt if you're using a custom main menu prompt. For example, "For the sales department, press 1. For the support department, press 2." To create this main menu prompt, you must create two key mappings: one named "Sales Department" and another named "Support Department", and then configure the key mapping entry to play an audio file, transfer to an extension number, or send the caller to another auto attendant.
When you configure key mappings, you define the options and the operations that will be performed if a caller speaks a phrase while they're using a speech-enabled auto attendant or the caller presses the key on the keypad of the telephone while they're using an auto attendant that isn't speech-enabled. To configure key mappings, you must add key mapping entries. When you configure the key mapping entries for an auto attendant, you must:
Enable business hours key mapping.
Add a key mapping entry.
Type the name of the key mapping entry.
Select Presses this key or Presses no key (Time-out) or type the phrase that the caller will say in the Or the user says this phrase field.
Configure the action you want performed:
Play an audio file
Transfer to an extension number
Run an auto attendant
- Play an audio file
The following examples demonstrate how you can use UM auto attendants with Exchange 2010 Unified Messaging:
- Example 1 At a company called Contoso, Ltd., external customers can use three external telephone numbers: 425-555-0111 (Corporate Offices), 425-555-0122 (Product Support), and 425-555-0133 (Sales). The Human Resources, Administration, and Accounting departments have internal telephone extensions and must be accessed from the Corporate Offices UM auto attendant.
To create a UM auto attendant structure that supports this scenario, create and configure three UM auto attendants that have the appropriate external telephone numbers. Create three other UM auto attendants for each department in the Corporate Offices. You then configure each UM auto attendant based on your requirements, such as the greeting type or other navigational information.
The following figure is a graphical representation of how UM auto attendants can be used in Example 1.
- Example 2 At a company called Contoso, Ltd., external customers call one main number for the business, 425-555-0100. When an external caller calls the external number, the UM auto attendant answers and prompts the caller by saying, "Welcome to Contoso, Ltd. Please press or say 'One' to be transferred to corporate administration. Please press or say 'Two' to be transferred to product support. Please press or say 'Three' to be transferred to corporate information. Please press or say 'Zero' to be transferred to the operator." To create a UM auto attendant structure that supports this scenario, you create a UM auto attendant that has customized extensions that route the call to the appropriate extension number.
The following figure is a graphical representation of how Unified Messaging auto attendants can be used in Example 2.