Add your sources
Upload PDF, Word, PowerPoint, Excel, CSV or Markdown files, import a web page by URL, or write a page yourself.
How it works
Upload PDF, Word, PowerPoint, Excel, CSV or Markdown files, import a web page by URL, or write a page yourself.
Keep billing, shipping and product content in separate knowledge bases, each made of articles.
Create a sub-agent with the knowledge base tool, pick which knowledge base it reads, and add it to your agent.
After each conversation, questions the agent couldn't answer from your docs are listed as knowledge gaps.
Capabilities
A knowledge base is only useful if the agent reaches for it before it improvises.
Bring help-centre pages, handbooks, price lists and product sheets into one searchable library.
The main agent hands questions to a knowledge sub-agent, so it stays focused on the conversation.
Questions match on meaning, not exact words, so “can I send it back?” finds your returns policy.
The same sub-agent and library serve website chat and browser voice calls, so you maintain content once.
Fix a paragraph in the built-in editor and save. Only the sections you changed are re-indexed.
Each organisation's knowledge lives in its own database, never mixed with anyone else's.
In practice
These are the moments teams stop relying on answers buried in Slack threads.
Shipping times, return windows, plan limits — answered from your docs every time.
New buyers get setup steps from your guides instead of waiting on email.
Every answer comes from the same rules your team already approved.
Knowledge gaps from conversation intelligence tell you what to write next.
How it connects
A knowledge base isn't attached to the agent directly. You give a sub-agent the knowledge base tool, point it at one knowledge base, and add that sub-agent to your agent. The main agent stays focused on the conversation and calls the sub-agent whenever it needs facts.
Talks to the visitor in website chat or browser voice and decides when it needs facts.
Has the knowledge base tool, searches your library and hands back what it found.
Your articles, split into short sections and indexed by meaning.
Each knowledge sub-agent reads one knowledge base. Give your support agent the help-centre library and your sales agent the pricing and product library.
Website chat and browser voice both call the same sub-agent, so an answer on a call matches the answer in chat.
Supported sources
Everything is split into short sections of about 1,000 characters and indexed by meaning, so the agent retrieves just the passage it needs.
Text-based files are converted in your browser and split into sections.
Paste a URL. Embage strips navigation, headers and footers and keeps the page text. One page per import.
Add a page in the built-in Markdown editor for answers that don't live in a document yet.
Scanned, image-only PDFs and password-protected files can't be read. Export them as text first.
Limits
An article is one source, like a PDF or a web page. A page is one short section of it. Every lookup by the sub-agent counts as one search.
200
searches a month
1,000
searches a month
1,500
searches a month
FAQ
Through a sub-agent. Create a sub-agent, give it the knowledge base tool, choose which knowledge base it searches, and add it to your main agent. When a visitor asks something your docs cover, the main agent calls the sub-agent and answers from what it returns.
PDF, Word (.doc, .docx, .odt, .rtf), EPUB, PowerPoint (.ppt, .pptx), Excel (.xlsx), CSV, text and Markdown files, plus web pages by URL. Files need real text: scanned, image-only PDFs and password-protected files can't be read.
Yes. Paste a page URL and Embage imports its text, leaving out navigation, headers and footers. Each import brings in one page, so start with the pages customers ask about most: pricing, shipping, returns and FAQs.
Yes. Embage splits your content into short sections, turns them into embeddings and retrieves the closest matches before the model answers. You get RAG without setting up a vector database or writing code.
The agent works from the closest matches in your library. After the conversation, questions it couldn't answer from your knowledge base are listed as knowledge gaps, so you know what to add.
Yes. Website chat and browser voice call the same sub-agents, so one library serves both. Telegram agents don't search the knowledge base yet.
Edit a page and save — new searches use the change right away, with no agent to redeploy. Imported web pages don't refresh on their own, so re-import a URL when that page changes.
Yes. Each knowledge sub-agent is set to one knowledge base, so your support agent and your sales agent can read different sources.
It depends on your plan: Free includes 1 knowledge base, 10 articles, 50 pages and 200 searches a month; Starter 3, 30, 100 and 1,000; Pro 20, 500, 5,000 and 1,500. Enterprise is scoped with you.
Related
The knowledge base reaches your agent through a sub-agent with the knowledge base tool.
Read moreSee which questions went unanswered so your knowledge base keeps growing.
Read moreTurn an answered question into a saved lead, ticket or feedback record.
Read moreNo credit card. Questions? Write to support@embage.com.