Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Hi

That's the Speech to Text engine which you are looking at inside Bot Flow. If you are trying to set Azure Text to Speech engine for your bot, you will need to select that in you Inbound Flow.

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

So, learn something new every day!  I see that Genesys now divides out the Normal TTS from the Advanced TTS with the Enhanced TTS engine.  There si a new subscription for each and it is separated out in the resource billing.   Not, that setting you see in the Bot flow has nothing to do with this.  That is for STT or ASR.  This shows up in my ORG as well (but unsure how long it has been there).  I am going to write the PM to see what is up.  @Anik Dey, can you explain what the Genesys Enhanced v1 and v2 are about?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Hi Robert, 

I don't really get, why my inbound flow setting controls which engine to use for TTS, while the STT/ASR setting is controlled by the bot flow itself. 
Why isn't the STT/ASR setting in the inbound flow as well...? Why is one flexible and controllable by the inbound flow, while the other is fixed in the bot flow..? This seems like a rather strange inconsistent product design to me, if there isn't a technical reason. And if so, it would still be helpful to have a hint in the GUI telling you the other setting is found in the inbound/bot flow. 

I'm fully aware though, that you are not a Genesys employee... ;) 

Cheers
Michael

So, learn something new every day!  I see that Genesys now divides out the Normal TTS from the Advanced TTS with the Enhanced TTS engine.  There si a new subscription for each and it is separated out in the resource billing.   Not, that setting you see in the Bot flow has nothing to do with this.  That is for STT or ASR.  This shows up in my ORG as well (but unsure how long it has been there).  I am going to write the PM to see what is up.  @Anik Dey, can you explain what the Genesys Enhanced v1 and v2 are about?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Mine is not to question the inner workings of the Genesys PM, but here is what I would reply with.

TTS is a customer-facing feature and you want consistency between the call flow and the BOT, especially if the bot is used across multiple flows from multiple business units that might like a different voice.  You define the TTS in flow that will be used by the Bot for this reason. 

ASR is not used in Inbound Call Flows, so no reason to define there.  A bot might require a unique ASR for things like language support or a specific vertical and that is why you can define that at the bot level.  Also, this is not customer facing.  

Hi Robert, 

I don't really get, why my inbound flow setting controls which engine to use for TTS, while the STT/ASR setting is controlled by the bot flow itself. 
Why isn't the STT/ASR setting in the inbound flow as well...? Why is one flexible and controllable by the inbound flow, while the other is fixed in the bot flow..? This seems like a rather strange inconsistent product design to me, if there isn't a technical reason. And if so, it would still be helpful to have a hint in the GUI telling you the other setting is found in the inbound/bot flow. 

I'm fully aware though, that you are not a Genesys employee... ;) 

Cheers
Michael

So, learn something new every day!  I see that Genesys now divides out the Normal TTS from the Advanced TTS with the Enhanced TTS engine.  There si a new subscription for each and it is separated out in the resource billing.   Not, that setting you see in the Bot flow has nothing to do with this.  That is for STT or ASR.  This shows up in my ORG as well (but unsure how long it has been there).  I am going to write the PM to see what is up.  @Anik Dey, can you explain what the Genesys Enhanced v1 and v2 are about?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

Haha...

Well that might an argueable p.o.v. - but nothing to discuss here. 
As paying customer for a high end system I simply expect every decision by PM to be very well thought through - and if I get the impression anything isn't it would be my good customer obligation to provide constructive criticism to support improbing the product. ;)

I perfectly agree with the argument of having the inbound flow configuring the TTS engine for the exact reasons you mentioned. 

But imho it is not correct, that inbound flows are not using ASR: With menus using voice input instead of DMTF htere sure IS ASR in inbound flows. 
(And the fact, that this is the only option for using ASR in inbound flows is actually a terribly missed feature: collect input blocks should support ASR as well.)

ASR might not be as relevant as TTS - but it may very well be, that different engines perform better or worse for different languages. 
So this choice would definitely make sense - and I have been assuming that the TTS engine choice in inbound flows covers ASR also... 

Mine is not to question the inner workings of the Genesys PM, but here is what I would reply with.

TTS is a customer-facing feature and you want consistency between the call flow and the BOT, especially if the bot is used across multiple flows from multiple business units that might like a different voice.  You define the TTS in flow that will be used by the Bot for this reason. 

ASR is not used in Inbound Call Flows, so no reason to define there.  A bot might require a unique ASR for things like language support or a specific vertical and that is why you can define that at the bot level.  Also, this is not customer facing.  

Hi Robert, 

I don't really get, why my inbound flow setting controls which engine to use for TTS, while the STT/ASR setting is controlled by the bot flow itself. 
Why isn't the STT/ASR setting in the inbound flow as well...? Why is one flexible and controllable by the inbound flow, while the other is fixed in the bot flow..? This seems like a rather strange inconsistent product design to me, if there isn't a technical reason. And if so, it would still be helpful to have a hint in the GUI telling you the other setting is found in the inbound/bot flow. 

I'm fully aware though, that you are not a Genesys employee... ;) 

Cheers
Michael

