Chatbase vs Training on Your Whole Site: What Support Teams Should Know
Chirps Team
2026-06-02
Chatbase made it easy to upload PDFs and spin up a GPT-powered bot in minutes. That workflow is excellent for static manuals—but most SaaS and ecommerce answers live across dozens of public URLs that change every sprint. When pricing, feature flags, and policy pages drift from your uploaded files, customers get confident wrong answers.
This post compares document-only training (Chatbase-style) vs whole-site crawling (Chirps-style), with pricing context for a 3-person SaaS team and a practical migration path.
Chatbase-style document bots
Upload PDFs, paste text, connect Notion—Chatbase indexes sources you explicitly provide. Strengths and limits are two sides of the same coin:
- Strong for: API reference PDFs, employee handbooks, fixed compliance docs.
- Weak when: pricing tables, changelog pages, and marketing copy live only on the website.
- Maintenance: someone must re-upload or sync when the public site changes.
- Pricing: free tiers cap messages and sources; paid plans scale with usage and bot count—costs climb as you add products and locales.
Whole-site crawling
Chirps indexes your sitemap and public pages, then layers uploads for internal docs. When marketing edits the pricing page, you recrawl—no rebuilding decision trees or re-exporting PDFs.
- Marketing edits pricing → recrawl → bot updates answers.
- Combine crawl + PDFs for public site + private spec sheets.
- Same widget handles chat, in-chat forms, and browser voice.
Pricing snapshot for a 3-person SaaS
A bootstrapped SaaS with ~2,000 support messages/month and three teammates reviewing transcripts:
- Chatbase paid tiers: typically scale with message volume and number of chatbots; budget $40–$100+/mo as bots and locales multiply.
- Chirps Starter ($19/mo): one assistant, enough for early-stage FAQ deflection.
- Chirps Pro ($49/mo flat): 5 assistants, 5,000 messages, unlimited team viewers—no per-seat fees.
The difference is not just dollars—it is who must babysit the knowledge base. Crawl-first teams ship page updates; document-only teams file a ticket to re-upload.
Accuracy test: what customers actually see
Run this quick audit on your own site:
- List five URLs customers cite most (pricing, security, integrations, status, refunds).
- Ask your bot each question verbatim from recent support tickets.
- Compare answers to the live page—not last quarter's PDF.
Side-by-side
Document-only bot trained on a January pricing PDF says "Pro is $39" while the site shows $49 with a new annual toggle. Crawl-trained Chirps reads the live `/pricing` page and answers with current tiers—after a one-click recrawl post-launch.
Support team workflow with crawl + uploads
The best setups hybridize both worlds—exactly what growing support teams need:
- Public marketing + docs: crawled on schedule (weekly or on deploy).
- Internal runbooks: uploaded PDFs/Notion exports not on the public web.
- Custom instructions: refusal rules, brand voice, escalation triggers.
- Human dispatch: WhatsApp or SMS when the bot lacks grounded context.
Who owns updates?
Assign marketing ownership of crawl triggers (post-publish) and support ownership of uploads (new macro policies). No engineer required for either path on Chirps.
How to switch from Chatbase
- Inventory Chatbase sources: note which files are still canonical vs outdated.
- Create Chirps assistant → enter root domain → run full crawl.
- Re-upload the PDFs that are still authoritative (security whitepaper, SLA).
- Copy your Chatbase system prompt into Chirps custom instructions—tighten grounding rules.
- Embed on staging; run the same 10-question accuracy test you used on Chatbase.
- Swap embed script in production when answers match or beat Chatbase.
Webflow / marketing sites
Project Settings → Custom Code → Footer. Paste Chirps embed. Publish. Recrawl after each pricing deploy so answers stay tied to what visitors see.
When Chatbase still wins
Chatbase remains a solid pick if your knowledge is mostly static files, you want a minimal UI focused on document chat, or you prototype internal bots over a fixed corpus (policy binder, course material) with infrequent updates. Teams deeply invested in Notion-as-SOT with reliable exports may prefer Chatbase's connector story.
Chirps fits when your website is the source of truth, you need customer-facing chat with voice and lead forms, and you want flat pricing without per-seat surprises.
How Chirps compares
Neither approach magically eliminates hallucinations—grounding discipline does. Chirps biases toward live URLs + uploads, Starter at $19/mo, Pro at $49/mo with 5 assistants and 5,000 messages. You trade Chatbase's document-first simplicity for a support widget that stays synced with what customers read on your site.
Train on your whole site—not just last month's PDF
Crawl your marketing site, layer PDFs for internal docs, and embed a grounded widget. Start free, then Starter $19/mo or Pro $49/mo flat.