Address
Last updated
Last updated
This module collects address information. Select Street Address, City/State, or ZIP code to choose which information will be collected from end users.
When selected, each option adds a default prompt that you can edit further as needed.
When Street is selected, this module will display the Search City, State or Zip field. This field requires you to enter one of the following:
City and state
Zip code
This field accepts strings and variables.
An Address module can collect only one piece of address information at a time.
The Search City, State or Zip field can be completed with end user input by doing the following:
Add a separate Address module with City/State selected. Give the module a unique name.
Connect the first module to a second Address module with Street selected.
In the Search City, State or Zip field, select the plus icon, then add the first module's name to enter it as a variable.
To collect all address information (other than name), add and connect the following modules in order:
City and State: Address, select City/State option
Street is handled last to ensure accuracy. Multiple cities can have streets with the same name.
This setting allows end-users to enter either an American or Canadian address. Enabling the ‘Canada’ setting extends the capability to include Canadian data in addition to, but not in lieu of U.S. data. There is no ‘Canada only’ option or functionality. When active, the ‘City/State’ menu item changes to ‘City/State or Province’, and the ‘State’ menu item changes to ‘State or Province’.
This allows users to set the maximum time, in seconds, that elapse before returning a timeout error. This applies modules that fetch outside scripts, like the SOAP, REST, or subdialog modules. The default value for Timeout Length is 30 seconds. Acceptable number values range from 1 to 120.
Zip code:
Street: Address, select Street option and
When the address is read back to the caller, the variable type address should be used. See for more information.
Note: Speech recognition is enabled by default for the Address module. It cannot be turned off. This is indicated by a green microphone icon in the text field.
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 .
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 .
Enabling this setting overrides the default, global error options set in the Application 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 No Match occurs when the caller input does not match the module's criteria for the input module.
Advanced Fuse users may want to use shadow variables that are available with input modules. For more information on this functionality, please visit the page.
