You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 ?
@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.
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
The text was updated successfully, but these errors were encountered: