From a published doc to a cited answer.
Publish your docs to a hub
The guides and SOPs you publish are the only things Doc can draw on. A draft is invisible to it until you publish.
The chat is live on the hub
Every hub has one. A reader opens it without an account and asks in their own words.
Doc answers, with its sources
The answer names the guide and step it came from, and it is clearly marked as AI-written.
No answer beats a wrong one
When the docs genuinely don't cover the question, Doc opens a ticket instead of guessing. The ticket lands in your Inbox, and your reply appears in the reader's thread.
It cannot make something up about your client.
Most support bots are sold on how many questions they deflect. That number goes up when the bot answers everything, whether or not it is right — which is the opposite of what you want in front of a client.
Doc is scoped to one hub's own published docs. It does not reach the internet, another client's hub, or its own earlier answers, and every answer it gives points back to the guide and step behind it. A reader can check the source, and so can you. When there is no source, there is no answer — there is a ticket.
A ceiling, set before the first question.
Every plan includes a monthly pool of Doc AI answers — the numbers for each plan are on the pricing page. On top of that pool, a daily safety ceiling per hub and per visitor is reserved before the model is ever called, so a busy month cannot become a bill you did not expect. You can tell a client what their hub costs and be right.
The monthly pool is what your plan includes; the daily ceiling is protection against abuse on top of it. See the pricing page for the pool on each plan.
The daily ceiling
Every hub and visitor has a monthly answer allowance.
Budget is reserved before the model runs, so a busy month cannot become a surprise bill. Current figures live on the pricing page.
See the plansAnswers inside your product, not in a support queue.
The chat lives on the hub by default, and it can also sit inside your own product. Drop in one snippet and readers ask where they already are, in their own words, against the same published docs.
Doc AI is the default name in the chat. Give it your own name per hub in branding — the name changes, and the disclosure does not. Whatever it is called, it still answers only from that hub's docs, still cites the guide and step, and is still marked as AI-written.
Two embeds, not one
The chat is one embed. A single guide is the other: place one guide — as an Article, as Slides, or as the auto-advancing Movie — into a page that is not a hub, with a snippet. Your product's own help page, an intranet, or a Notion page can hold the guide itself, still edited in one place here.
Connect your docs to Claude
Docssier also exposes your published docs over an MCP connector, so Claude and other AI clients can read them. Point your AI tool at the connector and it can look things up in your guides and help you keep them tidy — working from the same published docs the chat answers from.
Ask the one that runs on Docssier.
Docssier's own help center at help.docssier.com runs this chat against real docs. Open it, ask it something a guide covers, and watch the citation. Ask it something no guide covers, and watch it open a ticket instead of guessing.
Questions about how it answers.
Ready to write it once?
Capture a process, publish it as a help center under your own name or a client's, and answer the repeat questions from what you published.