We're looking to migrate a bot from Genesys Engage that uses quite a bit of customisation to achieve a very granular level of control over how Dialogflow handles a call. There is a raft of things being done with speech adaptation, control over timeouts etc.
Through looking at the documentation, I can see that some things can be set using custom payloads in bot responses. For example, if you want the response to be interruptible you can specify this:
{
"barge-in": true
}
If you want to play a prompt from architect, you can specify this:
{
"user-prompt": "ArchitectUserPromptName"
}
My question is - what other custom payload responses are there? Is there a (possibly internal) list of other things that can be returned so that the integration can control the bot?
Those responses are the only custom payload responses that are supported by the Genesys Cloud integration, however, the Genesys Cloud integration and Genesys Engage integration with Dialogflow are fundamentally different in their operation.
I believe with Genesys Engage much of the speech processing was done within Engage and the integration with Dialogflow is largely text based.
With the Genesys Cloud integration the audio is streamed to Dialogflow which allows Dialogflow to be in control of the speech adaptation and end of speech detection so those settings are not applicable for the Genesys Cloud integration.
So basically, the Genesys Cloud integration doesn't expose additional controls because Dialogflow is actually in control of those features.