FAQs: Dialogflow

Text-to-speech (TTS) playback depends on the voice you choose in Architect:

• If you choose a Google TTS voice, Google Cloud Dialogflow CX performs the TTS playback.
• If you choose a non-Google TTS voice, Architect receives the raw text-to-speech string and performs the TTS with the selected third-party TTS engine.

When Google text-to-speech (TTS) plays back within Google Cloud Dialogflow, Genesys includes the usage fees with the Dialogflow pricing. This process also applies to Genesys Enhanced TTS, as long as you select Google Voices. However, TTS usage fees still apply when TTS plays within the call flow before or after the Call Dialogflow action.

You must install the Google TTS integration or Genesys Enhanced TTS for Architect in order to select the appropriate language playback within Google Cloud Dialogflow.  

You can enable barge-in functionality for the Call Dialogflow Bot action in call flows that use the Google Cloud Dialogflow integration. Configure barge-in functionality for use with Genesys Cloud by creating a Custom Payload Response for your bot in the Google Dialogflow console.

To enable barge-in functionality for a Google Cloud Dialogflow bot, see Enable barge-in for Google Dialogflow bots.

To apply your preferred text-to-speech voice, in the Google Cloud Dialogflow console you must ensure that the Enable Automatic Text To Speech option is on. If it is not, the system uses the default text-to-speech voice.

Do you see the following validation warning: “There are no Architect supported languages configured on the selected Dialogflow agent.”

If so, make sure to set the correct Bot language and region for your bot in the Google Cloud Dialogflow console. Architect flows do not run in generic language codes such as “en.” You must configure the Google Dialogflow bot language to have a region such as “en-us”. For more information, see Languages in Agent Settings.

Grant the Dialogflow API Client and Dialogflow API Reader roles to the service account. For more information, see Granting roles to service accounts.

Make sure to set the correct Bot language locale for your bot in the Google Cloud Dialogflow console. Architect flows do not run in language codes only, such as “en.” You must add the locale, which includes the language and region code combination. For more information, see Languages in Agent Settings.

Google only allows one bot per project. To see multiple bots, create a Consumer project, and then create the bots as Resource projects. Create a service account for the Consumer account and then provide that service account access to the Resource projects. For more information, see Using multiple projects.

To appear as an output in Architect, when you create an intent in Google Cloud Dialogflow make sure to mark it as an end of conversation intent. Otherwise, the intent does not appear here.