Series: Genesys Enhanced TTS with Azure and Google to Amazon Polly or BYOT migration guide
Migrate to Enhanced TTS offering from Amazon Polly
This article assumes that your organization contains published Architect flows that use Enhanced TTS with Microsoft Azure or Google Voices, and describes how to migrate your existing flows to Enhanced TTS offering from Amazon Polly.
This article applies to you if you are using Enhanced TTS with Microsoft Azure or Google Voices in the following flows:
- Call flows
- Secure flows
- In-queue flows
- Bot flows
Before you begin
Review the following articles:
- Text-to-speech (TTS) engines overview
- About text-to-speech (TTS) engines
- Install Genesys Enhanced TTS from the AppFoundry
Select the Genesys Enhanced TTS engine and Amazon Polly voice for a flow
- From the Architect home page, click the Dependency Search tab.
- From the Select a dependency type list, choose the appropriate Text To Speech engine.
- From the Select an engine list, choose the appropriate engine that you are currently using.
- To open a flow from the list of search results, click the flow name.
- Under Settings, click Supported Languages.
- Locate the existing supported language.
- In the Text To Speech column for the supported language, do the following:
- Under Engine, select the TTS engine for the flow:
- Genesys Enhanced TTS: Select this option to use the Enhanced TTS integration.
- Under Voice, select a voice that has the Polly prefix. For example, en-us, polly-Danielle-NTTS.Note: You can select any voice that the selected TTS engine supports. The TTS voice does not need to match the flow’s language. For example, you can use a language as your flow’s default language for which Architect supports speech recognition (“en-GB”), and at the same time, use a different TTS voice (“en-IE”) to meet your customers’ language needs.
- Under Engine, select the TTS engine for the flow:
- Save and publish the flow.
- To check what languages and locales are supported by Amazon Polly, see Neural voices.
- If a Polly neural voice does not match the Genesys supported language codes, it will be added and made available for selection in Genesys Cloud before the effective date.
- If your language is not supported, move to BYOT and continue using TTS voices from Google or Microsoft Azure.
- If you are moving to Amazon Polly and you are using Speech Synthesis Markup Language (SSML) tags in bot flows, you may have to update the tags to Amazon Polly supported ones to render the TTS voices correctly. For more information on the SSML tags supported by Amazon Polly, see Supported SSML tags.
Test your TTS engine playback
For information on testing your TTS engine voice in a flow, see Test your TTS engine playback.