> 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/intro/what-is-jimo/how-jimo-fits-together.md).

# How Jimo fits together

Jimo has two halves. Experiences you build are predictable: you decide every step, every word, every trigger. The Agent is adaptive: it answers what the user asks, from what you taught it. Most accounts run both, and the question is only which one carries which job.

***

## Experiences you build

A tour, a checklist, a hint, a banner, a survey, a changelog, a resource center. You design them in the builder, position them on your screens, target them, publish them. They do the same thing for every user they reach.

Use them when:

* The moment is known in advance: first login, a feature release, the end of a key action.
* The content has to be exact: a compliance notice, a pricing change, a process with a fixed order.
* You want to measure a funnel: tours and checklists report step by step.
* The audience is low-tech or the product is new to them: a guided sequence works better than a question box.

## The Agent

The [Agent](/docs/experiences/agent.md) is a chat in your app. It answers from the [Knowledge](/docs/experiences/agent/knowledge.md) you give it (help center, URLs, files, your own screens), and through [Skills](/docs/experiences/agent/skills.md) it can guide the user on screen one control at a time, or execute a task for them with their confirmation.

Use it when:

* The questions are long-tail: hundreds of "how do I" that no tour will ever cover.
* Users already know what they want and need the shortest path to it.
* You have documentation to lean on, and someone to curate what the Agent learns.
* Support load is the problem you are solving.

The Agent is billed in requests (one answer is one request). Check the [pricing page](https://jimo.ai/pricing) for what your plan includes before you open it to everyone.

## How they connect

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F030sEnLt0UjObvbNPwZr%2F03-how-jimo-fits-together.png?alt=media&#x26;token=39c0a217-ea9f-4c24-b2f0-ee93ba56642d" alt="Built experiences and the Agent, and how they connect"><figcaption></figcaption></figure>

The two halves are wired to each other, in both directions.

| From                                                | To                          | How                                                                                                                                  |
| --------------------------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| A checklist task, a button, a Resource Center block | The Agent                   | The **Launch Agent** action, with an optional pre-filled message. See [Available actions](/docs/build/actions/available-actions.md). |
| The Agent                                           | A Tour, Survey or Checklist | A **Launch Experience** button under a [Custom Answer](/docs/experiences/agent/knowledge/custom-answers.md). The user clicks.        |
| A Resource Center                                   | The Agent                   | The **Ask Agent** block. See [Resource Center components](/docs/experiences/resource-center/components.md).                          |
| Your pages                                          | The Agent                   | The [Launcher](/docs/experiences/agent/launcher.md), filtered by page and audience.                                                  |

## Three setups that work

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FajZIIF59G4Ng40DWXJUa%2Fn03-three-setups.png?alt=media&#x26;token=8610af6d-2dc2-4136-b69b-69194f07a0cc" alt="Three setups: built experiences only, Agent for a subset, Agent first"><figcaption></figcaption></figure>

#### Built experiences only

Onboarding tour, checklist, hints, Resource Center with links. No Agent. The right choice when your users are not ready for a chat, when you have no documentation to train on yet, or when you want to control every word. Everything on this path is covered by the Getting started section.

#### Built experiences plus the Agent for a subset

Same as above, with the Agent available only to admins, to a plan, or to a segment, through a Launcher filtered on the Who or a dedicated Resource Center. A way to contain request usage while you test what users ask. See [Bring in the Agent](/docs/getting-started/what-to-build-next/bring-in-the-agent.md).

#### Agent first

The Launcher on every page, Knowledge trained on your help center, Skills on your core screens, and built experiences only for the moments that must be guided (first login, releases). Fits products with mature documentation and a product team that will curate Knowledge weekly.

{% hint style="info" %}
Whatever the setup, start with built experiences. A first tour and a Resource Center take an afternoon and need no training. The Agent is a second level: see [Your learning path](/docs/intro/what-is-jimo/your-learning-path.md).
{% endhint %}

## Related

* [Choose your first use case](/docs/intro/what-is-jimo/choose-your-first-use-case.md)
* [Agent overview](/docs/experiences/agent.md)
* [Migrating to Skills](/docs/experiences/agent/skills/migrating-to-skills.md), if you used Agent Tours or Actions before September 2026