> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/experiences/agent/knowledge.md).

# Knowledge

### Overview

The Knowledge section is where you train and configure your Agent's knowledge base. Everything the Agent can answer comes from what you provide here.

<figure><img src="/files/keaH0E3gomkXt1chpGnL" alt=""><figcaption></figcaption></figure>

**Dashboard path:** [Agent > Knowledge](https://i.usejimo.com/agent/knowledge)

Knowledge is organized into four tabs:

* [**Sources**](/docs/experiences/agent/knowledge/sources.md): Static training data that feeds the Agent. Add URLs (site crawls or individual pages), plain text, or upload files. The Agent uses this content to generate conversational answers.
* [**Tours**](/docs/experiences/agent/knowledge/tours.md): Make your live Tours available so the Agent can deliver targeted, step-by-step guidance directly in conversations.
* [**Actions**](/docs/experiences/agent/knowledge/actions.md): Make your No-Code Actions available so the Agent can perform automated tasks for your users during conversations.
* [**Custom Answers**](/docs/experiences/agent/knowledge/custom-answers.md): Create curated question-answer pairs that the Agent prioritizes. Attach CTA actions like launching an experience, navigating to a URL, or running an action.

***

### Test Knowledge

Click the **Test Knowledge** button (top-right) at any time to open a private Agent chat and test responses against your current knowledge base.

<figure><img src="/files/2Ug0Uz62Zx2wYQ7um9hY" alt=""><figcaption></figcaption></figure>

This is the fastest way to verify that:

* New sources have been trained correctly.
* Custom Answers trigger on the right questions.
* Tours and Actions are suggested in the right context.

{% hint style="warning" %}

#### **SDK and Actions are disbled in preview.**

The **CTAs** will properly show as expected in the chat but it **will be disabled** so it can trigger nothing. \
To test the full behavior you'll have to **test it live**.&#x20;
{% endhint %}

***

### Best Practices

{% stepper %}
{% step %}

#### Building your knowledge base

* **Start with Sources, then layer Tours and Actions.** Sources provide the foundational knowledge. Tours and Actions extend the Agent from answering questions to actually guiding and performing tasks.
* **Keep sources focused.** A few well-targeted source crawls (help center, product docs) perform better than a massive crawl of your entire website. Exclude marketing pages, blog posts, and legal content unless users frequently ask about them.
* **Use Custom Answers for your top support questions.** Look at your support tickets to identify the 10-20 most common questions, then create precise Q\&A pairs for them. The Agent will prioritize these over generated answers.
  {% endstep %}

{% step %}

#### Training Tours and Actions

* **Don't activate everything at once.** Start with the Tours and Actions that address your most common user needs. Add more as you review conversations and spot gaps.
* **Write clear Topics.** Topics are the intents and questions that should trigger a Tour or Action. Use natural language that matches how your users actually ask ("How do I invite someone?" not "team member invitation procedure").
* **Leverage AI Suggestions.** When adding Topics, Jimo AI suggests relevant questions based on the Tour or Action content. Use these as a starting point and customize them.
  {% endstep %}

{% step %}

#### Monitoring and iterating

* **Retrain regularly.** If your product changes often, set auto-retraining to Daily or Weekly. If your docs are stable, Weekly or manual retraining is sufficient.
* **Review conversations.** Check [Agent > Analyze > Conversations](/docs/experiences/agent/analyze.md) to spot questions the Agent struggles with. These reveal opportunities to add sources, Custom Answers, or connect new Tours.
* **Test after every change.** Use the "Test Knowledge" button after adding or modifying sources, Tours, Actions, or Custom Answers to verify the Agent's responses.
  {% endstep %}
  {% endstepper %}

***

{% hint style="info" icon="calendar-clock" %}

### Coming Soon

The Agent sidebar also shows upcoming capabilities under **Coming Soon**:

* **Contextual Triggers**: Context-aware triggers that let the Agent proactively engage users based on what they are doing in the app.
* **Observe**: Monitor and analyze how the Agent interacts with your users in real-time.
  {% endhint %}