Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lex Integration with the demo app. #5

Open
pks90 opened this issue Mar 17, 2020 · 0 comments
Open

Lex Integration with the demo app. #5

pks90 opened this issue Mar 17, 2020 · 0 comments

Comments

@pks90
Copy link

pks90 commented Mar 17, 2020

@danilop First of all thankyou for the amazing demo app and congrats for the awesome talk https://www.youtube.com/watch?v=d56OdHkMd80 which brought me here.

Now, I am lately considering to utilize the aws-websocket apis for an application development where both chatbot and chat are allowed.

So, the use-case is like a conversation which is initiated by a user with a chatbot and when the user is not satisfied from the QnA with the bot , we connect the chat to a human .

I thought of an architecture like below, of course a minor extension to the solution that you have provided, I have just introduced the Lex Conversations API here.

Picture1

I would like to know your thoughts for this approach i.e. whether this should be the way to go for the use-case that I would like to develop or it should be the other way round i.e. I connect to the Lex API directly and then somehow try to open a websocket for further communication when a human is required to take over ?

Or altogether something completely different which is already there ! Please suggest, I also have an open question in these regards here on SO https://stackoverflow.com/questions/59191118/aws-lex-human-handoff-intervene

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant