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.
What your team writes, and what you already have lying around, in one indexed place.
A customer who does ask a question gets the answer from the documentation you already wrote, without anyone copying it into a script.
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.
Point a step at one collection so a billing question is answered from billing documents, not from everything you have ever uploaded.
When a conversation reaches a person, SupportBuddy has already written a first reply from the same documents, inside UniversalInbox or inside Intercom.
Answers come from your documents rather than from a model improvising. Correct the page and the answer changes with it.
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.
Categories and pages carry over from the wiki, so the structure your team maintains is the structure a customer navigates. Breadcrumbs on every page.
Keyword search across every published page in that wiki, so someone who does not know where to look still finds the answer.
Each wiki gets its own sitemap and page metadata, so search engines index your answers and people arrive already knowing what you do.
Publish openly, or keep a wiki unlisted so it is reachable by link and left out of search. You choose per wiki.
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.
Four questions, ninety seconds. We will bring what you told us to the call.
