Can we configure Connect support to work with Next Experience?Issue If it is not possible to configure Connect support to work with Next Experience, is there a way to configure it so to have four different virtual agents that work independently?ResolutionConnect Chat and Connect Support are not supported if you activate Next Experience:https://docs.servicenow.com/en-US/bundle/sandiego-platform-user-interface/page/administer/navigation-and-ui/concept/next-experience-adoption-paths.html Each user can only have one active conversation in the system. You can change the look and feel of the Virtual Agent Web Client separately for different portals but you still see the same active conversation when you switch between those portals. So, in reality, there will be only one Virtual Agent instance in the background. To achieve the setup with four different Virtual Agents and four different groups:1- You can create 4 AWA queues with different conditions. You can set up the conditions based on the portal. For instance, if the chat is initiated on the Service Portal (portal is sp), use this queue. If the chat is initiated on the ESC portal (portal is ESC), use another queue. Our system passes the portal parameter automatically.2- You can set up the Virtual Agent for 4 different portals. This allows them to provide separate entries for each group. Our system automatically sets the "sysparm_portal" parameter in the URL and passes it to the Virtual Agent and AWA as mentioned in the previous step.