So, learn something new every day!  I see that Genesys now divides out the Normal TTS from the Advanced TTS with the Enhanced TTS engine.  There si a new subscription for each and it is separated out in the resource billing.   Not, that setting you see in the Bot flow has nothing to do with this.  That is for STT or ASR.  This shows up in my ORG as well (but unsure how long it has been there).  I am going to write the PM to see what is up.  @Anik Dey, can you explain what the Genesys Enhanced v1 and v2 are about?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?

The Menu ASR in Inbound Call Flows is NOT ASR. It is only doing phoneme matching like the old ININ Speech.  It is no way does any speech to text and is only matching the sounds of the words in the input to what the caller is saying, hence the terrible recognition rate.   

Haha...

Well that might an argueable p.o.v. - but nothing to discuss here. 
As paying customer for a high end system I simply expect every decision by PM to be very well thought through - and if I get the impression anything isn't it would be my good customer obligation to provide constructive criticism to support improbing the product. ;)

I perfectly agree with the argument of having the inbound flow configuring the TTS engine for the exact reasons you mentioned. 

But imho it is not correct, that inbound flows are not using ASR: With menus using voice input instead of DMTF htere sure IS ASR in inbound flows. 
(And the fact, that this is the only option for using ASR in inbound flows is actually a terribly missed feature: collect input blocks should support ASR as well.)

ASR might not be as relevant as TTS - but it may very well be, that different engines perform better or worse for different languages. 
So this choice would definitely make sense - and I have been assuming that the TTS engine choice in inbound flows covers ASR also... 

Mine is not to question the inner workings of the Genesys PM, but here is what I would reply with.

TTS is a customer-facing feature and you want consistency between the call flow and the BOT, especially if the bot is used across multiple flows from multiple business units that might like a different voice.  You define the TTS in flow that will be used by the Bot for this reason. 

ASR is not used in Inbound Call Flows, so no reason to define there.  A bot might require a unique ASR for things like language support or a specific vertical and that is why you can define that at the bot level.  Also, this is not customer facing.  

Hi Robert, 

I don't really get, why my inbound flow setting controls which engine to use for TTS, while the STT/ASR setting is controlled by the bot flow itself. 
Why isn't the STT/ASR setting in the inbound flow as well...? Why is one flexible and controllable by the inbound flow, while the other is fixed in the bot flow..? This seems like a rather strange inconsistent product design to me, if there isn't a technical reason. And if so, it would still be helpful to have a hint in the GUI telling you the other setting is found in the inbound/bot flow. 

I'm fully aware though, that you are not a Genesys employee... ;) 

Cheers
Michael

So, learn something new every day!  I see that Genesys now divides out the Normal TTS from the Advanced TTS with the Enhanced TTS engine.  There si a new subscription for each and it is separated out in the resource billing.   Not, that setting you see in the Bot flow has nothing to do with this.  That is for STT or ASR.  This shows up in my ORG as well (but unsure how long it has been there).  I am going to write the PM to see what is up.  @Anik Dey, can you explain what the Genesys Enhanced v1 and v2 are about?

Hi Robert,
What can I say - they are both offered to me as the only available text to speech engines in my bot - Azure isn't, although also configured (see the screenshot). 

I am not sure where you are getting the v1 and v2 for Enhanced TTS.  You don't get a choice as to which to use as V2 is just the updated version of Enhanced TTS that offers better quality, more languages, better performance and the future integration with other TTS providers.

Hi Robert!
Theanks for the reply - generally  helpful, but not really explaining my concrete issue. 
If Azure should be available for bot flows, why can't I pick it as engine under the supported languages configuration, although the integration is configured and working? I am only offered Genesys Enhanced V1 and V2. 

And what's the difference between both? I would assume V1 is just kept for legacy purposes and V2 is a current version..? 

Thanks a lot for the input! :)
Michael

I agree this can be fairly confusing.  Standard TTS cannot and should not be used for natural language bots because it sounds terrible and not natural at all.  I am not sure how any management of a company would accept it for customer-facing systems.  

Genesys Enhanced TTS is a merely just a white label for Google and Microsoft TTS voices so you don't have to subscribe to these services yourself.  Yes, it cost you about 20% more than going direct, but it comes in on your single bill from Genesys.  The other nice feature is that if you use Enhanced TTS in a Genesys Bot Flow (not 3rd-party), the characters used are NOT charged to the customer.  

3rd-party TTS from AWS, Microsoft, Google, etc. are possible with Genesys and you would pay these partners directly for the consumption of their TTS.  Genesys marks these as BYOT Rate A at $0.00, so there is no overhead to use them currently, but don't assume that will be the case going forward as it is marked as Rate A for the characters used and Genesys has the option to place a price on that rate at a future date.

Does that make it less confusing? 

This is a confusing topic, I have to say. Ok - another 6 months passed, but right now in my (voice) bot flow I only see "Genesys Enhanced V1" and "Genesys Enhanced V2" as offered STT engines - although we have a fully configured (and in use) Micorsoft Azure integration - and the bot flow in question is published and in production - and I seem to remember I created it using the Azure integration and a corresponding voice. 

Supporting the irritation: Showing the supported languages section in the flow does not display an engine for the already configured language in the flow!

Nope.  Still have to use any engine but that one.

Can we use Genesys (non-enhanced) TTS engine with bot flows now? or Do we still need to choose a different TTS engine?