What to ask?

Talk about your project the way you would to a colleague. Use the names you see in Jimo: an experience's title, a segment name, an end user's email. The assistant picks the right tool.

Get Insights

Ask	What you get
"How are we doing this month? What is expiring soon?"	A project overview: users, what is live, drafts, top performers, running experiments, activation.
"Where do people drop off in the Onboarding Tour?"	The per-step funnel with the biggest drop-off point.
"Is anything broken this week?"	Steps whose target element could not be found or was hidden, usually after a UI change.
"What has [e-mail] seen, and where did she get stuck?"	One end user's story before a customer call.
"Summarize this week's NPS comments."	The survey and NPS response feed, summarized.
"What did the agent fail to answer?"	The Jimo Agent's needs-attention feed: unanswered questions, disliked answers, abandoned skill runs.

Operate

Ask	What happens
"Draft a changelog post from these release notes, then show me the copy."	Creates a draft, invisible to end users, editable in the dashboard.
"Publish it to staging first."	Shows a preview and asks you to confirm before anything changes.
"Pause the Pricing banner right now."	Same rule: preview first, then your confirmation.
"Launch the churn survey to Trial Users, ending Friday."	Sets the audience and schedule, then sets it live, with a live audience count in the preview.
"Translate the Pricing modal into French and German."	Shows the languages it would write, then runs Jimo's smart translate once you confirm.

Every change is previewed before it happens, and nothing goes live without your confirmation. See Permissions & Safety.

Teach the Jimo Agent

Ask	What happens
"Teach the agent that exports are under Settings → Data."	The custom answer goes live for end users within minutes after you confirm.
"Recrawl the docs site."	Refreshes an existing knowledge source now instead of waiting for the schedule.
"Import the three onboarding docs from my Google Drive into the agent's knowledge."	Your assistant reads them with its own Drive tools and hands the text to Jimo. Jimo never gets access to Drive.
"Train the agent on help.acme.com, only the /docs pages."	Previews the pages found in the sitemap, up to 500, and any existing source that already reads them, before anything trains.
"Train the agent on our Zendesk help center."	Uses the Zendesk help center already connected in the dashboard, all articles or a selection.

A website source's settings cannot be edited in place. Add the new one, wait until training finishes, then delete the old one.

Set Up and Run the Jimo Agent

With Build and run my Jimo Agent, the assistant can take the whole Agent section: map your product's screens, train the agent on your help content, write the skills users need, test it the way users ask, put the launcher live, and review what happens once people use it.

It calls the same services as the dashboard, and a test question runs the real agent, so the answer matches what the widget would say.

Ask	What happens
"Set up the Jimo agent for app.acme.com. Our docs are at help.acme.com. Users mostly need help with projects and invitations."	The assistant checks what is missing, maps the screens, previews the help center before training on it, writes skills and leaves them off, and tests a real question. It activates skills and adds them as launcher suggestions only after you agree. The launcher goes live only when you say so.
"Teach the agent the project members screen I have open."	Writes a rule that covers every project, not only the URL that is open, and checks it against example URLs before saving. Once you confirm, it gives you a link to capture that screen's screenshot.
"Write a skill that walks users through inviting a teammate."	Writes the skill, inactive, tests a couple of phrasings, and activates it once you agree. It can add a suggestion on the page that starts it.
"How did the agent do this month? Fix what's worth fixing."	Reads usage and escalations against the previous period, then the disliked and escalated conversations, proposes a fix, and checks it with a test question.

Skills are created inactive, and putting the launcher live is its own confirmation. It is refused when your plan does not include the agent. See Permissions & Safety.

Screens

Each screen the agent knows is a page in Knowledge > Interface. The assistant can add one in two ways.

From a description (Read all). The assistant writes the page from a name, a description in your users' words, and URL rules. Once you confirm, it gives you a screenshot link: open it on that screen, with the Jimo Chrome extension or the browser's share-tab prompt. Until the screenshot is saved, setup still lists the page as missing one.

From a scan. For a screen whose elements matter, the assistant hands you a scan link instead. It opens the page builder with Scan and curate or Read all already chosen, and you still confirm before anything is saved.

• The Jimo snippet has to be on that site, or you use the Chrome extension.

• The URL is filled in only for a site the project already uses. Otherwise you type it.

• A scan saves a rule for that exact URL. The assistant then widens it to cover every record of the screen.

A Read-all scan of a page that already has a curated element list replaces that list. The scan link warns you before saving converts a page to the other mode.

Skills and Suggestions

Skills are explain, guidance (walk the user through it), or action (do it for them). Instructions name on-screen items by their labels, and {{email}} stands for a value the agent asks the user for. Skill names are unique in the project, and changes to an active skill reach users within about 30 seconds.

Suggestions are the chips above the launcher. A page has at most four active ones, a suggestion can start a skill, and {{attribute|fallback}} in its text is filled in for each user.

URL Rules

Every rule is checked against example URLs before it is saved. What it is matched on depends on where it is used:

Rule for	Matched on
A page	The path and query when the value starts with /, the full URL when it contains a domain.
Launcher targeting	The path, query, and # fragment, never the domain. Limit domains with the domain filter.
A website filter	Each page's path.

A rule written with a domain never matches launcher targeting or a website filter: write /docs, not help.acme.com/docs. A regex is written on the path, without . (use [^/]+, and \x2e for a literal dot).

When a page is created from a URL, record ids (numbers, UUIDs, and 24-character hex ids) become a wildcard and slugs stay as they are. A screen that routes in its # fragment, such as #/projects/123, is written on the full URL instead, for example contains app.acme.com/#/projects/.

Page names are unique in the project, and a new page that would load where another page already does is refused unless you say both should apply.

Ready-Made Workflows

Jimo also offers five prompts your assistant can list and run. They chain the right questions together and ask you for anything missing.

Prompt	What it does
release_announcement	Draft, read back, revise, and publish an announcement, then teach the agent about the release.
weekly_digest	Overview, top performers, activation, feedback, and agent gaps, written up as a digest.
cs_account_review	Everything Jimo knows about one account or cohort, before a call.
set_up_agent	Sets up the Jimo Agent from your product URL, help center URL, and what users need help with.
review_agent	Reviews how the agent did over a number of days you choose, and proposes fixes.

Next Steps

• Tools Reference: the full list of what the assistant can do, grouped by permission.

• Permissions & Safety: how previews and confirmations keep changes safe.