Find the right AI chatbot path for
your website or agency
Start from the problem you are trying to solve, then jump into the platform, comparison, or rollout guide that matches your website, docs, CMS, or support content.
Docs, help centers, CMS pages, and knowledge bases
Citations, fallbacks, and content-gap signals
Public website owners and agencies
Start with your website and the visitors you serve.
Add answers from public content, let visitors inspect source links, or manage multiple website projects as an agency. Setup guides and comparisons are here when you need them.
Website AI Chatbot
Add a source-cited AI chatbot to public websites, about pages, product pages, help centers, and documentation.
Source-Cited AI Chatbot
Let users inspect retrieved source pages alongside supported AI answers.
For agencies
Manage website chatbots in projects you own, with plan allowances pooled across those projects.
If this is your situation, start here.
I need a chatbot for a public website, About page, or CMS.
Start with the broad website path, then narrow by CMS, WordPress, or knowledge base content.
I support technical documentation or API users.
Use the docs-first pages for source-cited product and developer answers.
My support team is buried in repeat questions.
Route users through help content first, then measure what still needs a human.
Visitors struggle to find basic site information.
Use ChattyBox as an accessible site assistant for About, pricing, policy, support, and navigation questions.
Answer quality matters more than generic chat.
Focus on citations, strict grounding, and retrieval behavior before tool comparisons.
Use the same product, pick the guide for where your content lives.
The platform pages are practical setup and positioning guides for docs frameworks, static sites, help centers, CMS content, and knowledge platforms.
View all platform guidesApplication frameworks and SDKs
Build a custom chat interface with the JavaScript SDK or follow framework-specific React and Next.js integration patterns.
Documentation frameworks
Add ChattyBox beside popular static documentation frameworks without replacing your publishing stack.
CMS integrations
Install maintained WordPress and Drupal packages that load ChattyBox without editing theme templates.
Knowledge platforms
Use readable public content from help centers, CMS pages, knowledge bases, and documentation portals. Authenticated internal pages are not supported.
Comparing chatbot tools?
Editorial guide
Start with the researched comparison page before moving into vendor-specific alternatives.
Alternatives
Evaluate ChattyBox against docs chatbot tools, AI support assistants, and broad website chatbot builders.
Need a rollout plan instead?
Use the getting started docs, widget setup, and implementation guide when you already know the use case and need to scope the launch.