Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

Hi @Robert Wakefield-Carl

Thank you for the clarification, much appreciated. Yes you are correct it was  not mentioned that we can continue using the same engine with just additional work to be done. 

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

@Robert Wakefield-Carl, the notice is Q4, you indicated Sep 29, 2025, is this firmed date?

Genesys Cloud will deprecate support for Google and Microsoft text-to-speech (TTS) voices within Enhanced TTS in Q4 2025.

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

Yes  Deprecation: Genesys Enhanced TTS - Microsoft Azure and Google Voices - Genesys Cloud Resource Center.

@Robert Wakefield-Carl, the notice is Q4, you indicated Sep 29, 2025, is this firmed date?

Genesys Cloud will deprecate support for Google and Microsoft text-to-speech (TTS) voices within Enhanced TTS in Q4 2025.

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.

aha, greatly appreciated.

Yes  Deprecation: Genesys Enhanced TTS - Microsoft Azure and Google Voices - Genesys Cloud Resource Center.

@Robert Wakefield-Carl, the notice is Q4, you indicated Sep 29, 2025, is this firmed date?

Genesys Cloud will deprecate support for Google and Microsoft text-to-speech (TTS) voices within Enhanced TTS in Q4 2025.

This deprecation announce was poorly written and very misunderstood.  Genesys needs to chime in to why this is happening and what the change will entail.

First, if a customer is using Google or Azure TTS voices, they will still be able to use them, but it will require the customer to engage with Google/Azure and install the integration for their TTS services.  The customer would be billed by those 3rd-parties directly for the use of TTS on their platforms.

Genesys Enhanced TTS will only include AWS Polly voices after September 29, 2025.

Customers using Google or Microsoft voices with Enhanced TTS will have to edit each flow and change to the 3rd-party Integration and Voice and publish each before the 9/29 date or alternatively, edit and publish each flow with a new AWS TTS voice.

As you can see, none of this information was clearly communicated in the deprecation announcement, especially the part of having to touch each and every flow.

Hi Community,

Good day.

Following Genesys' announcement of the deprecation of "Genesys Enhanced TTS" (excluding Polly, which doesn't meet our needs), we are seeking a replacement.

We want to engage with the community to understand what alternative solutions you are considering and any challenges encountered during your evaluation.

Thank you in advance and much appreciated.