Help Center

Overview of the help center: where it appears (web, widget Help tab, Quinn), how to turn it on, and links to setup, categories, articles, search and custom domains.

JM
James Morton
Written By James MortonLast updated 1 day ago

The help center is a searchable knowledge base where you publish articles, grouped into categories, for customers to read on the web and inside your app. This article gives workspace admins an overview and links to each setup step.

Where it lives

  • On the web: at /hc on your workspace's address (for example https://feedback.yourcompany.com/hc). Self-hosted installs can also serve it from its own hostname, such as help.yourcompany.com.
  • In your app: in the Help tab of the widget, so customers can search and read articles without leaving your product. See In-app help below.
  • To Quinn: Quinn, the AI agent, answers customers from your published articles. See Knowledge sources.

The help center is a module. Turn it on in Admin > Settings > General, under Modules. See Set up your help center.

Get started

Customize

In-app help

Customers can use your help center inside your app through the widget:

  1. Install the widget (see Install the widget).
  2. In Admin > Settings > Widget, turn on the Help tab ("Browse and search Help Center articles"). The tab is only offered when the Help Center module is on.
  3. Optionally, open help from your own buttons or links with the widget SDK:
Quackback.open({ view: "help" });                     // the Help tab
Quackback.open({ view: "help", query: "pricing" });   // Help tab with a search
Quackback.open({ articleId: "getting-started" });     // one article, by id or slug

From an article in the widget, customers who are still stuck can ask your team a question when Messenger chat is on.

Manage content with AI tools

AI agents and scripts can create, update and publish articles through the MCP server (help center tools need the write:article scope) or the REST API. See the MCP tool reference.

Was this helpful?

Your feedback shapes what we write next.