> ## Documentation Index
> Fetch the complete documentation index at: https://agent-docs.magicwebs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge base

> Give your agents the FAQs, policies, pages and documents they answer from, then fix wrong answers and fill knowledge gaps.

The knowledge base is where agents look up answers they don't already know from your company profile. Every source is split into short passages and indexed, so an agent can find the right passage in the middle of a conversation.

Open it from **Build → Knowledge base**.

![The knowledge base with three sources ready to search](https://mintcdn.com/magicwebs/lXS3DuVdQz1WpiFT/images/console/knowledge.png?fit=max\&auto=format\&n=lXS3DuVdQz1WpiFT\&q=85\&s=dbf5f1472fa955507aacb951bf031753)

The page has three tabs:

* **Sources**: everything you have added.
* **Wrong answers**: replies your team marked as wrong.
* **Knowledge gaps**: questions agents could not answer.

## Add a source

**1. Choose Add source**

Give the source a **Title**. The agent sees it beside every passage, so make it descriptive, for example "Booking and documentation process".

**2. Choose who can use it**

**Available to**: every agent in the workspace, or only one agent.

**3. Add the content**

Pick a tab:

* **Paste text**: any prose an agent should be able to quote.
* **FAQ**: question and answer pairs, separated by a blank line. Retrieval works noticeably better with Q and A.
* **URL**: a page from your website. It is fetched once; choose **Reprocess** after the page changes.
* **File**: PDF, plain text, Markdown, CSV, JSON or HTML. Scanned, image-only PDFs have no text to read; paste their content instead.

**4. Wait for it to be searchable**

The source moves from *queued* to *indexing* to *searchable*, usually within seconds. If it shows *failed*, open it and choose **Reprocess**.

> [!TIP]
>
> Keep one topic per source, for example "Buyer FAQs", "Project amenities and locations" and "Booking and documentation process". Small, focused sources give sharper answers than one huge document.

## Manage sources

Each card shows its status, kind, how many passages it was split into, and which agents can use it.

* **View & edit**: read the passages agents retrieve. Text sources can be edited, which re-indexes them. For URL and file sources, only the title and availability can change.
* **Reprocess**: index the source again.
* **Delete**: remove it. Agents stop using it immediately.

## Knowledge gaps

When an agent is asked something it cannot answer, it tells the customer the team will follow up and logs the question here. Similar questions are grouped, most-asked first.

![Knowledge gaps: two unanswered questions about pets and plot prices](https://mintcdn.com/magicwebs/lXS3DuVdQz1WpiFT/images/console/knowledge-gaps.png?fit=max\&auto=format\&n=lXS3DuVdQz1WpiFT\&q=85\&s=2e0ae00e5347375a05bc46667161a975)

For each gap:

* **Add answer**: write the answer. It is saved as an FAQ, so every agent answers it from now on.
* **Dismiss**: ignore it.

Filter between **Open**, **Answered** and **Dismissed**.

## Wrong answers

When someone on your team marks an agent's reply as wrong in the [inbox](https://agent-docs.magicwebs.ai/inbox/conversations.md), it appears here with the sources the answer came from.

1. Choose **Fix** and write the **Correct reply**. Agents use your correction ahead of anything that disagrees with it.
2. Optionally edit the source the wrong answer came from.
3. Choose **Send the right answer to the customer**. This works within 24 hours of the customer's last WhatsApp message.

Choose **Not wrong after all** to unmark a reply.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.