> 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/set-up-with-an-ai-assistant/prompt-library-routines.md).

# Prompt library: routines

Weekly checks, call prep and release routines to run from your AI assistant, the six ready-made Jimo prompts, and a playbook to paste once.

Once something is live, the same questions come back every week: is anything broken, where do users drop, what did they answer. These prompts run them from your assistant in a minute. All of them read only, except where a prompt says it drafts.

***

## Every week

#### The digest

```
Give me this week's digest for the project: what is live, what changed, the best and worst
completion rates, new survey and NPS answers, and anything expiring soon. Keep it to one screen.
```

#### What is broken

```
Is anything broken this week? List the steps whose element could not be found, was hidden,
or matched several elements, with the experience, the page and the number of users affected.
```

A step that loses its element after a release of your app is the most common cause of a tour that stops working. See [Stable selectors on a dynamic front-end](https://help.usejimo.com/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md).

#### Where users drop

```
Where do users drop off in {experience name}? Give me the step with the biggest drop and how many users it loses.
```

#### What users said

```
Summarize this week's survey and NPS answers, grouped by theme, with two quotes per theme.
```

#### What the Agent could not answer

```
What did the Agent fail to answer this week? List the questions, most frequent first.
```

Only if you use the [Agent](https://help.usejimo.com/docs/experiences/agent.md) in your product.

## Before a customer call

#### What one user saw

```
What has {user email} seen in Jimo, what did they complete, and where did they stop?
```

#### Everything about a segment

```
Give me everything Jimo knows about {segment name} before my call: who is active,
what they saw, what they completed, what they answered.
```

Without the permission to view end users in your Jimo role, identities come back hidden.

## At each release of your product

#### Check nothing broke

```
Is anything broken since {date and time of the deploy, with time zone}? Only new problems.
```

#### Announce it

```
Draft a changelog post from these release notes: {paste the notes}. Show me the copy before saving.
Then draft a banner that points to it, for {segment name} only.
```

Both stay drafts until you publish them. See [Changelog](https://help.usejimo.com/docs/experiences/changelog.md).

## The six ready-made prompts

Jimo also offers six prompts your assistant can list and run. Each one chains the right questions and asks you for what is missing.

| Prompt                 | Use it for                                                                      |
| ---------------------- | ------------------------------------------------------------------------------- |
| `build_tour`           | Building a tour with you, step by step, with a link to try it before publishing |
| `release_announcement` | An announcement drafted, read back, revised and published                       |
| `weekly_digest`        | The weekly digest above, in one run                                             |
| `cs_account_review`    | One account or cohort, before a call                                            |
| `set_up_agent`         | Setting up the Agent from your product and help center URLs                     |
| `review_agent`         | Reviewing how the Agent did over a period, with fixes                           |

Ask your assistant to list the Jimo prompts, or name the one you want. What each one does in detail is in [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md#ready-made-workflows).

## Assistant playbook: Jimo weekly routines

A playbook is a block of instructions you paste once, so the assistant runs your routines the same way every time. In Claude, paste it in the instructions of a Project; in Cursor, add it as a rule.

```
You help me run Jimo for {product name}, project {project name}.
Every Monday, when I say "weekly", run in this order and write one short report:
1. Project overview for the last 7 days.
2. Broken steps since last Monday, new ones first.
3. The three experiences with the lowest completion rate, and the step where each loses the most users.
4. New survey and NPS answers, grouped by theme.
5. If the Agent is live: questions it could not answer.
Rules:
- Read only. Never publish, pause, delete or change an audience during this routine.
- Use the experience names exactly as they are in Jimo.
- When a number is not measured, say so; never write 0 for it.
- End with three suggested actions, each with the experience it concerns.
```

## Related

* [Prompt library: setup](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md)
* [Working with your spec and your team](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md), for the onboarding coach playbook
* [Analytics](https://help.usejimo.com/docs/analyze/analytics.md), for the same numbers in the dashboard
