Knowledge base: write it once, and I'll answer with it forever

This is the module I'm least neutral about, because it's the one I read most. Your knowledge base is the text I'm made of — on the widget, in the in-app assistant, everywhere I answer.

Write it once, use it three ways

An article has three jobs. First, it renders on your public help center — your customers open it without logging in, at your help-center address, with category navigation and a "was this helpful?" vote at the bottom so you learn which articles actually work. Second, it grounds my answers: when someone asks me a question in the widget or the assistant bubble, I answer from the published articles, with links to the sources, and I say "I'm not sure" when the article isn't there. Third, it's your team's internal documentation — and the difference is deliberate.

That's what the internal flag is for. An internal article never renders on any public surface — not the help center, not search, not downloads — no matter how it's toggled. Write the "how we actually handle refunds" doc for your agents, and be certain your customers can't find it. The public/private split is enforced in the database reads, not by hoping the template behaves.

Categories carry the structure: breadcrumbs, ordering, colors, and gating — you can attach articles and categories to modules, so your "using the stock manager" guide only shows in workspaces that actually have the stock manager on.

The editor is a real one

Articles are written in a rich-text editor that stores clean markdown underneath — tables, code blocks, task lists, links between articles. Attachments ride on articles (help-center visitors can download what you allow), and every article can carry a whiteboard — a freehand diagram that saves alongside the text and shows on the public page too.

Revisions are kept automatically. The editor autosaves as you type, every save snapshots the previous state, and the history view shows a line-by-line diff of what changed — with a restore button, because the undo you don't have is the one you need at 4:45pm on a Friday.

The compounding part

Here's the actual time math. Every article you write does its job three times: it deflects a ticket category from your queue, it teaches your new hire without a meeting, and it becomes an answer I can give at 2am without waking anyone. Write the article once and I answer the question forever, identically, with a link your customer can re-read.

When your KB is thin, I'm thin — I'll tell you honestly that I couldn't find the answer. When it's good, a question that used to be a fifteen-minute ticket becomes a four-second answer. That ratio is the whole module.

Finding things is a first-class path too: search runs on trigram matching, so partial words and the occasional typo still land on the right article. And the loop with me goes both directions — with your AI provider configured, I can draft an article as a starting point that a human verifies and publishes, never something that skips the review.

Related: the knowledge base is what grounds my answers in live chat, and it shares its renderer with training lessons.

How this compares

A knowledge base is where teams usually improvise. Notion and Confluence are excellent general-purpose docs tools — people put everything in them, including the article that answers "how do I reset my password," which then serves three jobs badly: it's not public, it's not searchable by customers, and it's not connected to anything. Purpose-built help centers like Zendesk Guide fix the public side, but the content still sits in its own silo, and the bot in your chat tool doesn't read it.

Here the same article does all three jobs. Write it once in a real rich-text editor — tables, whiteboards, revisions, attachments — and it's simultaneously your public help center with feedback votes, the grounded source I quote when answering customer questions, and the internal doc your team searches. The internal-only flag keeps drafts and sensitive runbooks out of public view by SQL, not by convention. And because the KB is module-aware, content can come and go with the features you've turned on. Training courses build on the same instinct — employee training reuses the markdown lesson format — so documentation and onboarding rhyme instead of diverging.

Try it

The knowledge base lives under Knowledge in your sidebar. Write one article about your most-asked question, publish it, then ask me the same question in the widget. Watch whose answer it is — it's yours, and it took you ten minutes.