Problem Statement:

The widget currently always opens to the Page Help tab by default, and there is no configuration setting to make the Knowledge Base tab the default or "sticky" tab instead. Customers who want users to land on, or return to, a broader Knowledge Base view (rather than page-specific help) must rely entirely on custom JavaScript to detect and override the default behavior, which is a workaround for a genuine, recurring configuration need rather than an edge case.

Suggested Enhancement:

Add a configuration option in the widget's Configure & connect settings (similar in spirit to the existing URL mapping default-behavior setting) that lets customers choose whether the Knowledge Base tab or the Page Help tab should be the default/active tab, including after the widget re-renders during a session.

Customer Benefit:

Eliminates the need for custom JavaScript for this common use case, reduces support tickets caused by custom scripts breaking during widget architecture updates, and gives customers a durable, supported way to control default tab behavior directly from widget settings.