> 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/getting-started/what-to-build-next/bring-in-the-agent.md).

# Bring in the Agent

The Agent answers your users' questions in your app, from what you teach it, and can guide or act on screen through Skills. Bring it in once a first experience is live and you have documentation to train it on. This page is about when, for whom, and how to start small. The full reference is the [Agent](/docs/experiences/agent.md) section.

***

## When it is worth it

* Your support gets the same "how do I" questions, and you have a help center or docs that answer them.
* Users know what they want and need the shortest path, not a sequence.
* Someone on your team can look at the Agent's conversations weekly and fix what it gets wrong.

Hold off while your users are still discovering the product itself, or while you have no docs to lean on: a chat that answers "I don't know" costs you trust and requests.

## Start in three moves

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F0fqPihFN423nKp4QvUlF%2Fn28-agent-rollout.png?alt=media&#x26;token=275ff1ea-1de8-4d31-91f4-8b7a58bfa3cb" alt="Train, test, open to a few"><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Train it

In [Agent > Knowledge > Sources](/docs/experiences/agent/knowledge/sources.md), add your help center URL. The guided setup may have done it already (check "What Jimo knows" at [Step 1](/docs/getting-started/your-workspace.md)). Add the pages of your app the Agent should know in [Interface](/docs/experiences/agent/knowledge/interface.md), starting with the two or three screens your users ask about most.
{% endstep %}

{% step %}

### Test it

Ask it ten real questions from your support inbox, in the dashboard's test panel. Fix the misses with [Custom Answers](/docs/experiences/agent/knowledge/custom-answers.md) or a better source. Nothing is visible to users yet.
{% endstep %}

{% step %}

### Open it to a few

Publish the [Launcher](/docs/experiences/agent/launcher.md) with Who = your internal segment, then a pilot segment (admins, one plan). Read the conversations in [Analyze](/docs/experiences/agent/analyze.md) for two weeks, then widen.
{% endstep %}
{% endstepper %}

## Contain it

The Agent is billed in requests, one answer per request, and your plan includes a monthly number (see the [pricing page](https://jimo.ai/pricing)).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FHJJtbiLjZrV9svpgEwoV%2Fn27-agent-entry-points.png?alt=media&#x26;token=a4c30db2-f0c9-41d9-aea9-b681f66d054d" alt="Launcher, Resource Center block and Launch Agent action, each with its own targeting, lead to one Agent"><figcaption><p>Each entry point keeps its own targeting</p></figcaption></figure>

Three ways to decide who gets it:

| Entry point                                                                                 | How to limit                                                          | Use it when                                                             |
| ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| The [Launcher](/docs/experiences/agent/launcher.md)                                         | Its own Where and Who                                                 | You want the Agent on every page, for a segment                         |
| The Ask Agent block in a [Resource Center](/docs/experiences/resource-center/components.md) | One Resource Center with the block for admins, one without for others | You already run a Resource Center per audience                          |
| A **Launch Agent** action on a button, a checklist task or a flow's last step               | The experience's own targeting                                        | A specific moment where a question is likely, with a pre-filled message |

Set up [Escalation](/docs/experiences/agent/escalation.md) to your support tool from day one, so a question the Agent cannot answer becomes a hand-off instead of a guess.

## Then Skills

A Skill is a task the Agent can guide the user through, or execute for them, on a scanned page: "create a project", "invite a teammate". Write one for the single action users ask about most, test it on your own account, and offer it through the Launcher's suggestions. See [Skills](/docs/experiences/agent/skills.md) and [Create a skill](/docs/experiences/agent/skills/create-a-skill.md).

## Related

* [How Jimo fits together](/docs/intro/what-is-jimo/how-jimo-fits-together.md)
* [Agent](/docs/experiences/agent.md)
* [Jimo MCP](/docs/integrations/mcp.md), to train and test the Agent from an AI assistant