Skip to main content
DialNexa knowledge bases store workspace documents that can be attached to draft agent versions. A knowledge base has a name, organization context, and related documents that can be uploaded, parsed, searched, and used by supported agents at call time. DialNexa Knowledge Base page showing the sidebar, selected knowledge base details, uploaded document, download action, and delete action.
Knowledge helps an agent answer from material you provide. It does not replace a clear prompt telling the agent when to use that material.

Knowledge Base Objects

These objects define how knowledge content is stored. The vector store behind a knowledge base is managed by DialNexa. Users should work with knowledge base names, documents, and agent version attachments instead of copying or editing vector IDs.

How Agent Retrieval Works

When a supported cascaded agent has knowledge bases attached, DialNexa searches the selected collections during the call and sends the best matching chunks as context for the model. Speech to Speech agents do not use the separate knowledge retrieval path. Use a cascaded agent when the call needs document-backed retrieval.

Where Knowledge Matters

Use knowledge when callers ask about factual material.

Agent answers

Give the agent reference material for product, policy, or FAQ questions.

Document management

Upload, update, download, and soft-delete knowledge documents.

File limits

Use accepted document types and keep files within upload constraints.

Call review

If the agent answered incorrectly, compare prompt, knowledge, transcript, and document content.

Knowledge Base Questions

No. Use it when the agent needs factual reference material beyond the prompt.
Only partly. The prompt still needs to tell the agent when and how to use knowledge.
Treat deleted documents as unavailable for future use and retest the agent.

Managing Documents

Maintain document content.

Using Knowledge In Agents

Attach knowledge to behavior.

Documents And Limits

Prepare files.