application-settings

Application Settings

Language Settings

This section allows users to define and modify an application's language settings.

1. Default Language: If an application on has one active language, that is automatically the default language. If an application has more than one language, users can select a different default language using the drop-down menu. Fuse only lists languages active in the application in the drop-down menu.

2. TTS Engine: Users can select their preferred text-to-speech (TTS) engine from the options available in the drop-down menu. Note: Not all TTS engines are available for all languages. If users select a TTS engine that is not compatible with all of the languages present in a given application, then the drop-down will be blank.

3. TTS Voice: Based on the options available from the TTS engine, users can select the different voices for each of the active languages in an application. Select the desired voice for each language from the options in the drop-down menu. Note: Some languages do not provide multiple voice options. To view a complete list of available TTS voices, visit the Text-to-Speech page.

User Input Settings

Settings in this section allow users to customize the end-user experience.

1. Initial Input Timeout: This determines the number of seconds an end-user has to provide input, either by pressing a button or saying something, before Fuse generates a 'No Input' error.

2. Final DTMF Timeout: After an end-user begins entering number pad input, this is the time, in seconds, that end-users have to input additional number pad input before Fuse determines that the end-user has finished inputting information, accepting that information and progressing to the next part of the call-flow.

3. Final Speech Timeout: This is the speech equivalent of final DTMF timeout. After an end-user begins speaking, this is the number of seconds of silence that must elapse before Fuse determines that the end-user has finished speaking. Once end-users reach this threshold, Fuse accepts the input they have already provided and progresses to the next part of the call-flow.


Global Error Handling

These are the default values when errors occur during a phone call. Users can over-ride these settings on specific modules by enabling the 'Show Custom Errors' option on modules that have it.

4. No Match: A 'No Match' error occurs when an end-user enters invalid input. For example, if a prompt asks end-users to “press 1 for yes, or 2 for no” and the end-user enters 0, this would constitute a 'No Match' error.

5. No Input: This happens when the user does not enter anything at all.

  • By default, both 'No Match' and 'No Input' errors allow end-users 3 attempts before taking a different action. Although, three is the recommended number of re-prompt attempts, the number can be increased or decreased for each application using the button in each section. Enter the prompt text in the text box; each attempt can provide a custom message. Clicking the ( ) icon next to the text box deletes that iteration from the application default.
  • Once an end-user exhausts all of their re-prompt attempts, select the next action in the drop-down menu in the “Then” section. The options in this menu include: Keep reprompting, Hang up (the default setting), Jump to, or Transfer to.
  • Selecting “Jump to” generates a new drop-down menu immediately to the right that contains a list of the pages that comprise the application. Users can set which page end-users are routed to by default.
  • Selecting the “Transfer to” option generates a text box to the right where users can set the default phone number where end-users will be transferred, for example, a customer service representative.

6. Shortcuts: Shortcuts allow users to define global grammars and tie those options/grammars to actions. The most common example of this to have a global option whereby end-users enter 0 to be transferred to a live operator. Although it is possible to use automatic speech recognition (ASR) for these functions, this is not a recommended practice.

To add a global shortcut to a Fuse application, click the button in the Shortcuts section. This generates a new field with three columns: Press, Or Say, and To Jump To.

Press: This drop-down menu contains the following DTMF values

  • 0
  • 00
  • 000
  • * (Star)
  • *0 (Star Zero)
  • * * (Double Star)
  • * # (Star Pound)
  • * * * (Triple Star)
  • #
  • ##
  • 9

Or Say: If users opt to include an ASR option for their custom shortcut, enter that information in the text box.

To Jump To: This includes a drop-down menu that contains all of the pages in the application.

Connection Settings

The connection settings control how a Fuse application interacts with an associated webservice.

Webservices

1. Webservice Timeout: This determines the number of seconds that Fuse waits for a connected webservice to respond before throwing an error. The default setting is 10 seconds. While it is certainly possible to increase the default value for this setting, it is recommended to work to increase the speed of the associated webservice if 10 seconds is insufficient.

2. Webservice Fetch Audio: This is where users set the audio that plays while the associated webservice is working. This corresponds to the hold music option for several modules, including the REST and SOAP module. The default is silence. Click the button to add a custom audio file.


Transfers

3. Transfer Timeout: This determines the number of seconds that Fuse waits for the transfer to ring before giving up. The default is 60 seconds.

4. Transfer Duration: This indicates the maximum amount of time, in seconds, that Fuse allows a call transfer to last.

5. Transfer Fetch Audio: This indicates the audio that plays while waiting for the transfer number to pick up. The default audio is of a telephone ringing.

Post-Call Webservice

A post-call webservice is one that a Fuse application connects to immediately after a call ends. These settings control how a Fuse application connects and interacts with that webservice. Fuse supports both SOAP and REST webservices.

Type: This drop-down menu lets users select either a SOAP or a REST webservice.

1. REST: Selecting a REST webservice dynamically changes the available options. Fuse generates fields for URL and parameters.

  • Request Type: Choose the desired REST request type from the drop-down menu. The options are the same as the REST module: GET, POST, POST RAW, PUT, and DELETE.
  • Timeout: Set the desired timeout duration, in seconds.
  • Private: Check this box to enable privacy mode for post-call web services.
  • URL: This is the web address for the webservice. Users can insert variables into the URL using a REST webservice.
  • Header: Type any desired headers into this field. Users can include Fuse variables in headers using the 'plus' button in the text field.
  • Paramenters: Click on the button to add a new parameter to the post-call webservice. Users can insert variables in the 'Value' field.

2. SOAP: Selecting a SOAP webservice dynamically changes the available options. Fuse generates WSDL and Method fields.

  • Timeout: Set the desired timeout duration, in seconds.
  • Private: Check this box to enable privacy mode for post-call web services.
  • WSDL: Enter WSDL connection information into this field. Click the icon ( ) to the right of the text box to refresh the connection.
  • Method: Select the webservice method from the first drop-down menu; this menu auto-populates after fetching values from a valid SOAP URL. Users can also choose between SOAP v1.1 or SOAP v1.2.

JavaScript Libraries

To add a JS library to your Fuse+ application, click the “+Add” button. This opens a new windows with a drop-down menu. Select the desired library from the menu to add it to your application.

Note: The JS Libraries section only appears in the Application Setting page after a user creates a JS library. You can create a new JS library at the My Account page.

application-settings.txt · Last modified: 2018/06/26 10:58 by admin