Knowledge Base
The knowledge base is how your AI assistant learns about your product. Feed it your website content, documents, or raw text β and it becomes an expert on your business.
How It Works
When a user asks a question, the SDK sends the message to the Produck backend which performs vector search against your knowledge base to find relevant content. This content is injected into the AI's context, enabling accurate, grounded answers.
User Question β Vector Search β Relevant Chunks β AI ResponseAdding Sources
Via Dashboard
- Go to SDK Projects β select your project
- Navigate to the Knowledge Base tab
- Click "Add Source"
Source Types
| Type | Description | Best For |
|---|---|---|
| Website URL | Crawls and indexes a web page | Product pages, docs, FAQs |
| Sitemap | Crawls all pages in a sitemap | Entire documentation sites |
| Document | Upload PDF, DOCX, or TXT files | Internal docs, guides |
| Raw Text | Paste text directly | Quick knowledge snippets |
Website Crawling
When you provide a URL, Produck uses Firecrawl (opens in a new tab) to:
- Fetch and render the page (including JS-rendered content)
- Extract clean text content
- Split into chunks (~500 tokens each)
- Generate vector embeddings
- Store in Qdrant vector database
URL β Firecrawl β Clean Text β Chunking β Embeddings β Qdrantπ‘ Tip: Add your most important pages first β pricing, features, FAQ, and docs.
Retrieval
When the AI receives a user message, it:
- Generates an embedding of the user's question
- Searches Qdrant for the top-k most similar chunks
- Includes those chunks as context in the AI prompt
- Generates a response grounded in your actual content
This means the AI will never hallucinate about your product β it only uses information from your knowledge base.
Relevance Scoring
Each retrieved chunk has a similarity score (0β1). Only chunks above the relevance threshold are used. This prevents irrelevant content from polluting the AI's context.
Best Practices
What to Include
- β Pricing pages and plan details
- β Feature descriptions
- β FAQ and help center articles
- β API documentation
- β Getting started guides
- β Terms of service, refund policies
What to Avoid
- β Extremely long pages (split into sections)
- β Pages behind authentication (the crawler can't access them)
- β Frequently changing data (use API schema for real-time data)
Content Quality
The AI is only as good as the content you feed it. Ensure your knowledge base sources are:
- Accurate β up to date with current product info
- Clear β well-written, unambiguous text
- Complete β cover the topics users ask about most
Limits by Plan
| Plan | Knowledge Base Sources |
|---|---|
| Starter | 2 |
| Pro | 10 |
| Business | 50 |
| Enterprise | Unlimited |
Next Steps
- API Schema β Let the AI execute actions on your behalf
- DOM Context β Let the AI read the current page
- Chat Widget β Customize the chat interface