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

Rocketchat needs to handle escalated sessions in whatsApp conversations. #1363

Closed
ear-dev opened this issue Feb 22, 2023 · 5 comments
Closed
Assignees

Comments

@ear-dev
Copy link

ear-dev commented Feb 22, 2023

Issue:
The twilio integration we use for whatsApp sessions routes always to the defined Dialogflow department in Rocketchat.

Fix:
Can we track if a particular session is in an escalated state, and when messages from twilio enter the integration can we bypass the configured default department (Dialogflow) and route to the SF department instead? All the while maintaining session state/integrity.

@ear-dev
Copy link
Author

ear-dev commented Feb 22, 2023

Hi @bhardwajaditya can you look at this story please and let me know what you think? I'd like to know if we can come up with a design that we could implement for this.

It's possible that the whatsApp bots could stay on Rocketchat for a while, and some of our european businesses seem interested in liveagent chat escalation in whatsApp. It would be nice if we can offer that. Thanks.

@bhardwajaditya
Copy link

@ear-dev I will look into this and get back with the answer by tomorrow meeting

@ear-dev
Copy link
Author

ear-dev commented Feb 23, 2023

@bhardwajaditya can you please describe your design for this here. Basically we want to spec the work and understand where and what the changes to accomodate this will be.

@ear-dev
Copy link
Author

ear-dev commented Feb 28, 2023

@bhardwajaditya please add your design diagram here.

Lets go ahead and implement.

@bhardwajaditya
Copy link

SMS_Flow drawio

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

2 participants