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

Seamless switching in between specialty bots #695

Closed
ARUNIMA1314 opened this issue Feb 21, 2024 · 3 comments
Closed

Seamless switching in between specialty bots #695

ARUNIMA1314 opened this issue Feb 21, 2024 · 3 comments
Assignees

Comments

@ARUNIMA1314
Copy link

Currently, in order to switch from one specialty bot to another, first we need to type in a phrase like exit, quit or bye, and then, type in a triggering phrase to start routing to another bot. This is a little inconvenient since users most likely wouldnt chat with a chatbot and type exit and then ask queries for another category. I tried to achieve seamless switching by adding a exit_routing intent in my specialty lex v1 bots and adding a fulfillment lambda in that intent, so that whenever the user enters an utterance matching with that intent, the routing is stopped and also that utterance would work as a triggering phrase to start routing to another bot. I'm able to stop the routing in the current bot but routing to the other bot is not working. How can I do this?

@dougtoppin
Copy link

dougtoppin commented Feb 21, 2024

@ARUNIMA1314 We will discuss and get back to you on this.

@fhoueto-amz
Copy link
Member

We will analyze this for prioritization and keep you updated.

@abhirpat
Copy link
Member

abhirpat commented Jun 7, 2024

Hi @ARUNIMA1314, this issue should be addressed with the latest release v6.0.0 from changes in #726. To provide you with additional details of this mechcanism, if you notice on line 475, the dialog state of Fulfilled or Close will exit and provide welcomeBackMessage message. I'd recommend to try this functionality in 6.0.0 and let us know if you still have any questions or concerns. For now, I will archive this issue.

Please refer to CHANGELOG for additional details about this release. Thank You!

@abhirpat abhirpat closed this as completed Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants