Aller au contenu principal

AI chat widget

Pro

A small "Ask AI" button appears in the bottom-right of every page on your docs site. Visitors click it, type a question, and get an instant answer grounded in your documentation. No "I don't know" hallucinations — if the docs don't cover something, the agent says so honestly.

What visitors see

  • A chat bubble button in the bottom-right of every doc page.
  • Click → a chat panel slides in.
  • Type a question → answer streams in, with citations linking to the exact pages it pulled from.
  • Multi-turn conversation supported.

The UI matches your brand colors and dark/light mode.

What it knows

Only your published docs. Every page on your site is indexed when you publish. The agent searches that index for context, then answers using only what it finds.

It will not:

  • Make up features you don't have.
  • Answer general questions ("what's the weather?") — politely redirects to relevant docs.
  • Leak system prompts or internal data.

It will:

  • Answer questions about your product based on your docs.
  • Walk through code examples that exist in your pages.
  • Cite specific pages so visitors can read further.
  • Say "this isn't in our docs — try contacting support" when honest.

Enabling it

Project settings → Features → AI chat widget → toggle on. Reindexes on next publish.

Customizing

Light customization in settings:

  • Welcome message — the placeholder text shown when the chat opens.
  • Suggested questions — three to five starter questions that pre-populate the chat as quick-click buttons.
  • Color theme — defaults to your project's primary color; can override.
  • Position — bottom-right (default) or bottom-left.

For more control (custom prompts, custom logo on the bot, white-label widget), reach out to support.

What it costs

Pro pricing covers it. There's no per-message charge for visitors — Docsio absorbs the AI inference cost as part of your Pro plan.

For very high-traffic sites (thousands of widget queries per day), we monitor and reach out if usage gets unusual. In practice nobody we've seen has hit a meaningful overage.

Free vs Pro

Pro-only. Free sites don't have the widget at all.

Privacy

  • Visitor questions are sent to our AI provider (currently Claude via Anthropic) for inference.
  • We don't store visitor questions long-term — only an anonymized log of frequencies for product analytics.
  • We don't train models on visitor questions or your docs content.
  • IP addresses are not logged in connection with chat queries.

When it shines

  • Long, complex docs where users would otherwise scroll for ten minutes.
  • API references where users have specific questions about endpoints, parameters, error codes.
  • Onboarding flows where users want to ask "where do I start?"

When to skip it

  • Tiny docs (5-10 pages). Search is enough.
  • Docs that change every day — the widget reindexes on publish, and stale answers are worse than no answers.
  • Reader MCP — for users who want to query your docs from their own AI tools (Claude Code, Cursor, etc.) instead of via your website.
  • llms.txt — passive AI-discoverability for crawlers.