We have a use case where we want to have chats started from a couple pages on our site to route to a different team, while the majority of chats on the site goes to the general chat queue. This part we were able to achieve with deploying a different chat button on those pages which routes to that other team. On that front, everything works well.
The issue we're finding though is some of our customers are moving from page-to-page while in a chat. If they go from a page where we have this secondary chat button deployed to one with the primary chat button, we lose connection with that customer.
I guess the question is: is there any way that we can maintain the chat when users navigate to a primary chat page? Maybe some way to deploy the secondary chat on a primary page so that it's hidden, but will allow customers coming from a secondary chat page to maintain their current chat?
We have a use case where we want to have chats started from a couple pages on our site to route to a different team, while the majority of chats on the site goes to the general chat queue. This part we were able to achieve with deploying a different chat button on those pages which routes to that other team. On that front, everything works well.
The issue we're finding though is some of our customers are moving from page-to-page while in a chat. If they go from a page where we have this secondary chat button deployed to one with the primary chat button, we lose connection with that customer.
I guess the question is: is there any way that we can maintain the chat when users navigate to a primary chat page? Maybe some way to deploy the secondary chat on a primary page so that it's hidden, but will allow customers coming from a secondary chat page to maintain their current chat?
