Genesys Cloud - Main

I am contacting you to confirm the specifications regarding the Genesys STT engines described in the following article.
 
https://help.genesys.cloud/announcements/genesys-cloud/addition-of-deepgram-flux-and-nova-3-speech-to-text-stt-engines-and-updated-stt-engine-names/
 
I have the following two questions regarding the information in the article:
 
* Are there any differences in the characteristics or behavior of the STT engines listed in the article?
 
  If so, could you please explain the features and characteristics of each engine?
 
* Is it correct to understand that the current Enhanced Transcription service uses V4?
 
Kind Regards,

Hello Ryuma, 

The documentation you're referencing is primarily a naming update, rather than a comparison of engine behavior or performance. 

From the documentation, the main functional difference called out is support for custom ASR dictionaries:

Supported: Amazon Transcribe (v3) and Genesys Native (v4)
Not supported: Google Cloud (v1) and Microsoft Azure (v2)

For the Deepgram engines (Flux and Nova-3), audio is processed by Deepgram. Depending on the configured endpoint, audio may be processed outside your Genesys Cloud region, so organizations with data residency or compliance requirements should review the Deepgram regional endpoint documentation before enabling either engine.

Aside from the updated names, the documentation states that this is a naming change only. Existing bot flows continue to work without modification, and there are no changes to engine behavior, accuracy, or configuration as a result of the rename.

The previous Genesys Enhanced v1–v4 names were simply labels for the available STT engine options. The new naming makes the underlying provider (or Genesys Native) explicit, rather than implying they're all the same technology.

Cheers,