Download IC Cookbook - Intervoice
Transcript
Setting the Maximum Error Retry Limit Before we can start defining what our event/error handlers will do, we need to set one more thing in the DTMF Menu component – the error retry limits. To prevent a key-entry-challenged user from endlessly attempting to make an erroneous selection, we need to limit the number of user-input errors that can occur. We typically give the caller three times to get their selection right. If the caller fails to make a valid selection after three tries, they most likely need help from a live person, so we would typically transfer the caller to an operator. To set the retry count limits, select the NewsWeatherSports DTMF Menu component in the voice diagram. In the Properties view > General option, select the Standard tab. See Figure 6.11. This is where you can set the properties for the Max Errors, Max NoMatch and Max NoInput counters. In our original NWS recipe these maximum counts were all set to 1. Change the three max count values to 3, to follow our best practices for DTMF Menu error handling. The caller will stay in the DTMF Menu component until he either makes a correct entry, or reaches one of the max error limits. Setting the max error counts as shown will allow the caller to have three NoMatch errors (where an invalid option is chosen), or three NoInput errors (where the caller experiences a timeout – basically caller doesn’t “key in” anything), or a combination of these errors that add up to three, which we specify in MaxErrors. If one of these maximums is reached, the call flow leaves the DTMF Menu component through the error exit and goes to the event handler. To get a better understanding of MaxErrors, here’s an example. If a caller has two NoMatch errors and one NoInput error, then Max Errors will now be three. At this point, we will execute the processing that is defined for MaxErrors, which we will define in the event handler sections. An easy way to understand MaxErrors is to realize that this is just a combination of NoMatch and NoInput errors encountered. Figure 6.11 shows the completed error count entries for best practices error recovery. Figure 6.11 - Defining the number of Errors Completing the Event.Diagram Just because the IC event handler diagram has predefined entry points for standard dialog events doesn’t mean that what the event handler does is also standardized. In most cases any of these max-count menu errors would cause a simple explanation prompt to be played, followed by a transfer to a live operator, but it is easy to add more comprehensive dialogs in the event handler. September 2013 Copyright © 2013 Convergys. All rights reserved. 80