GetFoxChat for Docs sites

AI chat for your docs site that answers from your own guides and links the page

GetFoxChat adds a chat bubble to every page of your documentation. Behind it is the GetFoxChat AI operator (it starts as Foxy; rename it and give it your own avatar). It reads your public docs and answers readers from them, with the link to the page that says so.

See it on your docs site

First month free, 100 conversations.

What the chat operator does on your docs site

It learns from the public pages: guides, tutorials, API reference pages, FAQs and troubleshooting pages. It finds them through the sitemap and the links on the homepage. Developers and readers ask things like:

“How do I authenticate with an API key?”“Is there a rate limit?”“Where is the webhook reference?”“Why am I getting a 401?”

It answers developers and readers in a chat bubble on every page, from what the site's own pages say, in the language the visitor writes in.
It points to the page that has the answer, and when that link is on the page the visitor is looking at, it highlights it.
When your pages don't have the answer, it says so and passes the conversation to you instead of guessing.
There is a Talk to a person button in the chat. When someone on your team is online, they reply from the GetFoxChat inbox; when nobody is, the visitor can leave an email address so you can follow up.
Asked whether it is a person, it says it is an AI assistant.
It comes with a default name and avatar; rename it and change the avatar anytime, and visitors see the name you pick.

Where it fits on a docs site

Finding the right page

Readers often know what they want but not what you called it. The operator answers in their words and links the page that has the detail.

Questions spread across pages

Some answers sit across a guide and a reference page. The operator answers from what those pages say and links them.

Gaps in the docs

The What visitors asked view shows the questions your docs could not answer, so you know which page to write next.

What it does not do

It answers from your published docs. It does not run code, see a reader's account or keys, or know about features your docs don't describe. When a question needs an engineer, it hands the conversation to your team.

An example on an API reference page

A developer on your authentication guide asks why their requests come back with a 401. Your troubleshooting page lists the common causes, so the operator answers from it and links the section. The developer then asks for a code sample in a language your docs don't cover. The operator says your docs don't include one and points to the closest page, rather than writing code your docs don't contain.

Pages that help it answer well

The operator can only answer from what your pages say. These are the pages that make the biggest difference on a documentation site:

One page per task, with a clear title in the words readers use
A troubleshooting page that lists error messages and what they mean
A sitemap that includes every docs page, so none are missed
A page on limits: rate limits, quotas and plan differences if you have them

Questions docs teams ask us

Does it run or test code?

No. It answers from your published docs and links the page it used.

Can it answer from docs behind a login?

It learns public pages. Pages that need a login are not read.

How do we find what the docs are missing?

The What visitors asked view groups readers' questions and shows the ones your docs could not answer.

Also in GetFoxChat

WalkthroughsRecord a task once; the operator plays the steps in the chat when asked.

Returning visitorsIt remembers what a visitor said before, on the same browser.

Spam and botsSpam and bot messages are filtered before the operator answers.

What visitors askedSee what visitors asked and what your pages didn't answer.

Every feature is on every plan; Starter and Pro cover one site and differ in conversations a month, Agency covers up to five sites and removes the GetFoxChat branding. See pricing for what each plan includes.

See it on your docs site first

Type the address. GetFoxChat reads the public pages and opens a preview of the operator answering from them. No account, nothing to install.

Like it? Press Keep it on my site in the preview. You get a free account with the site already set up.

Put it on your docs site

One line of code before the closing </body> tag. Create your free account, add the address, copy your snippet, then press Check my site.

The line looks like this. Yours has your own site ID in place of YOUR_SITE_ID:

<script src="https://getfoxchat.com/widget.js" data-site-id="YOUR_SITE_ID" defer></script>

Step-by-step guides for Shopify, WordPress, Wix, Squarespace, Webflow and other platforms.

Add GetFoxChat to your docs site

See it answering from your own pages first. No account needed.

First month free, 100 conversations.

See it on your docs site Start free See pricing