Hi Front team,
We use the Front Chat widget with our knowledge base enabled inside it, and we'd like to extend the widget's in-app Help Center experience to article links that live elsewhere in our web app.
Context on what we're doing:
We've started adding contextual tooltips throughout our web app that link to the relevant Front KB article for each feature. This has been great for helping users understand features — especially newer ones — right at the point where they encounter them.
The one bit of friction: those tooltip links open the article in a new browser tab, pulling the user out of our app. What we love about the widget's built-in Help Center is that when an article is linked inside the widget (from a chat reply, or from a link within another article), clicking it just opens the article in the Help Center tab of the widget. The user can read the full article, expand the widget for a better view, and follow along while staying in our app. That in-context experience is exactly what we want for our tooltip links too.
So concretely, today:
- A KB article link inside the widget → opens in the Help Center tab in the widget ✅ (great experience)
- The same article linked from a tooltip in our web app → opens in a new browser tab ❌ (user leaves the app)
We want any KB article we link from within our own web app to be able to open in the widget's Help Center tab instead.
What I've checked:
I've been through the Chat Widget SDK Reference. I can see show / hide, but those only control the main messenger panel — there doesn't seem to be a command to open the Help Center tab, and nothing to deep-link to a specific article.
3 questions:
- Is there any supported (or undocumented) way today to (a) open the Help Center tab programmatically, and ideally (b) deep-link it to a specific article — something like
FrontChat('openArticle', { id })or passing an article URL toshow? - If not, can this be logged as a feature request? Opening a given KB article inside the widget from our own in-app tooltip/"Learn more" links would keep users in-context instead of bouncing them to a new tab — a meaningful UX win for in-product education.
- Analytics: Since we'd be driving a meaningful chunk of our article traffic through the widget's Help Center tab, we want to make sure those views are still captured. Does an article opened inside the widget's Help Center tab count in the Knowledge base report the same way a visit to the public knowledge base page does — same "page views"/"visitors" metrics, same attribution? Or are in-widget views tracked differently (or not at all)? We rely on the Knowledge base report to measure how well our in-product education is landing, so consistent tracking regardless of entry point is important to us.
