Record
Last updated
Last updated
This module initiates a voice recording. If users want to enable callers to leave a message or a comment they should use this module.
The available range, in seconds, for audio recording is 1 to 14400 (which is 240 minutes, or 4 hours). The recording is ended when silence is detected for more than the final silence settings, or if the caller force stop the recording at any time by pressing any DTMF keys.
If the module is used for a voicemail recording, it is recommended that Post-Call Webservice be used to upload the recorded voice, as the caller can hang up at any time during the recording, The post-call webservice will be made once the call is completed.
Post-Call Webservice can be found under Application Settings > Post-Call Webservice
To gather information such as the duration of the recording or whether or not the terminate character was pressed, please refer to the Shadow Variable section.
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.
This settings enables the module to play an audible beep for end-users before starting the recording.
Note: This setting is enabled by default.
This setting establishes the threshold, in seconds, of silence necessary to trigger the end of a recording. Acceptable number values range from 1 to 14400. The default setting for Final Silence is 3 seconds. For example, if this is set to 3 seconds, the recording stops once an end-user stops speaking for three consecutive seconds. To force-stop a recording, end-users can use any DTMF input.
This setting establishes the maximum threshold, in seconds, for how long to record audio. Acceptable number values range from 1 to 14400 seconds. The default setting for Max Length is 300 seconds (or 5 minutes).
The ‘Show Custom Errors’ option for this module only includes ‘No Input’ option and not 'No Match' because the module is not trying to match a grammar; it simply makes a recording.
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.
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.
Note: Fuse stores audio data in memory temporarily until it is either sent somewhere or the call ends, at which point the audio file is deleted in order to conform to security compliance. Fuse does not have any recorded audio storage. Users who want to save audio recordings must have a data webservice where they can send the audio file by using the REST () module or Post-Call webservice. Audio will be in .WAV format. A guide explaining how to upload audio recordings to your cloud storage solution is available here.
To record the entire phone call, or a series of module and call flow responses, the Call Recording () module can be used instead.
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.
