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

# Knowledge Search

> Let the agent look answers up in your knowledge bases mid conversation instead of guessing or inventing them.

**Knowledge Search** lets the agent look something up while it is talking. You point
it at one or more knowledge bases and say what each one covers. When the conversation
touches those topics, the agent searches rather than improvising.

***

## Set it up

Create your content first under **[Knowledge Bases](/product/features/knowledge-base)**.

<Warning>
  This one is not in **Choose Skills**. Look for it on the agent's **Data** tab, in the
  **Knowledge Bases** section.
</Warning>

Click **Add Knowledge Base** and fill in two fields.

<Frame>
  <img src="https://mintcdn.com/fluents/Ntis-q5QWqwCqRQw/images/product/skills/knowledge-bases-on-data-tab.png?fit=max&auto=format&n=Ntis-q5QWqwCqRQw&q=85&s=92773a4225a3f81e891f19277ef85571" alt="The Knowledge Bases section on the agent's Data tab, with an Add Knowledge Base button, rather than a chip under Choose Skills" width="1568" height="620" data-path="images/product/skills/knowledge-bases-on-data-tab.png" />
</Frame>

| Field                         | What it does                                         |
| ----------------------------- | ---------------------------------------------------- |
| **Knowledge base**            | Which of your knowledge bases to search.             |
| **When should this be used?** | The topics it covers, for example `return policies`. |

Add as many as you need.

***

## The second field is the important one

It is easy to treat "When should this be used?" as a label. It is not. It is the
instruction that decides when the agent searches.

The agent is told to reference a knowledge base whenever the conversation turns to the
topics you describe. A description that does not match how customers actually talk
means the agent never searches, and answers from the prompt instead.

| What you write                                                 | Result                                              |
| -------------------------------------------------------------- | --------------------------------------------------- |
| "Return policy, refund windows, exchanges and restocking fees" | Fires when someone asks to send something back.     |
| "Docs"                                                         | Vague. The agent has no idea when this is relevant. |

<Tip>
  Write it as the list of things a customer might ask about, in their words. You are
  not naming the document, you are naming the questions.
</Tip>

You can attach several knowledge bases with different topics, and the agent picks
based on what is being discussed.

***

## Where to go next

* Create and fill the content: **[Knowledge Bases](/product/features/knowledge-base)**
* Prove the agent looks things up when it should: **[Testing an agent](/product/features/agent-testing)**
* Everything else on the agent: **[Agents](/product/features/agent)**