Skip to content

Website vs Knowledge Base chatbot

Denser is one platform that adapts to two common setups. You don’t pick a fixed “type” up front — you choose which data sources to connect and how you deploy. Most users land in one of these two patterns.

Website chatbotKnowledge base chatbot
Primary sourcesWebsite crawl (URLs, domain, sitemap)File uploads, Google Drive
Typical accessPublic — embedded on your sitePrivate — internal to your workspace (can also be public)
Best forCustomer support, lead capture, pre-salesInternal knowledge, document Q&A, research
Where it livesEmbed widget, WordPress, ShopifyDashboard, Slack, or embedded internally
KB HealthOptionalRecommended — catch contradictions across docs

Point Denser at your website. It crawls your pages, indexes them, and answers visitor questions with citations back to the source page. You then embed it as a widget so it’s available to everyone who visits.

Website chatbot embedded as a widget on a live site

Choose this if you want to:

  • Deflect repetitive support questions with 24/7 answers
  • Capture leads mid-conversation
  • Help visitors find the right product or page

Upload your documents — PDFs, Word, Excel, slides — or connect Google Drive. Denser builds a private knowledge base your team can ask questions against. Keep it internal, or publish it when you’re ready.

Knowledge base chatbot answering from uploaded documents with citations and a PDF source preview

Choose this if you want to:

  • Give your team instant answers from internal docs
  • Search across many documents at once
  • Keep contradictory or outdated content in check with KB Health