> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replybubble.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Help Center

> Publish your knowledge base as a public help site and surface it inside the chat widget

Your knowledge base isn't just for the AI — you can publish it as a public, searchable help site, and surface it directly inside the chat widget so visitors can self-serve without waiting for an answer.

***

## Enabling the help center

1. Go to **Settings**
2. Find the **Help Center** card
3. Toggle **Public help center** on
4. A URL slug is generated automatically the first time you enable it — you can customize it (lowercase letters, numbers, and dashes)
5. Your public URL is shown live as `<your-domain>/help/<slug>`, with a copy button next to it

The card's description sums it up: *"Publish your knowledge base as a public, SEO-friendly help center. Toggle individual articles live from the Knowledge Base page."*

***

## Publishing articles from the Knowledge Base

Enabling the help center doesn't publish anything by itself — each Knowledge Base document is published individually.

1. Go to **Knowledge Base > Documents**
2. Find the document you want to make public
3. Open its row menu and click **Publish to help center**
4. The document's status badge changes from **Draft** to **Published**

Use the **All / Published / Draft** filter tabs on the Knowledge Base list to see what's live. To pull an article down, open the row menu and click **Unpublish**.

An article is only publicly visible when both conditions are true:

* Its indexing status is **Active** (not Processing, Error, or Archived)
* It has been explicitly **Published**

The URL slug for each article is generated automatically from its title the first time you publish it, and stays stable after that — it isn't user-editable. Articles can optionally belong to a **category**, which groups them on the public index page; category is set via the API/KB source ingestion rather than a dashboard field.

> **Note:** Nothing in your knowledge base is public by default. Uploaded documents, crawled pages, and manually written articles all start as drafts and require an explicit publish step before they leave your dashboard.

***

## The public help site

Once articles are published, they're served at `<your-domain>/help/<slug>`:

| Page                                | URL                                    |
| ----------------------------------- | -------------------------------------- |
| Article index (grouped by category) | `/help/<slug>`                         |
| Single article                      | `/help/<slug>/articles/<article-slug>` |
| Search results                      | `/help/<slug>/search?q=...`            |
| XML sitemap                         | `/help/<slug>/sitemap.xml`             |

The index page groups published articles by category, with uncategorized articles listed last. Article content is authored in Markdown and rendered to sanitized HTML server-side — no scripts, iframes, or unsafe URL schemes make it into the page.

**Search** uses PostgreSQL full-text search (ranked by relevance) against the title and content of published articles, with a fallback to a simple title match for very short queries.

**SEO:** every workspace with the help center enabled gets a sitemap at `/help/<slug>/sitemap.xml`, and pages are served with cache headers so they load fast and index well.

If you disable the help center or a workspace's slug is unknown, all of these routes return a 404 page — published content is never exposed once the toggle is off.

***

## The in-widget Help view

When the help center is enabled, a **Help center** button appears in the widget header (it's hidden while the widget is showing an offline-mode conversation). Clicking it opens an in-widget **Help Center** view without leaving the chat.

The Help view has three modes:

* **Browse** — articles grouped by category, same grouping as the public site
* **Search** — a search box; typing at least 2 characters triggers a debounced search across published articles
* **Article reader** — tapping any article opens it inline, rendered from the same sanitized Markdown as the public site (including images, which are only allowed in this help-article context)

A **Back** button steps out of the article reader to the list, or closes the Help view entirely from the top level. If articles fail to load, the view shows a retry button rather than failing silently.

The in-widget help view is powered by the same public help-center data as the standalone site — nothing needs to be configured separately for the widget.

***

## Related articles under AI answers

When the AI answers a question using your knowledge base, and the help center is enabled, the widget can show up to 3 **Related articles** chips underneath the answer. These are derived from the same knowledge base chunks that grounded the AI's response — the highest-similarity chunk per source document, filtered down to only the documents that are actually published.

Clicking a chip opens that article directly in the in-widget Help view, so a visitor who wants more detail than the chat answer gives can jump straight to the full article.

If a chunk used to ground an answer comes from a document that isn't published (or the retrieval didn't succeed), no chips are shown for that answer — related articles never point to content visitors can't actually reach.

***

## How it fits together

The help center and the [knowledge base](/knowledge-base) share the same underlying content — a help center is really just a public, browsable view of your published KB documents. That means:

* Content quality tips from the knowledge base guide (write for questions, keep articles specific and current) apply directly to your public help articles
* Editing a document's content updates it everywhere at once: AI answers, the public help site, and the in-widget Help view
* Unpublishing or archiving a document removes it from the public site and the widget's Help view immediately, while leaving it available to the AI (unless you also change its indexing status)

***

## Summary

| Surface               | Where                               | Requires                                                      |
| --------------------- | ----------------------------------- | ------------------------------------------------------------- |
| Public help site      | `<your-domain>/help/<slug>`         | Help center enabled                                           |
| In-widget Help view   | Help center button in widget header | Help center enabled                                           |
| Related-article chips | Under AI answers in chat            | Help center enabled + answer grounded in a published document |

Enable the help center in **Settings**, publish the documents you want visitors to find on their own, and both the public site and the widget's Help view pick them up automatically.