This module allows users to re-direct the call-flow based on binary choices like yes/no or true/false.
There is no default call path for this module.
Note: By default, end-users enter 1 for yes or 2 for no. When enabling speech input, end-users can say “yes” or “no”.
This functionality and grammar is automatically built into the applications for every supported language.
| This setting allows callers to interrupt a prompt before it finishes playing.
When enabled, DTMF input interrupts the prompt and progresses the call forward in the call-flow. If speech recognition is enabled on the ensuing module in the call-flow, then end-users can also interrupt the prompt with a spoken utterance, too. Disabling barge-in forces callers to listen to the entire prompt.
A barge-in enabled module will have a dashed line on top of the text box. See example here.
Note: This setting is enabled by default.
| This setting enables Automatic Speech Recognition (ASR) for that module.
A green microphone ( ) icon appears in the module when this is enabled.
| This setting controls the logging function of a module.
Enabling the 'Private' setting instructs the module to not record, report, or retain the information input to that module for reporting or any other purposes. When enabled any information entered into a module during a call will be lost immediately when the call terminates.
The 'Private' setting is critical for businesses that need to maintain PCI-DSS or HIPAA compliance.
The module icon, in the upper left-hand corner, becomes grayed-out when this setting is enabled. See more details here.
| Enabling this setting overrides the default, global error options set in the Application Settings > User Input Settings.
This allows users to establish custom error handling in order to act on errors in a specific way in that module.
Instead of progressing to the next module in the call-flow, custom error handling allows users to re-prompt the same module, to provide a custom error message, to re-direct the call based on the error, or any other desired behavior.
Adding multiple errors ( ) to a module functions behave the same way as a counter.
The first error follows the path for the first error listed, if a second error occurs in the same module it follows the second listed error, and so on until all errors are exhausted or an error directs the end-user away from that module.
No Input occurs when the caller does not provide an input based on the timeout settings.
This is based on the “Initial input timeout” in User Input Settings
No Match occurs when the caller input does not match the module's criteria for the input module.
Advanced Settings: Advanced Fuse users may want to use shadow variables that are available with input modules. For more information on this functionality, please visit the Shadow Variables page.