Skip to main content
  • Team: the main workspace container for bots, channels, data, and integrations. Open in app.
  • Bot: the AI assistant configuration that defines tone, prompt, welcome copy, and reply behavior. Open in app.
  • Channel: the connection between BoundBot and a platform such as WebChat, WhatsApp, or Slack. Open in app.
  • WebChat: the embeddable website widget managed by a public key and UI settings. Open in app.
  • FAQ item: a text-based knowledge record stored in the knowledge base. Open in app.
  • File: an uploaded document that BoundBot indexes for question answering. Open in app.
  • Website source: a crawl, sitemap, or individual URL source that feeds website content into the knowledge layer. Open in app.
  • Product: a structured catalog record with price, stock, tags, and optional variants. Open in app.
  • Action: a reusable interaction such as a button, booking flow, lead capture step, or custom API request. Open in app.
  • Workflow: a multi-step automation built in the visual editor. Open in app.
  • Keyword rule: a lightweight auto-reply rule that matches a pattern and returns fixed text. Open in app.
  • Inbox conversation: a thread created from any connected channel. Open in app.
  • Lead: captured contact or buyer-interest data collected through conversation flows. Open in app.
  • Order: a workspace-level record used for order-aware workflows and support context. Open in app.
  • Credits: the usage currency consumed by AI-generated replies.
  • MCP: Model Context Protocol; a way to connect external tool servers to BoundBot.

Documentation home

Return to the main docs entry point and choose the next workflow.

Bots

See how core bot settings map to the terms used across the product.

Channels overview

Review the channel types referenced throughout the docs.

Knowledge base

See how FAQs, files, website sources, products, and MCPs work together.