We are testing with using AWS Lex V2 integration and it has been going well however we have been trying to make use of their Wait and Continue specification settings https://docs.aws.amazon.com/lexv2/latest/dg/wait-and-continue.html but it doesn't seem to work with Genesys. We are using a lambda integration with our bot so not sure if that might need to pass some kind of info to Lex to make it work but any insight would be really helpful!
I tested "wait and continue" with and without using a Lambda. The feature worked without using a Lambda. However, I wasn't able to get it to work with a Lambda. We've got an open inquiry to Amazon asking for clarification on its usage with a Lambda. I'll update here when I know more.
Thanks for the quick reply, hopefully we can get some info from them on what type of response the lambda needs to use in order to use this feature or if it is simply not possible with a lambda function.
I got a response and was able to get this working. The slot needs to be required on the intent from my testing. Also verify your slot has the wait and continue configuration saved.
All 3 of the settings need to be configured "Response when user wants the bot to wait", "Periodic response as the bot continue to wait", and "Response when user wants to continue" otherwise it does not save properly.
Additionally if you make changes on the intent page to the slot (toggle required, change name, type, or prompt) that will set the wait and continue config to disabled and clears the fields. Doing those through the advanced options page did not disable and clear the wait and continue config.