> 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/jLN6os7q5BIOEc4m8bJx" alt=""><figcaption></figcaption></figure>

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

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

Knowledge is organized into five tabs:

* [**Interface**](/docs/experiences/agent/knowledge/interface.md) **(**<mark style="color:blue;">**Beta**</mark>**)**: Let the Agent read the pages of your own product. Scan a page once, or let the Agent read it live, so it can answer questions about what users actually see on screen.
* [**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.
* [**Tours**](/docs/experiences/agent/knowledge/tours.md): Make your live Tours available so the Agent can deliver step-by-step guidance in conversations. <mark style="color:$info;">(</mark>*<mark style="color:$info;">Deprecated on September 12, 2026, replaced by Guidance Skills.)</mark>*
* [**Actions**](/docs/experiences/agent/knowledge/actions.md): Make your No-Code Actions available so the Agent can perform automated tasks. <mark style="color:$info;">(</mark>*<mark style="color:$info;">Already deprecated: only visible in projects that still have active Actions, replaced by Execute Skills. Agent triggering stops on September 12, 2026.)</mark>*
* [**Custom Answers**](/docs/experiences/agent/knowledge/custom-answers.md): Curated question-answer pairs that the Agent prioritizes. <mark style="color:$info;">(</mark>*<mark style="color:$info;">Deprecated on September 12, 2026, replaced by Explain Skills.)</mark>*

{% hint style="warning" %}

#### **Tours, Actions and Custom Answers are being replaced by** [**Skills**](/docs/experiences/agent/skills.md)**.**&#x20;

The Agent stops triggering all three on <mark style="color:red;">September 12, 2026</mark>.&#x20;

Automated Actions are one step ahead: their section is only available in projects that still have active Actions; everyone else should build Skills directly.&#x20;

Each tab shows its own deprecation notice with what to use instead.
{% endhint %}

***

### 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/ElNIR0IXgLVGxjewKU6Z" 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 disabled in preview.**

The **CTAs** will properly show as expected in the chat but it **will be disabled** so it can trigger nothing.&#x20;

To test the full behavior you'll have to **test it live**.&#x20;
{% endhint %}

***

### Best Practices

{% stepper %}
{% step %}
**Building your knowledge base**

* **Scan your key pages first.** The [Interface](/docs/experiences/agent/knowledge/interface.md) tab teaches the Agent what your users actually see. Start with your 3-5 most visited screens.
* **Then layer Sources.** A few well-targeted source crawls (help center, product docs) perform better than a massive crawl of your entire website.
* **Use Custom Answers for your top support questions** while they last, then convert them to [Skills](/docs/experiences/agent/skills.md).
  {% endstep %}

{% step %}
**Teaching procedures**

* **Prefer Skills over Tours and Actions.** New procedures should be built as [Skills](/docs/experiences/agent/skills.md) directly: they are the replacement, and they cover guidance, execution and complex answers in one place.
* **Write clear descriptions.** Whether for a scanned element or a Skill, describe intent in the words your users use ("How do I invite someone?" not "team member invitation procedure").
  {% endstep %}

{% step %}
**Monitoring and iterating**

* **Retrain regularly.** If your product changes often, set auto-retraining to Daily or Weekly in Sources. Rescan Interface pages when your UI changes.
* **Review conversations.** Check [Agent > Analyze](/docs/experiences/agent/analyze.md) to spot questions the Agent struggles with.
* **Test after every change** with the Test Knowledge button.
  {% 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 %}