Date/Time
Last updated
Last updated
This module enables the collection of date or time information. Select Date or Time 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.
If Date is selected, this module will collect date(s) in the MM-DD-YYYY format.
Data output for this option is also formatted as MM-DD-YYYY.
If Time is selected, this module will collect time in the HH:MM format. You must select the desired time format: either 12 Hour or 24 Hour.
Data output for this option is HH:MM for 24 Hour time and either HH:MM AM or HH:MM PM for
12 Hour time.
The module will add an additional prompt to end users to specify AM or PM. During calls, the module will accept a DTMF input of either 1 for AM or 2 for PM.
If speech recognition is enabled, and the end user says "AM" or "PM", the module will automatically bypass this additional AM/PM prompt.
This setting is toggles between the 'Date' and the 'Time' mode.
This allows users to set the maximum time, in seconds, that elapse between inputting each digit before returning a timeout error. This applies to all input modules that accept multiple digits, like Date/Time, Number, and Digits.
The default value for this module is 3 seconds. Acceptable number values range from 1 to 60.
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.
Date and time cannot both be collected using a single Date/Time module. Two separate modules must be used, one for date and the other for time. The () module functions similarly.
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 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 .
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.
