A Knowledge Base is a set of approved documents an assistant can use during a call. It helps the assistant answer questions from the right source instead of relying only on the prompt.
When to Use a Knowledge Base Use a knowledge base when the assistant needs to answer from:
FAQs.
Pricing or plan details.
Product catalogs.
Policy documents.
Eligibility rules.
Support scripts.
Standard operating procedures.
Do not use a knowledge base as a replacement for a clear prompt. The prompt still tells the assistant when and how to use the information.
Knowledge Base Types
Deterministic KB Use this for structured data where you define the exact fields to retrieve.
Non Deterministic KB Use this for general documents where Ringg AI searches for the most relevant answer.
Type Best For Tradeoff Deterministic KB Pricing tables, policy fields, product catalogs, eligibility rules More setup, more predictable answers Non Deterministic KB FAQs, articles, manuals, SOPs Faster setup, but answers may need more testing
File Limits Limit Value Files per knowledge base Up to 4 File size Up to 512 MB per file
Use focused files with clear headings. Remove outdated or conflicting content before upload.
Attach to Assistants After training a knowledge base, attach it to an assistant from Assistant Settings and then Knowledge Base .
Multiple assistants can use the same knowledge base, but every assistant should be tested after attachment.
Developer Handoff If your product or backend needs to reference knowledge base setup, send developers:
Item Why It Matters Knowledge base name Confirms the right document set Knowledge base type Explains the retrieval behavior Assistant name and agent_id Confirms where the KB is attached Source document owner Identifies who approves changes Test questions Helps QA the assistant and support workflows
If engineers store knowledge base IDs, ask them to retrieve the current ID after training is complete. 
