Lync 2010 Auto Attendant Call Flow Design
You use interactive voice response (IVR) to obtain information from callers and navigate them to the appropriate queue. You can specify question-and-answer pairs that you use for call navigation. Depending on the caller’s response, the caller either hears a follow-up question, or is routed to the appropriate queue. The IVR questions and the caller’s responses are provided to the responding agent when he or she accepts the call. This system provides valuable information to the responding agent.
Overview of the IVR Features
The Response Group application offers speech recognition and text-to-speech capabilities in 26 languages. You can enter IVR questions using text-to-speech or a wave (.wav) or Windows Media audio (.wma) file. Callers can respond by using voice or dual-tone multifrequency (DTMF).
Interactive workflows support up to two levels of questions, with each question having up to four possible answers. The IVR asks the caller a question that has up to four possible answers, and depending on the caller’s response, routes the caller to a queue or asks a second question. The second question can also have four possible answers. Depending on the answer to the second-level question, the caller is routed to the appropriate queue.
The IVR questions and the caller’s responses are provided to the responding agent when he or she accepts the call.
Working with Speech Technologies
Speech technologies, such as speech recognition and text-to-speech, can enhance customer experience and let people access information more naturally and effectively. However, there can be cases where the specified text or the user voice response is not recognized correctly by the speech engine. For example, the “#” symbol is translated by the text-to-speech engine as the word “number.” This issue can be mitigated by the following:
- Speech engine gives caller five attempts to answer the question. If caller answers the question incorrectly (the answer is not one of the specified responses) or does not provide an answer at all, he/she gets another chance to answer question. Caller has five attempts to answer the question before being disconnected. You can configure IVR to play a customized message after each caller error. The question is repeated each time.
- Minimize the potential for ambient noise to be interpreted by the speech engine as a response by using longer responses. For example, responses should have more than one syllable and should sound notably different from each other.
- If your questions have both speech and DTMF responses, configure speech responses with words that represent the concept rather than the DTMF response. For example, use "Press 1 or say billing” instead of using "Press or say one.”
- After you design your IVR, call the workflow, listen to the prompts, respond to each of the prompts using voice, and verify that the IVR sounds and behaves as expected. You can then modify the IVR to fix any interpretation issues. Following the previous example, if you need to refer to the # key, you can rewrite your IVR prompt to use the key name, rather than the # symbol. For example, "To talk to sales, press the pound key."
IVR Design Examples
The following sections contain examples of different IVR scenarios and question-and-answer pairs.
IVR with One Level of Questions
This uses speech recognition to detect the caller’s response.
For Example:
Question: "Thank you for calling Human Resources. If you would like to speak to payroll, say payroll. Otherwise, say HR."
- Option 1 is selected: The caller is routed to the payroll team.
- Option 2 is selected: The caller is routed to the human resources team.
IVR with Two Levels of Questions
This allows callers to respond using either speech or DTMF keypad input.
For Example:
Question: "Thank you for calling the IT Help Desk. If you have a network access problem, press or say 1. If you have a software problem, press or say 2. If you have a hardware problem, press or say 3."
- Option 1 is selected: The caller is routed to the network support team.
- Option 2 is selected: The caller is asked a follow-up question:
Question: "If this is an operating system problem, press or say 1. If this is a problem with an internal application, press or say 2. Otherwise, press or say 3."
- Option 1 is selected: The caller is routed to the operating systems support team.
- Option 2 is selected: The caller is routed to the internal applications support team.
- Option 3 is selected: The caller is routed to the software support team.
- Option 3 is selected: The caller is asked a follow-up question:
Question: "If this is a printer problem press 1. Otherwise, press 2."
- Option 1 is selected: The caller is routed to the printer support team.
- Option 2 is selected: The caller is routed to the hardware support team.
Two-level Interactive Call Flow
The following list describes some best practices for designing your IVR:
- Let caller get to the task quickly. Avoid giving too much information or long marketing messages in your IVR.
- Callers cannot bypass the welcome message. If you want to include a lengthy message, add it to the first question instead of to the welcome message. This way, callers can avoid the message if it is part of the first question by answering the question.
- Try to speak in caller’s language. Speak naturally and avoid unnatural language.
- Write efficient and effective prompts. Remove any unnecessary options. Arrange the information so that the caller’s expected response is at the end of the sentence. For example, “To speak to the sales team, press 1."
- Make voice responses user friendly. For example, if you specify both DTMF and voice responses, use something like: "To speak to the sales team, press 1 or say sales."
- Test IVR on a group of users before deploying it across your organization.
