Knowledge & memory
Knowledge bases
Give agents documents to answer from, so facts live in one place instead of in every prompt.
Why use a knowledge base
Prompts should describe behavior. Facts that change, such as prices, policies, opening hours, product details and FAQs, belong in a knowledge base. The agent searches it during the conversation and answers from what it finds.
Create one
- 1
Open Knowledge and create a knowledge base.
- 2
Add sources: upload files or paste text.
- 3
Wait until each source shows as indexed.
- 4
Attach the knowledge base to an agent on its Model tab.
Sources
| Source | Status | Notes |
|---|---|---|
| File upload | Live | PDFs, documents and text files. Re-upload a file to replace it. |
| Pasted text | Live | Good for FAQs and short policies. |
| Website URL | Coming soon | Importing pages by URL needs a safe fetch boundary that is still being built. Paste the page text for now. |
Voice and chat knowledge are separate
Each knowledge base belongs to one channel, and the database enforces it. A voice agent can't attach a chat knowledge base or the other way around. This keeps chat-only content, like long policy pages, out of fast voice lookups.
Writing knowledge that works
- One topic per section, with a clear heading.
- Write the answer, not the marketing: "Cleanings cost $120 without insurance."
- Remove duplicates and outdated versions. The agent can't tell which is current.
- For voice, prefer short answers. Long passages slow down the reply.
Tip
When an agent gives a wrong answer, search your knowledge for the topic. Most wrong answers come from missing, outdated or contradictory sources.
Last updated November 2026 · Found a problem? Email support@katexs.com
