01
SaaS and product sites
Check pre-sales plan and integration questions against pricing pages, onboarding questions against quickstarts, and troubleshooting against help articles; keep private account requests with support.
AI Chatbot for Sites
AI Chatbot for Your Website
Help visitors find answers in your published website, help, and FAQ content. Add ChattyBox to your existing site and let visitors open source pages for more detail.
Published website, help, and FAQ contentSource links visitors can openEmbeds with one scriptNo website migration requiredNo credit card requiredYour content stays yours
Try ChattyBox
LiveLoading the live chat…
Ask about ChattyBox. Answers use our public documentation and link to their sources.
Launch a source-cited chatbot without rebuilding your site stack
ChattyBox crawls your existing website, documentation, help center, CMS, or knowledge base, then embeds a chatbot that answers from your own published content instead of generic model memory.
One assistant for your published website, help, and FAQ content.
Source links help visitors inspect the pages used for answers.
Keep your existing website and CMS; add the widget with a script.
Content-gap tools on Pro or Business help you improve FAQs and help pages.
Workflow step
Choose published website, help, and FAQ pages that answer real visitor questions.
Workflow step
Index your sitemap or selected public URLs.
Workflow step
Test realistic questions and check answers, source links, and fallbacks.
Workflow step
Add the widget where visitors need help, without migrating your website.
Three-step launch
Paste your Website URL, test cited answers, then install the widget.
Broad website support
Put your published answers within reach
For service businesses, product sites, and help centers—not just technical documentation.
Before you launch
Start with a small set of useful public pages. Test visitor questions and check source links before adding the widget.
02
Service businesses
Help visitors find published service scope, locations served, preparation steps, and policies. Do not treat public content as live availability or a personalized quote.
03
Help centers and FAQs
Turn existing help content into a conversational support layer with citations back to the original articles.
04
Independent agencies
Choose each client’s public sources, test visitor questions, and assign a content owner. Add the widget without replacing their CMS.
Source content strategy
Start with pages that actually answer questions
Choose pages with specific, current answers. A smaller, useful source set is a better starting point than indexing every page.
Good source content
- Published help articles, FAQs, policies, tutorials, and documentation.
- Service and product pages that explain scope, pricing, integrations, eligibility, and limits.
- Pages with clear headings, specific answers, and stable URLs that can be cited.
Content to avoid indexing
- Private account pages, admin screens, internal notes, drafts, or content users should not see.
- Thin landing pages that make broad claims but do not answer real visitor questions.
- Temporary campaign pages or outdated announcements that could create stale answers.
Answer preview
Example questions a site chatbot should handle
Illustrative questions and review goals—not recorded chatbot results. Use your own pages to check answers before launch.
The pattern to look for
Ask a real visitor question, check the answer, and confirm the source cards point to pages you trust. If the source is weak, improve the page before trusting automation.Product pages
“Which plan includes the integration I need?”
Check the published integration and pricing pages; link to the relevant plan details.
Help center
“Where can I find help with this billing error?”
Look for the published troubleshooting steps and link to the help article. Keep account-specific requests with support.
Service pages and FAQs
"Which areas do you serve, and what should I prepare before a visit?"
Look for the published service area and preparation checklist, then link to those pages. Do not infer availability or confirm a booking.
Explore next
More ways to use ChattyBox
01Source-Cited AI ChatbotLet users inspect retrieved source pages alongside supported AI answers.02Documentation ChatbotTurn technical docs into a self-serve support assistant that answers with source links.03Knowledge Base ChatbotHelp visitors discover knowledge base and help center articles while keeping the source pages in view.04AI Support ChatbotUse source-cited answers for repeat public-content questions and preserve escalation for account-specific support.
FAQ
Common questions
1
Can I use ChattyBox as an AI chatbot for any site?
Use public pages with readable content in fetched HTML and a website where you can install custom scripts. The crawler does not execute page JavaScript or access private accounts. Review extracted content before testing answers.
2
Do I need a CMS plugin?
No. You can usually add the widget as a script in your CMS theme, template, tag manager, or custom HTML area.
3
Will answers cite my website pages?
Supported answers can show links to indexed source pages. Visitors can inspect details and context, but citations do not guarantee a correct or current answer and are not proof of every claim.
4
What if my pages cannot answer a question?
Retrieval and fallback instructions reduce unsupported answers, but errors are still possible. Some fallback answers have no sources. Test gaps, keep content current, and direct private account requests to your existing support channel.
5
Is this only for documentation?
No. The same workflow supports public service pages, product information, FAQs, help centers, and SaaS websites. The important requirement is useful, crawlable source content, not a particular industry or CMS.
6
What happens when CMS content changes?
Refresh crawled content after edits and review the indexed pages. Refreshes are limited by your plan’s budget and do not automatically remove omitted pages.