Skip to main content
All CollectionsInteractive Flow Builder
Custom Text-to-Speech (TTS) in Interactive Flows
Custom Text-to-Speech (TTS) in Interactive Flows

Tailoring Spoken Content to Enhance User Experience

Updated over a week ago

The frontline.io Interactive Flows utilize the powerful Text-to-Speech (TTS) mechanism to vocalize the steps within the flow. We offer flexibility in choosing which elements to include in the audio, such as the title, description, or both. Moreover, we have introduced a new feature that allows for customization of the TTS separately from the written description.

Text-to-Speech functionality is available for the following node types within the Interactive Flow:

  1. Step:

    • The description of the step can be read aloud using TTS.

  2. Question:

    • The question text can be read aloud using TTS.

  3. Multi Choice:

    • The question text and answer options can be read aloud using TTS.

  4. Warning:

    • The warning message can be read aloud using TTS.

  5. Input:

    • The input prompt or instruction can be read aloud using TTS.

In each of these node types, you have the option to enable TTS to provide an auditory experience for users interacting with the content.

Defining Custom TTS:

  1. Open the relevant Interactive Flow.

  2. Select a step.

  3. In the Step Settings, navigate to the text-to-speech section, where you will find two radio buttons with the following options:

    • Read description (default):

      When selected, the procedure player's TTS will audibly read the step's description.

    • Custom:

      When selected, you gain access to a rich text editor, enabling the input of customized text.

      The custom text will be displayed in the settings panel alongside the description.

      During playback, the procedure player will dynamically read aloud the custom text provided by the editor.

      Importantly, the custom text will not be visible within the player itself.

Note: If custom text is entered while the custom option is selected, it needs to be saved even if the editor later switches back to the "Read description" option.

Additionally, editing of the custom text is only possible when the custom option is selected, ensuring full control over the spoken content.

Did this answer your question?