I have got a (oneway) working implementation using RocketChat as the centralized router. It is early days, but so far it has been really good since RocketChat has been designed as an omnichannel router. I don’t need to think about routing, and queuing users to speak to live (human) agents,
It is transferring to a human all well through a custom action that calls the API endpoint specified by the app, but I am still figuring how to transfer it BACK to the bot.
When I get a properly working implementation I’ll definitely write it up since this seems to be a really common struggle, and there is hardly anything comprehensive I could find for Twilio/WhatsApp.
@manoj_kumar
I have not been working on the handoff for a while now. I am unable to share exact codes due to org restrictions. However, I can help you with your implementation. You can reach out directly or I can collaborate on a shared GitHub repo.
Also interested in your implementation here. I am trying to do the same thing, where the customer is using SMS and the live agent is using Slack. Would also like to log all the messages from user and bot into the Slack channel so the live agent can see the whole history.
If you are available to consult, I would be very glad for it.
Hello @arpitd143. Got a little sidetracked on this project, and this took the back burner for a little bit. As I mentioned this is only a (slightly hacky) one-way transfer from Twillo (so WhatsApp & SMS) to RocketChat. Got the vise part but versa figured out. I check if I have called ‘action_default_fallback’ twice in a row, and if that’s the case (and the input channel is WhatsApp), I then call this method :
You get the ‘url’ by downloading the app to your rocketchat server and clicking the settings. Admin–> Settings → App. The detailed steps are here. Make sure you have the bot working first on rocket chat, and then give it the role of ‘live chat agent’. It is finicky to set up. I am still working on it. Once I do I plan on writing up a tutorial since RocketChat takes care of a lot of live-agent routing on their end, and might serve as a great OmniChannel Human Handoff platform.
Hello Stephens,
I understand your proposed solution. However, getting the client UI to switch is not possible, especially when we are developing it for MS Teams. Do you have any other approach?