Skip to main content

Text-to-speech (TTS) engines overview

Feature coming soon: Genesys Generative TTS

Note: The organization's default text-to-speech (TTS) engine is Genesys TTS. To access additional third-party TTS engines in Architect, first obtain them from the Genesys AppFoundry. Then, configure them in Genesys Cloud. For more information, see .

To meet your organization’s text-to-speech (TTS) needs, Genesys offers the following options:

  • Genesys provides an that you can install from the Genesys AppFoundry. The Genesys Enhanced TTS engine offers many voice and language options and great audio quality. Genesys includes usage of the Enhanced TTS engine free of charge in Dialog Engine Bot Flows.
  • You can add third-party TTS engine integrations and then select voice and language options. These integrations expand language options and enable you to select a TTS voice for the organization, serving callers across built-in applications with the most appropriate voice. Architect can integrate with these third-party solutions for text-to-speech playback on a per-flow basis. 
  • Genesys Cloud also includes a default Genesys text-to-speech (TTS) engine that offers more limited voice and language options and is suitable for testing purposes.

For a specific flow, you can configure the TTS engine and voice options for each language you include in the flow. You can select any TTS voice that the configured TTS engine supports. For more information, see .

Genesys Generative TTS

Genesys Generative TTS converts text into human-like voices across supported languages. Architect flow authors can work with generative TTS voices for natural sounding text-to-speech playback within call flows, bot flows, and voice surveys.

Genesys supports the following voice models under Genesys Generative TTS:

Voice modelProviderCall flowsBot flows (Virtual Agents, AI guides, and agentic virtual agents)Voice surveys
Chirp 3: HD voicesGoogle Cloud✓✓✓
Eleven Flash v2.5ElevenLabs✓✓✓
Generative voicesAmazon Polly✓✓✓

Notes:
  • TTS voices that do not directly match the flow’s language can result in issues with the customers’ text-to-speech experience.
  • If your flow uses prompts, Architect plays the prompt’s audio recording based on the flow’s language. If you want to use a TTS voice for prompts, remove the audio recording and add text instead.
  • Because not all TTS engines operate the same way, Genesys and third-party TTS engine playback performance can vary depending on language, dialect, and voice. Perform testing to ensure that you find the best solution for your use case, or contact your solutions consultant. For more information about third-party TTS engine performance, see .
  • Only third-party TTS solutions are supported in the US East 2 (Ohio)/FedRAMP region. 
  • Only PCI-certified third-party solutions are available in Architect secure call flows. Secure call flows can only use the Genesys TTS engine, Genesys Enhanced TTS, Amazon Polly TTS, Google Cloud Text-to-Speech, Microsoft Azure Cognitive Services Text-to-Speech, or Nuance Text-to-Speech.
  • You can configure an Architect flow with a language that supports runtime data playback and select a different TTS voice for localized speech. For example, you can use English (“en-US”) as the flow language to enable runtime data playback and select English (“en-IE”) voice to provide an Irish accent.