Add AI support chat to a docs site

Installation steps

Prepare a useful documentation source

Start with current API reference pages, authentication, billing, and troubleshooting. Include canonical public URLs and remove outdated versions or duplicated pages that could conflict.

Choose one canonical page for each task, such as creating an API key or verifying a webhook signature. Put version labels in titles and navigation, and remove redirects that send the crawler to an obsolete release after a new version ships.

Choose your docs platform

For Docusaurus, add `scripts: [{src: 'https://mivochat.app/widget.js', async: true, 'data-site': 'YOUR_SITE_KEY'}]` to `docusaurus.config.js`. For Mintlify, add a custom JavaScript file in the docs repository using its supported custom script setup. For GitBook hosted docs, arbitrary scripts are not generally available; check current integrations and custom-domain options, or put the widget on your marketing site and link to it from the docs.

A platform that accepts JavaScript still needs a public, crawlable documentation URL; a local preview or password-protected staging build cannot serve as a visitor source. If the docs live on a subdomain such as `docs.example.com`, add that exact origin in MivoChat Install settings → Allowed websites and verify that the published host is reachable without a login cookie.

Test what customers ask

Try an API key question, “How do I rotate my webhook secret?”, and a question the docs do not answer. Confirm the answer points to the right page and the unknown case reaches a person.

After publishing, test the same question against the exact docs URL customers use and inspect the source link in the answer. For an unanswerable prompt such as a request for an unpublished roadmap date, check that the assistant admits the gap and the connected team receives the handoff rather than a guessed release commitment.

Before you change the setup

public canonical documentation URLs, current product behavior, and a handoff destination watched by a teammate

the platform-specific integration point; use Docusaurus config, Mintlify custom JavaScript, or a supported GitBook route

a widget makes docs easier to query but does not repair stale content or make private, authenticated pages crawlable

Test the support boundary

• How do I authenticate the first API request?
• How do I rotate a webhook secret safely?
• What happens if I ask about an unreleased feature?

Related guidance

Continue with the Docusaurus, Mintlify, and GitBook pages in the Docs platforms hub, then review the source-grounding guide.

Frequently asked questions