When to use hidden mode
Hidden mode is a good fit for several scenarios:- Internal QA and testing workflows — Your QA team can use a shared keyboard shortcut to file bugs without a feedback button being visible to end users during a testing session.
- Consumer-facing products where UI cleanliness matters — If a persistent button would feel intrusive or off-brand, hidden mode lets you offer feedback collection without cluttering the interface.
- Embedded or white-labeled tools — When NOCK is running inside a product where you don’t want NOCK branding or any extra UI visible to the end user.
- Programmatic trigger flows — You can open the widget at a specific moment in your product’s flow (for example, after a user completes a task) without showing a persistent button.
Enabling hidden mode
1
Open Settings → Widget
In your NOCK Dashboard, click Settings in the sidebar and select the Widget tab.
2
Enable Hidden Mode
Find the Hidden Mode toggle and switch it on.
3
Save your changes
Click Save. The widget button will immediately become invisible on all pages that load the NOCK script.
Setting a keyboard shortcut
You can configure a keyboard shortcut alongside hidden mode so that pressing a key combination opens the widget.1
Open Settings → Widget
Navigate to Settings → Widget in your Dashboard.
2
Configure the Keyboard Shortcut
In the Keyboard Shortcut field, click the input and press the key combination you want to use (for example,
Shift + F or Ctrl + Shift + K). NOCK records the combination you press.3
Save your changes
Click Save. The shortcut is now active on every page that loads the widget.
Choose a shortcut that is unlikely to conflict with your application’s own keyboard shortcuts or common browser shortcuts. A combination that includes Shift or both Ctrl/Cmd and another modifier key is usually safe.
Programmatic triggering
In addition to the keyboard shortcut, you can open the NOCK widget from your own application code. This is useful when you want to surface the feedback form in response to a specific user action — such as clicking a custom button you’ve built, completing a workflow step, or encountering an error state in your UI. Refer to your Dashboard’s Settings → Widget page for the programmatic trigger details specific to your project setup. No changes to the script tag are needed.Configure the Widget
Review all widget settings including keyboard shortcut options.
Troubleshooting
Widget not opening in hidden mode? Check the troubleshooting guide.