One source of truth for every answer you give.

Your flows answer from it mid-conversation, SupportBuddy drafts your team's replies from it, and you can publish it as a help centre customers read for themselves. Correct a page once and it is corrected in all three.

Request a demo Read the docs

A published help centre, with its categories and a search box

Everything your answers come from.

What your team writes, and what you already have lying around, in one indexed place.

The wiki

Pages and categories your team authors and owns, in a structured editor. This is the part that can go public, and the part worth writing carefully.

Everything else

PDFs, synced web pages and pasted text. These are indexed for answering and stay internal. They are not published to a help centre.

Collections

Group sources so a flow can be pointed at exactly the documents that apply to it, rather than everything you have ever uploaded.

The same pages answer inside the conversation.

A customer who does ask a question gets the answer from the documentation you already wrote, without anyone copying it into a script.

Any step can search it

Put a knowledge step anywhere in a flow. It searches your documents and hands the result back to the flow, which decides what to say next.

Scoped to what applies

Point a step at one collection so a billing question is answered from billing documents, not from everything you have ever uploaded.

Drafts for your team

When a conversation reaches a person, SupportBuddy has already written a first reply from the same documents, inside UniversalInbox or inside Intercom.

Grounded in what you wrote

Answers come from your documents rather than from a model improvising. Correct the page and the answer changes with it.

And customers can read it for themselves.

Publish a wiki and it becomes a public site under your organisation, with its own address, your logo, your categories, and a search box covering every published page.

An article on a published help centre, with its category breadcrumb

Organised the way you wrote it

Categories and pages carry over from the wiki, so the structure your team maintains is the structure a customer navigates. Breadcrumbs on every page.

Searchable

Keyword search across every published page in that wiki, so someone who does not know where to look still finds the answer.

Findable

Each wiki gets its own sitemap and page metadata, so search engines index your answers and people arrive already knowing what you do.

Public or unlisted

Publish openly, or keep a wiki unlisted so it is reachable by link and left out of search. You choose per wiki.

Edit the page. Everything else follows.

There is no second copy to keep in step. Saving a page re-indexes it for answering, and if that wiki is published the help centre serves the new version.

Request a demo Read the docs

Synced pages refresh. A URL source is re-scraped, so a page you do not own still stays current.

Unpublishing is immediate. Take a wiki off the public web and the help centre stops serving it.

Included on every plan. Publishing a help centre costs nothing extra, on Free as well as paid.

Curate it with an AI agent, or from your own code.

Adding sources, refreshing synced pages and searching the base are tools an AI agent can call over MCP, or your own script over a REST API, so keeping the knowledge current can be automated too.

Add and refresh sources

An AI agent creates collections, adds URL and website sources, and re-syncs or reprocesses a document when it changes, within the scopes you grant its token.

Search it from anywhere

The same search your flows use is a tool, so an AI agent or a script can ask the knowledge base a question and get back the passages it would answer from.

Read the Agent Gateway docs