No add-on tiers, no enterprise gates, no fine print. The full FoxChat capability set ships in every plan from the $29 Starter. Here is every piece, end to end.
The FoxChat widget is the visible part of the system: a small bubble that lives in the corner of your site, opens to a clean chat surface, and stays out of the way until a visitor needs it. The bubble itself is named The FoxChat AI Operator (you name it yourself). The widget is a single script tag. There is no React, no iframe acrobatics, no SDK installation. You paste the line into your page template, and your AI operator starts answering questions on the next page load.
The widget renders on top of your existing site without touching its layout. It respects mobile breakpoints, picks up your brand colours automatically the first time it loads, and uses your page font when you have one defined. Visitors can drag the bubble out of the way of a sticky CTA, and the position they choose is remembered for that browser. If your site already runs a heavy script bundle, the widget defers its own load until idle so it does not steal first-paint budget.
Out of the box the widget is fully keyboard navigable, screen-reader labelled, and works without JavaScript-driven layout. If JavaScript fails to load the widget simply does not appear — nothing else on the page breaks. The whole capability surface, from greeting copy to escalation routing, is configured from your FoxChat dashboard, not from the script tag, so you never have to touch the embed code again.
The brain is what makes your AI operator useful. When a visitor asks a question, your AI operator retrieves the most relevant passages from your help content, your product pages, and any documents you have uploaded, and answers in plain language with the source still attached. The retrieval is hybrid: a semantic search ranks passages by meaning, and a full-text search catches the literal words a visitor typed. Both signals are blended before the answer is generated, which is why your AI operator keeps answering correctly when visitors paraphrase or misspell.
Your AI operator reads your help centre and answers from it. It does not invent product features, prices, or policies that are not in your content. When the retrieval score is too low to answer confidently, your AI operator says so and offers to take a message or hand off to a human, instead of guessing. The confidence threshold is configurable per site, and every answer carries a small footer that shows which passages were used so you can audit it later.
The brain also keeps short-term memory inside a single conversation. If a visitor asks about pricing in turn three and asks about cancellation in turn five, your AI operator still knows it is the same person, the same site, the same context. That memory rolls forward across sessions for up to ninety days on Pro and indefinitely on Agency, so a returning visitor does not have to restart the conversation from scratch.
Every conversation your AI operator has is logged in the FoxChat inbox. The inbox is a single web view that pulls together messages from every site you operate, filters them by unanswered, escalated, or recently active, and lets you reply in two clicks. The visitor sees the reply in their open widget or, if they have closed it, in a small push notification the next time they return.
The inbox surfaces visitor context next to every thread: which pages they visited, how long they stayed, what they searched for, and which previous conversations they have had with your AI operator. Operators can leave private notes on a conversation that the visitor never sees, tag conversations for later review, and bulk-archive resolved threads. Search runs across the full body of every message.
Unanswered questions are the inbox feature that pays for itself. When your AI operator could not answer with confidence, the question lands in a separate queue. You answer it once, in plain language, and that answer becomes part of the knowledge base. The next visitor who asks the same thing gets your AI operator answering correctly without you in the loop. Most teams clear the queue in fifteen minutes a week and watch their answer rate climb every cycle.
Some conversations need a human. FoxChat ships with one-click takeover: while your AI operator is mid-conversation, an operator can step in from the inbox, type a message, and the visitor sees that the agent has joined. Your AI operator steps back and watches, ready to help with retrieval or summarisation if asked, but no longer driving the conversation.
Takeover is asymmetric in a useful way. Visitors do not know whether they are talking to your AI operator or to a human unless you decide to tell them. Operators see exactly what your AI operator saw — the same retrieval results, the same conversation history, the same visitor context — so the handoff is invisible from the visitor side. When the agent is done and closes the takeover, your AI operator resumes on the next message automatically, with full memory of what was said.
For teams that want the opposite, you can configure your AI operator to default to silent mode on certain pages or for certain visitor segments, so every conversation routes to a human first. The same widget surface handles both modes without any code change.
Walkthroughs are step-by-step product tours that your AI operator can play inline inside the chat window. You record one once, in your own product, by clicking through the steps you want a visitor to follow. The recorder captures the elements, the order, and the natural-language description of what each step accomplishes. Your AI operator can then trigger the walkthrough whenever a visitor asks how to do that thing, regardless of how they word the question.
Walkthroughs are resilient to UI changes. The recorder captures several anchor signals per step — not just a CSS selector but a visible label, a relative position, and surrounding context — so when your product redesigns a button, the walkthrough still finds it. When all anchors fail, the step degrades gracefully to a plain-language instruction instead of silently breaking.
Visitors can replay any walkthrough, pause it mid-step, or ask your AI operator a question without losing their place. Recording happens from a bookmarklet or a Chrome extension, so you do not need to write a single line of code to capture a tour.
If you run more than one website — an agency managing client properties, a holding company with several brands, a founder running a SaaS and a marketing site — FoxChat treats each one as a separate site with its own knowledge base, brand voice, and inbox, all stitched together in one dashboard. You switch sites from a single drop-down at the top of every page.
The Agency plan gives you five sites, white-label branding on the widget, and an operator role that lets your clients see their own inbox without seeing your account. Custom domains, per-site billing, and shared knowledge fragments across sites are part of the same surface. If you are building a productised service on top of FoxChat, the multi-site dashboard is the layer you operate from.
The knowledge base editor is where you shape what your AI operator knows. Every FoxChat site starts with a knowledge base populated automatically from a crawl of your public site: titles, headings, body copy, FAQ blocks, and any markdown or HTML you have uploaded. From there, the editor lets you edit any passage in plain prose, add new entries by typing them, mark passages as canonical or deprecated, and group them into topics that show up in the visitor-facing answer footer.
The editor enforces a simple rule that matters more than it sounds: write entries in the words a visitor would actually use. Internal jargon retrieves poorly because the semantic search compares meaning, and visitor questions rarely use operator phrasing. The editor highlights jargon-heavy entries and suggests visitor-friendly rewrites you can accept with one click.
Entries are versioned. Every save creates a revision you can roll back to. When your AI operator answers a question incorrectly, the inbox shows you which entry it used, and one click takes you to the editor with that entry preselected. The fix lands in production immediately — no rebuild, no deploy, no waiting.
Your AI operator speaks the way your brand speaks. When a site is first added, FoxChat samples a few dozen pages of your existing copy and infers a voice profile: how formal you are, whether you use contractions, how you handle technical jargon, how you greet people, what you say when you do not know something. Your AI operator answers in that voice from the first conversation.
You can override any aspect of the voice profile from the dashboard. Want shorter answers? Set a target length. Want a specific greeting? Type it. Want your AI operator to refuse to talk about a competitor? Add the rule. The voice profile applies across all answers and all languages, so a visitor in Spanish hears the same brand even if your site copy is English.
Brand voice extends to the widget itself: bubble colour, accent colour, font, corner radius, mascot replacement, and a custom display name for your AI operator if you want to call it something else. The visitor-facing surface ends up looking like a feature of your product, not a third-party widget.
Your AI operator detects the visitor language from the browser and the first message they send, and answers in that language. The detection covers more than sixty languages out of the box and works correctly on mixed-language conversations, where a visitor types one turn in English and the next in their native language. Your AI operator follows the visitor.
The knowledge base stays in your source language — usually English. FoxChat does not bulk-translate your content into every language and store the translations, because translated content drifts the moment you edit the source. Instead your AI operator translates on the fly when it answers, using the original passages for grounding so the answer stays accurate. The source-language entry remains the single canonical version you maintain.
For teams that want a manual override, you can author specific entries in additional languages and your AI operator will prefer those when the visitor is in that language. Useful for legal disclaimers, region-specific pricing, or culturally-tuned greetings that you want to control word for word.
Every visitor that opens the FoxChat widget gets a lightweight profile that follows them across sessions for as long as your plan supports. The profile collects browser, country, referring source, the pages they visited, the searches they ran, the conversations they had with your AI operator, and any structured fields you choose to capture — email, plan tier, account status.
The intelligence surfaces in three places. Inside the inbox, every conversation shows the profile alongside, so operators answer in context. Inside the KB editor, the questions your AI operator could not answer are clustered by topic so you can see which gaps in your content cost you the most conversations. And inside a weekly digest email, you get a written summary of what visitors asked about, where they got stuck, and which entries closed the most loops.
None of this is sold to third parties or shared between FoxChat accounts. The profile is your data, lives in your site, and is exportable from the dashboard whenever you want a CSV of it.
FoxChat ships today with email notifications for unanswered questions and escalations, push notifications for operators on the go, Slack and Discord channels for inbound conversation streams on Pro and above, a public API for reading and writing knowledge entries and conversations, and webhook delivery for every significant event in the system.
The roadmap for the next two quarters: native HubSpot and Salesforce pushes for captured leads, a Zapier connector for teams that wire their own automation, a Chrome extension for operators that surfaces visitor context inline on any page, and a public OAuth surface for help-centre platforms that want to sync content into FoxChat automatically. Every integration ships once and is available to every plan tier, including Starter. Nothing on the integrations roadmap is gated behind enterprise pricing.
That is the full system, end to end. The widget your visitors see, the brain that answers them, the inbox where you keep watch, the takeover that hands a conversation to a human, the walkthroughs that show people what to click, the dashboard that spans your sites, the editor that shapes the knowledge, the voice that sounds like you, the languages that follow the visitor, the intelligence that closes the loop, and the integrations that wire it into the rest of your stack. Every piece ships on every plan.
The full FoxChat feature set ships on every plan, but how the features get used depends on the kind of site you run. Each of the pages below walks through where your AI operator helps most on a specific vertical, where it stays out of the way, and the setup specifics that matter for that kind of site. Pick the one closest to what you operate and read the page that maps to your reality.
FoxChat for SaaS — signup, pricing, integration, and account questions for SaaS sites.
FoxChat for ecommerce — product, shipping, returns, and stock questions for online stores.
FoxChat for docs sites — API references, how-to guides, and troubleshooting for technical documentation.
FoxChat for help desks — deflect tickets while escalating honestly when a human is needed.
FoxChat for agencies — manage chat across multiple client sites from one dashboard.
FoxChat for info sites — answer reader questions about your full archive on content sites and publications.
No credit card required. One script tag. Works on any website.
Start your free trial