What is Jimo

A product adoption platform: experiences you build, an Agent that answers and guides, and how a first one goes live.

Jimo is a product adoption platform: you build in-app experiences on top of your own product, target who sees them and when, publish without a release, and measure what they change. Two things make it up: experiences you build yourself, and an Agent that answers and guides on its own.

---

Three things you do with it

Every use case we see falls into one of three families. Naming yours is the first decision, because it decides which experience you build first.

Family	What you want	Experiences that do it
Announce	Push a piece of information to users, concisely: a release, a webinar, a new concept, a maintenance window	Banner, Modal, Changelog post
Guide	Take users by the hand through a process or a feature, and show them where things are	Tour, Checklist, Hint, Resource Center, Agent Skills
Collect	Get information back: feedback, NPS, a choice, a discovery question	Survey, NPS, feedback widget

Most accounts start with Guide (an onboarding flow), add Announce the first time they ship something, and add Collect once they have an audience worth asking.

Two ways to deliver

Within each family you choose how the content reaches the user.

Guided

Jimo starts the experience, based on context and behavior. A tour on first login, a modal when a feature ships, a survey after an action. The user does not have to look for it.

Self-serve

The content stays available and the user comes to it. A Resource Center with links and a checklist, hints on the controls that need explaining, the Agent's launcher at the bottom of the screen.

A good first setup mixes both: one guided flow for newcomers, one self-serve surface they can come back to. Choose your first use case shows which combination fits which goal.

The toolbox

Experiences you build

Tours & Modals

Step-by-step guides on your screens. A modal is a tour with a single step.

Checklists

A list of tasks with progress, each task launching a tour or a link.

Hints

Tooltips and hotspots pinned to a control, always there.

Banners

A bar at the top or bottom of the page for an announcement.

Surveys

Questions in context, NPS, with branching and notifications.

Changelog

A feed of posts users can browse, with a trigger in your app.

Resource Center

A help hub in a widget: links, checklist, Agent, contact, per page and per audience.

The Agent

The Agent answers your users' questions in-app from the knowledge you give it (help docs, URLs, files, your own screens), and can guide or act on screen through a Skill the user confirms. It has its own trigger, the Launcher, and can also sit inside a Resource Center or be launched from a button in any experience. How Jimo fits together explains when to use one or the other.

Around them

Target & Publish

For every experience, Show on (the trigger), Where (the pages), Who (the audience), When (schedule and frequency), and a Goal to measure.

Users & Segments

The users your app identifies to Jimo, their attributes, and the segments you build on them. See Users & Segments.

Analytics

Views, completion, step drop-off, survey answers, goals. See Analytics.

Spaces

Folders that group experiences of any type by topic, such as "Onboarding". See Spaces.

Jimo MCP

Drive all of the above from Claude, Cursor or another AI assistant. See Jimo MCP.

How a first experience goes live

Only Install needs a developer

1

Build

Build on your own app with the Chrome extension, before anything is installed. Or start from the drafts the onboarding flow generated for you.

2

Install

Install the snippet on your app, and identify your users so Jimo knows who is who.

3

Target and publish

Pick the trigger, the pages, the audience, the environment. Publish to yourself first.

4

Measure and iterate

Analytics per experience, a goal when the experience is meant to change a behavior.

That is the Getting started section, step by step.

Plans. Jimo is sold as the Adoption Suite (the experiences above) and the Adoption Agent, separately or together. The trial covers both. What each includes is on the pricing page, and your usage sits in Settings > Plan & Billing.

Go further

• How Jimo fits together: built experiences and the Agent, what each does, when to combine them.

• Choose your first use case: one use case to start, and the experience to build for it.

• Your learning path: the five levels from "visible to me" to "self-serve and Agent".

Next page: How to start?