Skip to content
FluentBot Beta
This site is under construction. Content, screenshots, and workflows may change at any time.

Use Cases

Four common setups. Pick the closest to yours — most teams mix two.

Customer support

Auto-resolve tier-1 questions from your help center. Hand off to a human when the bot can’t.

  • Escalation — visitor clicks the escalate button (or you run Human-Only mode). The chat enters a Pending → Active → Resolved flow handled in the Live Chat.
  • Live chat — real-time message delivery, agent presence, and organized agent replies.
  • Quick Questions — up to 3 preset prompts on the welcome screen to nudge visitors into self-service.
  • Feedback — thumbs up / down on every bot reply.
  • Attachments — visitors can attach files in escalated chats; agents see them inline.

Sources to add: help center URLs, sitemap, support PDFs. Start here: Create a bot → enable escalation in Widget Settings.

Sales and pre-sales

Qualify visitors on your marketing pages. Capture leads before they leave.

  • Email capture — opportunistic prompts during escalation flows; the captured email becomes the conversation handle.
  • Quick Questions — “Compare plans”, “Book a demo”, etc., as starter chips.
  • Visitor tracking — IP geolocation, browser, country surface in the Conversations page so sales can prioritize hot leads.
  • Identity Verification — HMAC-sign visitors who are already logged in elsewhere; skip the email wall entirely. See Identity Verification.

Sources to add: pricing, features, case studies, comparison pages. Start here: Embed the Widget → tune copy in Widget Settings.

Product documentation

Natural-language answers across your docs site. Every grounded answer cites its source.

  • Source citations — every answer links the document(s) it pulled from. Widget renders a Sources block.
  • Fast replies — visitors see answers quickly, without leaving the page.
  • Content gap review — unanswered questions become a backlog for improving docs.

Sources to add: docs site root URL, sitemap.xml, Markdown / PDF uploads. Start here: Train your bot — start with a Sitemap for fastest coverage.

Internal knowledge base

Private bot for runbooks, onboarding, and tribal knowledge. Team-scoped, auth-gated.

  • Team isolation — every bot, source, and document lives inside a Team. Cross-team access blocked.
  • Content Gaps — questions the bot couldn’t answer surface in Content Gaps so you can close doc holes systematically.
  • Document Usage — see which articles get cited most / never; trim dead weight.
  • Scheduled refresh — Website Links sources re-crawl Daily / Weekly / Monthly so the index stays current as docs change.
  • Identity Verification — logged-in employees land pre-identified. No email wall.

Sources to add: internal wiki sitemap, runbooks, onboarding PDFs. Start here: Create a bot → add your wiki → enable Identity Verification for logged-in employees.

Mixing use cases

Most teams run more than one bot: a public support bot, a logged-in product bot, an internal staff bot. Each has its own sources, theme, and analytics. Billing rolls up at the team level.

What’s next