Ask your agency anything.
"What's our monthly reporting process?" The agent searches your base first and answers from your SOP, not from a guess.
See AI AgentsYour knowledge.
Its answers.
Upload documents, import websites and write SOPs once. Your AI agents answer from them in your voice, with the source attached, and one client's knowledge never leaks into another's.
Free plan forever. Paid plans include a 14-day trial.
Generic AI guesses. Yours should know: your prices, your process and your brand voice, with the page it came from right under every answer.
01 / From source to answer
Scroll and four sources flow into one named base. Attach the base to an agent, ask a question, and the answer arrives with its source. The base next door stays sealed.
Add sources
Glow Skincare0 sources
Attached to Front desk agent
Northside GymIsolated
Its own sources. Never mixed into Glow Skincare's answers.
Front desk agentGlow Skincare
02 / Ways in
Upload documents
PDFs, Excel sheets, CSV and plain text files. The parser handles multi-page PDFs, then indexes the content for retrieval.
Write it directly
Write brand guides, SOPs and client notes with slash commands for headings and checklists, or paste text and Q&A pairs straight into a base.
Answers you can check
Responses in chat can show the documents they came from, so you can see exactly which entries informed each answer.
See AI Agents03 / Where it answers
"What's our monthly reporting process?" The agent searches your base first and answers from your SOP, not from a guess.
See AI AgentsAI drafts replies on email, SMS and website chat, grounded in your knowledge base, so prices and policies come out right.
See the InboxVoice agents search the knowledge base while they talk, then book the meeting and write the summary into the CRM.
See AI calling04 / By the numbers
ways in: upload files, paste text, add Q&A pairs
file types: PDF, Excel, CSV, plain text
base can serve many agents at once
content shared between bases unless you add it
05 / Questions
A knowledge base is a named container of sources: documents, website pages, written docs and FAQs. You attach a whole base to an agent, and that agent answers from it. Bases are isolated from each other, so content in one base never shows up in another base's answers.
When you ask your AI agent a question, it searches the knowledge base using RAG (Retrieval Augmented Generation) to find relevant documents. It then generates a response based on that context, so answers are grounded in your actual data — not hallucinations.
You can upload PDFs, Excel spreadsheets, CSV files, and plain text files (.txt). The parser handles multi-page PDFs automatically. You can also paste text or add question and answer pairs directly.
Not automatically yet. You can save a page's URL with a document as a reference, but the page itself isn't fetched. Paste the page content into the base as text, or add the key facts as question and answer pairs.
Per client, if you want. Knowledge bases are separate, named containers, so you can keep one per client and attach each only to the agents that should use it. Agency-wide material like SOPs and brand guides can live in its own base. Bases never share content, so one client's documents never show up in another client's answers.
New documents are indexed in the background, usually within a few minutes, and each one shows its status while it processes.
Yes. Every AI response in chat can show the source documents it referenced. You can see exactly which knowledge base entries informed each answer.
Free plan forever. No card needed.