First off, thanks for SupportApp — we've deployed it across our macOS fleet via Jamf Pro and it's been a great help-desk tool.
Summary
It would be great to have the ability to open an embedded web/chat window inside SupportApp itself, rather than only launching an external app or URL.
Use case
We'd like to add a button (e.g. "Support Bot") that, when clicked, opens a web view hosted within SupportApp pointed at an internal, self-hosted support assistant via a configurable URL. The goal is to keep the support experience contained within the SupportApp UI instead of sending users out to a browser, so the interaction feels native and stays within the corporate support surface.
Current limitation
Today the Button ActionType supports App, URL, Command and PrivilegedScript. A URL button opens the default browser, and there's no way to render web content inside the app. As far as I can tell, an embedded view would currently require forking the Swift source, which isn't really maintainable for a managed fleet.
Proposed solution
- A new
ActionType (e.g. WebView / EmbeddedURL) or a new Item Type that opens a sandbox-safe WKWebView panel within SupportApp.
- A configurable target URL via the existing
nl.root3.support preference domain so it can be managed entirely through a Configuration Profile.
- Optionally, sizing/title configuration for the window.
This would let organizations link SupportApp directly to their own internal chat/support assistants without leaving the app. Happy to provide more detail or help test a beta if useful.
Thanks for considering it!
First off, thanks for SupportApp — we've deployed it across our macOS fleet via Jamf Pro and it's been a great help-desk tool.
Summary
It would be great to have the ability to open an embedded web/chat window inside SupportApp itself, rather than only launching an external app or URL.
Use case
We'd like to add a button (e.g. "Support Bot") that, when clicked, opens a web view hosted within SupportApp pointed at an internal, self-hosted support assistant via a configurable URL. The goal is to keep the support experience contained within the SupportApp UI instead of sending users out to a browser, so the interaction feels native and stays within the corporate support surface.
Current limitation
Today the Button
ActionTypesupportsApp,URL,CommandandPrivilegedScript. AURLbutton opens the default browser, and there's no way to render web content inside the app. As far as I can tell, an embedded view would currently require forking the Swift source, which isn't really maintainable for a managed fleet.Proposed solution
ActionType(e.g.WebView/EmbeddedURL) or a new ItemTypethat opens a sandbox-safeWKWebViewpanel within SupportApp.nl.root3.supportpreference domain so it can be managed entirely through a Configuration Profile.This would let organizations link SupportApp directly to their own internal chat/support assistants without leaving the app. Happy to provide more detail or help test a beta if useful.
Thanks for considering it!