The challenge that "skip_load_history"  loads a new conversation when a new window is open (for example,when you click the link on a KB article and it opens in a new tab) is actually the result of URL Navigations.

 

**There is a flag as of Vancounver in Conversational Interfaces to allow multiple conversations, so perhaps this plus "Load_active_only" might be a good combination - I haven't tested it yet.** 

Anyway, URL Navigations identifies what should happen when you click on a link in the chatbot.

If you navigate to a page in a portal with chat activated, it will launch window and a new chat. If you navigate to a page where chat is not activated (like displaying the KB article or opening the catalog item in a popup), the new window opens with no chat.  You still have the original window/tab open and the chat remains active, while you can review and request and then close that non-chat window. 

I documented my workaround here: https://www.servicenow.com/community/virtual-agent-nlu-forum/va-should-not-start-conversation-in-red...

 

Hope that helps @Kenn Denn , @Mike Stout , @Diana27 , @Azim3 @Community Alums