> 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.md).
# Agent
## What is the Agent?
The **Agent** is Jimo's built-in AI chat assistant. It turns your documentation, knowledge base, and curated answers into an interactive help layer embedded directly in your product. Users interact with it through a conversational prompt where they can ask questions in plain language and get precise, contextual replies.
Beyond answering questions, the Agent can suggest and trigger other Jimo experiences (Tours, Checklists, etc.) and even perform automated actions to guide users through your product in real time.
{% hint style="info" %}
**Migrated from Settings:** The Agent section replaces the former **AI Knowledge** page that was previously located under Settings. All knowledge management features have been moved here, along with new configuration and analytics capabilities. If you navigate to [Settings > AI Knowledge](https://i.usejimo.com/settings/ai-knowledge), you will be redirected to the [Agent Knowledge section](https://i.usejimo.com/agent).
{% endhint %}
***
## Overview
The Agent section in the Jimo dashboard is your central hub for configuring, training, and monitoring your AI assistant. It is accessible from the main sidebar navigation, marked with a **NEW** badge.
The section is organized into three customization areas, plus two upcoming features:
### Customize
* [**Chat**](/docs/experiences/agent/chat.md) - Configure the chat widget appearance, the Agent's personality and behavior (general instructions), language settings, and preview the chat experience.
* [**Knowledge**](/docs/experiences/agent/knowledge.md) - Manage everything the Agent knows: your product's interface (scanned pages), training data sources, Tours, Actions, and curated Q\&A pairs.
* [**Skills**](/docs/experiences/agent/skills.md) **(****Beta****)** - Teach the Agent reusable, step-by-step procedures it can run on your product: guide users, take actions, or answer complex questions.
* [**Analyze**](/docs/experiences/agent/analyze.md) - Monitor Agent usage with key metrics (messages, users, success rate) and review the full history of user conversations.
#### Coming Soon
* **Contextual Triggers** - Automatically trigger the Agent based on user context and behavior.
* **Observe** - Monitor and observe user behavior patterns to improve the Agent's responses.
***
### Use Cases
* 📚 **Self-Serve Support**\
Let users ask questions in plain language and get instant answers from your knowledge base, reducing repetitive support tickets.
* 🎯 **Contextual Feature Guidance** \
When a user asks about a feature, the Agent can explain it and offer to launch a relevant Tour to walk them through it step by step.
* 🚀 **Onboarding Assistance** \
New users can ask the Agent how to get started, and it will guide them through setup steps, link to documentation, or trigger onboarding experiences.
* 🔍 **Content Discovery** \
Replies can surface related documentation, Changelog posts, and Jimo experiences, helping users discover features they didn't know existed.
* ⚡ **Automated Task Execution**\
With an [Execute a flow Skill](/docs/experiences/agent/skills/create-a-skill.md), the Agent completes tasks on behalf of the user: clicking, filling in forms, and navigating your product.
{% hint style="warning" %}
In projects that still have active [No-Code Actions](/docs/build/actions/automated-actions-no-code.md), it can also trigger those until September 12, 2026.
{% endhint %}
***
## How Users Access the Agent?
End-users can interact with the Agent in two ways: through a dedicated prompt in a Resource Center, or via the Launch Agent action triggered from any experience.
### From a Resource Center
Add an **Ask Agent** block to any Resource Center. This block displays a prompt input field in the Resource Center header. When a user types a question and submits it, the Agent chat opens with that question pre-loaded.
To add it: open your Resource Center in the builder, click **+ Add block** on the Header section, and select **Ask Agent** under Interactive.
For full configuration details (layout, text styling, placeholder customization), see the Ask Agent block section in the Resource Center Components documentation.
### From a Launch Agent Action
The **Launch Agent** action opens the Agent chat from anywhere in your experiences. Like any other action in Jimo, it can be assigned to:
* **CTA buttons** (Primary or Secondary) in Tours, Surveys, Banners and Hints.
* **Resource center** actions or **Checklist** tasks.
* **Progress triggers** as the "Then" result of an If/Then condition.
* **Survey conditions** as the "Then" result based on a user's answer.
When configuring the Launch Agent action, you can optionally pre-fill a **Message** with **dynamic attributes** (Jimo Email, Jimo Username, or any custom attribute) so the Agent immediately starts processing a contextual, personalized prompt when it opens.
For the complete configuration reference (Message field, Attributes, use cases, and combination rules with other actions), see [Launch Agent](/docs/build/actions/available-actions.md#launch-agent) in the [Available Actions](/docs/build/actions/available-actions.md) documentation.
{% hint style="info" %}
Pre-filling a message is powerful for contextual guidance. For example, at the end of an onboarding tour, you can trigger the Agent with "What should I do next?" to seamlessly transition from guided to conversational help.
{% endhint %}
***
## Best Practices
Training your Agent
* **Scan your key pages first.** The [Interface](/docs/experiences/agent/knowledge/interface.md) tab lets the Agent read the screens your users actually work on. Start with your 3-5 most visited pages, then expand.
* **Start small and focused.** Index your help center and core product documentation first. Avoid crawling your entire website including marketing pages, blog posts, and legal pages. A focused knowledge base produces better answers than a broad but noisy one.
* **Create Custom Answers for your top 10-20 support questions.** Look at your support tickets and chat logs to identify recurring questions, then create precise Q\&A pairs for them. The Agent will prioritize these over generated answers.
* **Retrain regularly.** If your product changes often, set auto-retraining to Daily or Weekly in Agent > Knowledge > Sources. If your docs are stable, Weekly or manual retraining is enough.
Building your first Skills
* **Start from a real support conversation.** The best first Skill answers a question your users actually ask. Pick a recurring "how do I..." and turn the answer into a Guide user in a flow Skill.
* **Choose the right type.** Execute a flow when the Agent should do the task, Guide user in a flow when the user should stay in control, Answer complex questions when text is enough. See [Skills](/docs/experiences/agent/skills.md).
* **Scan the page before creating the Skill.** A Skill runs on the elements the Agent knows. Scanning the relevant page first ([Interface](/docs/experiences/agent/knowledge/interface.md)) gives it the vocabulary.
Writing good General Instructions
* **Be specific about your product.** Mention your product name, key features, and target audience so the Agent uses the right vocabulary.
* **Define the tone.** Should the Agent be friendly and casual, or professional and precise? State it explicitly.
* **Set boundaries.** List topics the Agent should and should not cover. Include an escalation path for when the Agent can't help (e.g. "Suggest contacting support at ").
* **Use a preset as your starting point.** The five built-in presets (AI Agent, In-App Coach, Onboarding Specialist, Support, Expert Explainer) are good foundations that you can then tailor to your product.
Integrating the Agent in your product
* **Don't hide it.** Add the Ask Agent block to your main Resource Center so users can discover it naturally.
* **Use "Launch Agent" actions at the right moments.** Add contextual triggers at the end of a tour ("Have more questions?"), inside a checklist step ("Need help with this?"), or as a CTA in a changelog post ("Learn more about this feature").
* **Pre-fill messages when you can.** Using the Launch Agent action with a pre-filled message (and dynamic attributes like the user's name or email) makes the first interaction feel personal and immediately relevant.
Monitoring and improving
* **Review conversations weekly.** Go to Agent > Analyze > Conversations to spot questions the Agent struggles with. These are opportunities to add new sources or Custom Answers.
* **Track your success rate.** The Success Rate metric in Agent > Analyze > Statistics tells you how often the Agent provides satisfactory answers. If it drops, your knowledge base may need updating.
* **Iterate on your instructions.** The General Instructions are not a "set and forget" configuration. As you review conversations and spot patterns, refine the persona, add constraints, or adjust the tone.
{% hint style="info" %}
**The Agent is most effective when it combines all knowledge types together.**
* Interface pages so the Agent understands what users see on screen.
* Static sources (URLs, files) for comprehensive documentation.
* Custom Answers for precise control over critical questions.
* Skills for hands-on guidance and automated task execution.
{% endhint %}