Publish articles once. Serve them everywhere.

What it is

Each project can publish a public help center at its own address (Business plans can use a custom domain). It lists your published articles grouped by category, searchable, locale-aware — with the chat widget one click away if an article doesn't solve it.

Structure that works

Article groups are the help center's categories. A structure that ages well:

• Getting started — first-run setup, one article per task.
• Core features — the five things 80% of questions are about.
• Troubleshooting — symptom-titled articles ("Widget doesn't appear"), not feature-titled.
• Billing & plans — limits, upgrades, invoices.

Writing articles that deflect

• Title = the visitor's words. "Can't log in" beats "Authentication subsystem overview."
• Answer in the first paragraph. The AI quotes it; skimmers thank you.
• One article, one question. Long guides split into steps deflect worse than short focused answers.
• Translate your top ten. Articles support per-locale translations; the help center and widget serve the visitor's locale automatically.

Publishing flow

1. Write in the dashboard's markdown editor (with preview and image uploads).
2. Publish — the article appears in the help center, the widget's article search, and the AI's evidence sources simultaneously.
3. Hidden-from-help-center articles stay available to the widget and AI without public listing — useful for internal-ish answers you still want deflected.

Public API

Help center content is readable without auth — build your own frontend if you like:

GET /api/helpdesk/{accountId}/articles?locale=en
GET /api/helpdesk/{accountId}/articles/{slug}

Measure it

Deflection rate (AI answers resolved without an agent) and article-included replies show up in analytics. If an article keeps appearing in suggestions but not in deflection, its opening paragraph probably doesn't actually answer the question.