Overview
A knowledge base is a collection of sources — files, URLs, or text snippets — that your agent can search during a conversation. When a caller asks a question, the agent retrieves the most relevant passages from the knowledge base and uses them to formulate a response. This is especially useful for:- Product catalogs — answer questions about pricing, features, and availability
- FAQ documents — handle common customer inquiries accurately
- Policy documents — reference specific terms, conditions, or procedures
- Internal wikis — provide support agents with up-to-date information
- Training materials — ensure consistent, accurate responses across all calls
Creating a Knowledge Base
From the Dashboard
- Navigate to Knowledge Bases in the sidebar
- Click Create Knowledge Base
- Enter a Name and optional Description
- Click Create
Via API
Adding Sources
Each knowledge base can contain up to 10 sources. Sources are processed asynchronously — after adding a source, it moves through the following statuses:| Status | Description |
|---|---|
queued | Source is queued for processing |
processing | Source is being indexed and will be available shortly |
ready | Source is indexed and available for retrieval |
failed | Processing failed (check errorMessage for details) |
Text Sources
Add text content directly. Useful for FAQ lists, policy excerpts, or any structured text. Dashboard: Click Add Source → Text, enter a name and content, then click Add Text Source. API:URL Sources
Add a web page URL. RevRing fetches and indexes the page content automatically. Dashboard: Click Add Source → URL, enter a Name and the URL, then click Add URL Source. API:Only
http:// and https:// URLs are supported. The page content is fetched and indexed at the time the source is added. To update the content, delete and re-add the source.File Sources
Upload documents directly. Supported formats: PDF, TXT, DOCX, MD, CSV, JSON. Dashboard: Click Add Source → File, then select a file from your computer. API:Checking Source Status
After adding a source, you can check its processing status:status field (queued, processing, ready, or failed) and an errorMessage if processing failed.
Linking Knowledge Bases to Agents
Once your knowledge base has sources in theready state, link it to one or more agents.
From the Dashboard
- Open your agent’s settings
- Go to the Knowledge tab
- Click Link Knowledge Base
- Select the knowledge base you want to link — it’s linked immediately
Via API
Retrieval Settings
When a knowledge base is linked to an agent, you can configure how the agent uses it. These settings are on the agent, not the knowledge base — so different agents can use the same knowledge base with different retrieval behaviors.Retrieval Mode
| Mode | Description |
|---|---|
automatic | Labeled Automatic (RAG) in the dashboard. The agent automatically searches the knowledge base before every response. This is the default and recommended mode. |
query_tool | Labeled Query Tool in the dashboard. The agent uses a dedicated tool to search the knowledge base. This gives you more control over when retrieval happens — useful if you want the agent to only search when explicitly asked. |
Chunks to Retrieve
The number of text passages to retrieve per query (1–20, default 3). Higher values provide more context but use more tokens. Start with the default and increase if the agent is missing relevant information.Similarity Threshold
Minimum relevance score for retrieved passages (0.0–1.0, default 0). Set this higher (e.g., 0.3–0.5) to filter out loosely related content. A value of 0 returns the top results regardless of relevance score.Configuring via API
Managing Sources
Deleting a Source
To remove a source from a knowledge base: Dashboard: Hover over the source row and click the trash icon, then confirm deletion. API:Deleting a Knowledge Base
Deleting a knowledge base removes all its sources and unlinks it from any agents. Dashboard: Open the knowledge base, click the ⋮ menu, then select Delete Knowledge Base. API:Best Practices
Content Quality
- Be specific: Focused, well-structured content retrieves better than long, rambling documents
- Use clear headings: Documents with clear sections help the retrieval system find relevant passages
- Keep content current: Delete and re-add sources when the underlying content changes
- Avoid duplication: Don’t add the same content multiple times across different sources
Prompt Integration
Reference the knowledge base in your agent’s prompt to guide how it uses retrieved information:Source Organization
- Create separate knowledge bases for different topics (e.g., “Product Catalog”, “Support Policies”, “Pricing”)
- Link only the relevant knowledge bases to each agent
- Keep source count manageable — a few high-quality sources outperform many low-quality ones
Troubleshooting
Source stuck in processing
Source stuck in processing
Most sources process within a few seconds to a minute. If a source stays in
processing for more than 5 minutes, it may have encountered an issue. Try deleting and re-adding the source. For file sources, ensure the file is not corrupted and is in a supported format.Source failed to process
Source failed to process
Check the
errorMessage field on the source for specifics. Common causes include:- URL is unreachable or returns an error
- File format is not supported
- File is corrupted or empty
- Text content is empty
Agent not using knowledge base
Agent not using knowledge base
- Verify the knowledge base is linked to the agent (check the Knowledge tab)
- Ensure at least one source is in
readystatus - Check that retrieval mode is set to
automatic(orquery_toolif you prefer manual control) - Add guidance in your prompt telling the agent to use its knowledge base
- Try increasing the
knowledgeBaseChunksvalue if relevant content is being missed
Agent returning inaccurate information
Agent returning inaccurate information
- Review the source content for accuracy
- Increase
knowledgeBaseSimilarityThresholdto filter out loosely related passages - Decrease
knowledgeBaseChunksto reduce noise from less relevant results - Add instructions in your prompt to only use verified knowledge base content