chat-headless: implement agent handoff with support of ChatHttpClient and ChatEventClient #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
popestr
reviewed
Jul 3, 2024
popestr
reviewed
Jul 3, 2024
yen-tt
added a commit
that referenced
this pull request
Jul 5, 2024
bump headless version for this feature: #51 update ChatHeadlessProvider to accepts `clients` param as a passthrough to headless J=CLIP-1328 TEST=manual tested through test-site with chat-core-aws-connect as agent client
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ChatHeadless now accepts a bot chat client and an agent chat client. A Chat client can be of type
ChatHttpClient(e.g. process requests through Yext Chat API endpoints) or of typeChatEventClient(e.g. WebSocket connection for Amazon Connect integration). A chat client can initiate a handoff to the other client.J=CLIP-1286
TEST=manual&auto
see that unit tests passed
see that the behavior is as expected in test-site with chat-core-aws-connect as the agent client. upon user request, a chat session is created and successfully interact with agent. When agent closes the session, user can either reconnect by sending a new message, or after 15 minutes, resume conversation with the bot.