Zum Hauptinhalt springen

Add the AI chat widget to your docs

Pro

The AI chat widget is a small floating button on your docs site. Visitors click it, ask a question in natural language, and get an answer grounded in your published content — with citations to the source pages.

What visitors see

A pill in the bottom-right of every page: Ask AI with a sparkle icon. Click expands to a chat panel:

  • The visitor asks: "How do I set up a webhook for new orders?"
  • The widget searches your docs, picks the 3–5 most relevant pages, and uses them as context.
  • The AI responds with a paragraph or two of answer + a list of cited pages ("Sources: [Webhooks overview], [Configuring events]").
  • The visitor can click any citation to jump to the canonical page.

It's not a replacement for the docs. It's a faster path to a specific answer for visitors who'd otherwise have to skim multiple pages.

Enabling

Project settings → Features → AI chat widget → toggle on. Pro plan.

Customize:

  • Trigger label — defaults to "Ask AI". Some teams prefer "Search docs" or "Ask docs"; the visual is the same.
  • Position — bottom-right by default. Move to bottom-left or top-right if it conflicts with your own site chat.
  • Initial prompts — three suggested questions visitors see before they type. Use these to highlight things people ask most. ("How do I add a custom domain?", "What's the difference between free and Pro?")

What to expect

The widget answers based on what's in your llms.txt plus the full text of every public page. So:

  • It can answer anything that's documented. If your docs say it, the widget will surface it.
  • It will say "I don't know" when the answer isn't in your docs. That's a feature, not a bug — bad answers are worse than no answers. The widget never makes up product behavior.
  • It respects published-only content. Drafts, hidden pages, and password-protected sections don't get used as context.

What to do with the analytics

Project settings → Analytics → "Chat queries" tab. Three things worth checking weekly:

  1. Top queries. What people ask most. If "how to install" is a top query and you don't have a clear install page, you have writing to do.
  2. Queries with no good answer. The widget tags queries where confidence was low. These are usually gaps in your docs — write the missing page.
  3. Click-through rate to citations. If visitors get an answer and never click into your docs, your widget answer is doing real work. If they always click through, it's a navigation aid more than an answer engine. Both fine, just useful to know.

What we don't do

  • We don't enable the widget on free. Generative AI on every visit isn't free for us; we cover the cost only on Pro.
  • We don't let visitors continue conversations across sessions. Each session is independent. (We've heard the request; it's a v2 question of how to handle privacy + storage.)
  • We don't replace human support. The widget includes a "Still stuck? Email support" footer that links to your support contact (configured in project settings → Help).