Write and publish a help article
Write, organize and publish useful help content, with clear control over public access and AI use.
On this page
Overview
The article editor at #/kb (article route) stores title, body, category, publish state, and internal vs public. Published public articles become Document-tab detail pages and RAG source text. Internal articles stay for agents only.
When to use this
Grounded Chat AI may only state facts present in retrieved allowed Fulltext + Chunk text. Thin or unpublished articles produce no_evidence instead of a guess.
Where to find the controls
#/kb list → open or create an article. Public readers use the help-center slug. Chat Document shows category → popular → detail.
Who can make these changes
elegant_support_manage_kb to write. elegant_support_view_kb to read in admin. Customers never edit.
Before you begin
Category must exist first. Feedback and search are System → Knowledge Base. After substantial edits, reindex RAG if AI is enabled so chunks match the new body.
Follow these steps
- Create article.
- Choose category.
- Write the procedure (steps, not slogans).
- Keep internal runbooks internal.
- Publish.
- Open the public URL and the chat Document detail.
- Ask Chat AI the article question and confirm citations or a no-evidence handoff.
Settings reference
Title, body, category, status, internal flag, language variants where supported, attachments only if your process stores them in the article body as links.
Example workflow
Article “Refund windows” states “14 days for unopened items.” Chat AI retrieves that chunk and answers 14 days. It will not invent a 30-day window.
Good practices
Put the factual sentence near the top; chunking works better on explicit statements than on long stories.
Important considerations
Do not paste customer PII into KB. Do not mark a draft public “just to test AI” on a production site without reviewing the text.
If something does not work
Editor 403: missing manage_kb. Public 404: permalink/slug, or article not published. AI no answer: unpublished, internal, not indexed, or retrieval_status no_evidence — offer Talk to human.