Skip to main content
Who can use this?
  • Gallabox users with Bot Builder access who want to give their Chat AI Agent domain-specific knowledge.
  • Roles: Owners and Admins — Knowledge Base is configured in the Chat AI Agent settings.
The Knowledge Base is a RAG (Retrieval Augmented Generation) system. When a visitor asks a question, the agent searches the Knowledge Base for relevant documents and uses that information to generate accurate, grounded responses — rather than making things up.

Plan Availability

What is the Knowledge Base?

The Knowledge Base is a document library that your Chat AI Agent uses to answer questions accurately. Instead of relying only on its general training data, the agent can search through your specific documents — product guides, pricing sheets, FAQs, policies — and use that information to answer visitor questions. This is called RAG (Retrieval Augmented Generation):
  1. Visitor asks a question in the Web Chat widget
  2. Agent searches the Knowledge Base for relevant documents
  3. Agent retrieves the most relevant chunks and includes them in the LLM prompt
  4. Agent generates a response grounded in your actual documents

Supported Data Sources

For file size and storage limits, see Add Data Sources.

How Chunking Works

Documents are split into chunks — smaller pieces of text that the agent can search and retrieve quickly. Chunking matters because:
  • Smaller chunks → more precise answers, but may miss broader context
  • Larger chunks → more context, but less precise retrieval
You can configure:
  • Chunk size — how many tokens per chunk (default: 800 tokens)
  • Chunk overlap — how much overlap between adjacent chunks (default: 400 tokens)

How Retrieval Works

When a visitor asks a question, the agent searches the Knowledge Base and retrieves the most relevant chunks. You can configure:
  • Documents returned per query — how many chunks the agent retrieves to answer each question (default: 2)
  • Relevance threshold — minimum relevance score for a chunk to be included (default: 0.7)
Retrieval uses hybrid search (semantic + keyword, enabled by default) with reranking of results for better relevance.

Provider Options

The Managed (Qdrant) provider is recommended for most users — it requires no configuration and is fully integrated with Gallabox.

How to Connect a Knowledge Base to an Agent

1
Go to AI Agents and Bots in the left navigation of Gallabox.
2
Open or create a Chat AI Agent.
3
Click Settings on the agent.
4
Click Knowledge Base.
5
Click Connect Knowledge Base.
6
Choose your provider (Managed or OpenAI Assistant).
7
Add your data sources (see Add Data Sources).
8
Wait for documents to index — check status in the Knowledge Base panel.
9
Click Save.
Pro tip: Start with your most commonly asked questions and work backwards. Upload documents that answer your top 10 FAQ topics first. You can always add more documents later. Quality of answers depends on quality of documents — well-structured, clearly written documents produce better answers.

Example

Scenario: You run a SaaS company and want the Chat AI Agent to answer common questions about pricing, features, and integrations — without having to write every answer manually. Here’s how you’d set it up:
1
Create a Chat AI Agent with the use case: FAQ / Support.
2
Go to Settings → Knowledge Base and connect a Managed (Qdrant) Knowledge Base.
3
Upload:
  • Your pricing page as a PDF
  • Your feature comparison table as a CSV
  • Your integrations list as a PDF
  • Your FAQ page URL to crawl
4
Keep the default chunk size (800 tokens) and overlap (400 tokens).
5
Keep documents returned per query at the default of 2.
6
Write the agent’s instructions: “Use the Knowledge Base to answer pricing, feature, and integration questions. If you can’t find the answer in the Knowledge Base, say you don’t know and offer to connect the visitor with your sales team.”
7
Test in the Test Widget with questions like “What’s your pricing?” and “Do you integrate with HubSpot?”

FAQs

You can connect up to 3 Knowledge Bases per Chat AI Agent. This is useful if you want to separate different types of knowledge — e.g., one KB for product docs, one for support policies, one for pricing.
Typical indexing time varies by source size:
  • Small PDFs (under 10 pages): 1–5 minutes
  • Large PDFs (over 50 pages): 10–30 minutes
  • Website crawl: 5–20 minutes depending on number of pages
You can check the indexing status in the Knowledge Base panel. The status shows: Pending → Processing → Completed.
Yes. When you update a document in the Knowledge Base, you can re-index just that document — without re-indexing your entire Knowledge Base. Go to Knowledge Base → [Document] → Re-index.
Set your agent’s instructions to handle this explicitly. For example: “If you can’t find the answer in the Knowledge Base, say: ‘I don’t have that information yet. Let me connect you with our team who can help.’ Then use @assignTo to hand off to a human agent.”

In this section