> 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/checklists/behavior.md).

# Behavior

Set up progression by configuring how tasks expand, complete, and how users can dismiss the checklist. Manage both overall checklist behaviors and individual task actions easily.

**You will have at the end:** a checklist whose tasks tick themselves when users do what they ask, with the order, expansion and dismissal you chose.

***

## General behavior options

These options allow you to manage the flow, dismissal, completion behavior, and position flexibility of your checklist, helping users track their progression effectively and interact with the widget in a way that suits their workflow.

### Checklist step

This section helps you define how your checklist interacts with users. You can manage how tasks are expanded, whether the checklist can be dismissed, the order in which tasks should be completed, and whether users can reposition the checklist by dragging it around the screen.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Ftiw9IZoYtfgoIZy8cS89%2Fimage.png?alt=media&amp;token=c437f85d-e83c-42a8-b5ea-e33dcd740130" alt=""><figcaption></figcaption></figure>

#### Auto expand (A)

By default, tasks expand automatically upon task completion which means that it forces the checklist from the collapsed version to the full version. You can disable this and set custom conditions (similar to [experience step triggers](https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers.md#setting-conditions-if)). For instance, expanding can be triggered based on element visibility, page visit, or a delay.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FLFYFcGReRWKWov6ef78D%2Fimage.png?alt=media&amp;token=7ecec6c3-9dda-4fac-8463-5aa4a1f1282c" alt="A checklist in its collapsed version"><figcaption><p>Collapsed version</p></figcaption></figure>

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F1WzMMyAaFwkHJtRprGCh%2Fimage.png?alt=media&amp;token=7fff0761-7755-4def-a740-348fb944f912" alt="A checklist in its full version"><figcaption><p>Full version</p></figcaption></figure>

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FuORDb9EZ697lnhGaiWzM%2Fimage.png?alt=media&amp;token=d48e4c73-94fb-44cb-a6fe-0ab46b66552a" alt=""><figcaption></figcaption></figure>

#### Dismissible (B)

If set to **Yes**, a dismiss button appears, allowing the checklist to be skipped without completing all tasks. Without this, the only way to dismiss the checklist is by completing all tasks.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F2r28jy7fRbCdEBC2leJu%2Fimage.png?alt=media&amp;token=0463fbf3-b7c1-4770-831e-edceecc57f3d" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Using the dismiss button can prevent the checklist from being completed if there’s no recurrence setup, depending on your targeting settings.
{% endhint %}

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FWhP7GCYrsEnnNHwsssKA%2Fchecklists-07-recurrence-dismiss.png?alt=media&amp;token=20b70675-cf99-4f40-b0f5-99795984cba7" alt="Two rows. Show once: users dismiss the checklist on visit 1, and on the next visit it is not shown, marked May not show again. With a recurrence, Show every time or Show every N days, weeks or months: users dismiss it on visit 1 and it comes back on the next occurrence."><figcaption><p>Set a recurrence to bring a dismissed checklist back.</p></figcaption></figure>

**When the checklist is launched again**

By default a checklist shows on its own once: after all its tasks are completed, or after it is dismissed, it does not come back by itself. Another experience, or a **Launch experience** action, can still open it again. What the user gets then depends on **Dismissible**:

| Dismissible | State of the checklist | What the user gets                                                                                                |
| ----------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Yes**     | Completed or not       | The task list, every time. Each task can be run again. The completion step does not show, not even at completion. |
| **No**      | Completed              | The completion step, directly. The tasks are no longer reachable.                                                 |
| **No**      | Not completed yet      | The task list, where the user stopped.                                                                            |

{% hint style="info" %}
**For a checklist users can come back to whenever they want,** set Dismissible to **Yes** and add a **Launch experience** action to a [Resource Center](https://help.usejimo.com/docs/experiences/resource-center.md). The checklist stays within reach from there, even after it was closed or completed.
{% endhint %}

#### Draggable (C)

The **Draggable** option controls whether users can reposition the checklist on screen.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FQt4vJsNyvPVE8jN99wbS%2Fimage.png?alt=media&amp;token=9b7d78ab-3c79-483b-9b78-b02238ca08e8" alt=""><figcaption></figcaption></figure>

* When enabled (**Yes**, default), end users can drag and move the checklist widget anywhere along the screen borders, offering flexibility to place it in a convenient location as they work through tasks.
* When disabled (**No**), the checklist will remain fixed at the position defined in the **General > Position** setting.

{% hint style="info" %}
The **draggable behavior applies** both when the checklist is **expanded** and when it is **minimized**, allowing users to move it even after collapsing it.

<img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F0YbXvDSPRxXPFw4haUww%2Fimage.png?alt=media&amp;token=2f79a036-b398-496c-8f0d-e79dbbf573af" alt="" data-size="original">
{% endhint %}

#### Completion order (D)

You can control how tasks are completed:

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FReYSPdXBpUqHaDJIXR5F%2Fimage.png?alt=media&amp;token=45ab4080-9930-4067-ac26-ef37e75f8150" alt=""><figcaption></figcaption></figure>

* **In order:** Forces users to complete tasks from top to bottom.
* **In any order:** Allows users to complete tasks in any sequence they prefer.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F4OEmVB8o6pZtnf52A6TA%2Fchecklists-06-in-order-v2.png?alt=media&amp;token=c9f19590-e197-4ad2-94d2-9edbc05464b0" alt="Two checklists side by side. In any order: tasks are ticked in any sequence. In order: users complete tasks from top to bottom."><figcaption><p>In any order or in order</p></figcaption></figure>

With **In order**, the checklist opens the next task to complete and shows its button. A task whose completion condition is met before its turn does not tick, and the earlier match is not kept: once the task before it is completed, the user has to meet the condition again. For example, with task 1 on the Tables page and task 2 on the Billing page, a user who opens Billing first ticks nothing, then opens Tables and ticks task 1, and has to open Billing once more to tick task 2.

### Task list

This section lets you manage how tasks within the checklist are displayed and interacted with, along with the structure and elements of each task.

#### Expand task behavior

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FtmIdaR4dUmCHKiI2a5sn%2Fimage.png?alt=media&amp;token=1eda93e7-1349-4ce6-9256-bba716bda610" alt=""><figcaption></figcaption></figure>

This setting controls how tasks expand to show more details like a paragraph or CTAs (Call to Actions):

* **Hover:** Tasks automatically expand when the user hovers over them. This option allows users to see the task details without clicking.
* **Click:** Users need to click on a task to expand and view the details. This gives users more control over what they see and when, making it useful if you want a cleaner interface until users are ready to take action.

### Completion step

The **Completion Step Section** is where you can configure the final behaviors after users have completed all tasks in the checklist. This section lets you tweak how the step is **dismissed**, manage **completion actions**, and adjust the **primary CTA**. The completion step shows only when Dismissible is set to No.

#### Dismissing behavior

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FVAriMBRhPUzfDyqPYpkV%2Fimage.png?alt=media&amp;token=8b59904a-ccfe-4776-8622-de1aed8195c4" alt=""><figcaption></figcaption></figure>

The **general options** define how users can dismiss the completion step, with available options such as:

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FRo7NWiDVyiFSYNOBUtXq%2Fimage.png?alt=media&amp;token=98a1c4a9-6384-4eff-b73f-e56c1488a926" alt=""><figcaption></figcaption></figure>

* **Click the cross** (default): users need to click the cross to dismiss.
* **Click outside**: dismisses the checklist when the user clicks outside the modal.
* **Can't be dismissed**: forces users to stay on the modal unless they take specific actions (such as clicking on your primary CTA).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FmvFZGcOhlcbuxJekPKRx%2Fimage.png?alt=media&amp;token=ed9c381b-3687-4322-9d6c-34dc88bba0f4" alt=""><figcaption></figcaption></figure>

The **cross element** automatically dismisses the checklist and currently, this default behavior can't be changed.

#### Single CTA action

Unlike modals that may include secondary CTAs, the completion step has **only one primary CTA**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FLfVv8GUcFXqmEK1Mlopi%2Fimage.png?alt=media&amp;token=743e78bc-ea3c-4eeb-be3f-100731ecadd3" alt=""><figcaption></figcaption></figure>

This **primary CTA** comes with a default action to **complete the checklist**, which cannot be removed. However, you can add additional actions to it, similar to the [CTA actions](https://help.usejimo.com/docs/build/actions/available-actions.md) of tours. These actions include:

* **Launch Agent**: send a message to the AI Agent.
* **Launch experience**: show another Jimo experience.
* **Open Post**: open a changelog post.
* **Navigate to**: go to a URL.
* **Run JavaScript code**: not self-serve. The action shows greyed out with "Contact our support to enable this feature" until support enables it for your project.

Launch experience on this button is the instant way to show the next experience once the checklist is completed. See [Chain experiences](https://help.usejimo.com/docs/build/actions/chain-experiences.md).

## Tasks behaviors

In the **Tasks Behavior** section, you can define specific actions for each task, allowing you to control what happens when a user interacts with tasks and how tasks are marked as completed.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FpwxldzKf8PpgaLYLlo4q%2Fimage.png?alt=media&amp;token=9e1509b5-f828-485f-9566-b8204eb80ee7" alt=""><figcaption></figcaption></figure>

### Main task action

These are triggered when a user clicks on the task title or interacts with the task's primary CTA. Task actions operate similarly to any other [CTA or trigger actions](https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers.md#types-of-actions-then) within Jimo experiences.

When the action is **Launch experience**, the task holds an [experience link](https://help.usejimo.com/docs/build/actions/experience-links.md). The builder shows the launched experience beside the checklist, with the color of its state.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FwZCvguxpu8W341szkcpn%2Fimage.png?alt=media&amp;token=442bc6c0-0545-4535-a41c-60731af976bf" alt=""><figcaption></figcaption></figure>

### Completion conditions

These are conditions that, once met, automatically mark the task as completed. When the task is completed, it will display the checkmark, and progress will be updated. Common conditions include:

* **Experience is seen**: added on its own when the task's action is Launch experience, so the task ticks itself once users have seen the launched experience. You can remove it. Removing the Launch experience action removes it too.
* **On experience completion**: A typical condition used when the task’s action involves launching another Jimo experience, and completion of that experience marks the task as complete.
* **Event**: the task ticks itself when an existing event is triggered. Pick one of your [Success Tracker events](https://help.usejimo.com/docs/analyze/success-tracker/events.md) in **Select an event**: there is no need to rebuild its condition on the task.
* Other conditions, similar to the ones available for any [Jimo experience trigger conditions](https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers.md#types-of-conditions-if), can also be set to mark the task complete.

Select a task, then under **Mark completed** click **Add condition...**. The list offers eight types: **User's Segment**, **User's Attribute**, **Experience**, **Event**, **Element**, **Fills in input**, **Current page** and **Delay**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FLaMYQgxQI06b2W6rZ6Pb%2Fexperience-links-06-has-seen.png?alt=media&amp;token=a7b453e1-d84a-4f59-9c42-ace640918cfd" alt="The Mark task as completed popover with the condition Experience is seen, then Mark as completed."><figcaption></figcaption></figure>

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FPhLzxBvi4RI47kRaWfb6%2Fimage.png?alt=media&amp;token=4ed19727-5d32-43f2-818a-8dcdbf7d7dff" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You can select and combine different types of conditions.

Multiple conditions can be grouped with logical operators, making it possible to define precisely when a task should be marked as completed.
{% endhint %}

By combining these conditions or setting logic groups, you can create flexible and powerful completion criteria, ensuring that tasks are completed according to your user journey flow.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FwYCgY4sFxqsFWIPCqbqM%2Fchecklists-03-task-lifecycle.png?alt=media&amp;token=d20868e2-31f7-410f-83e2-f75cdeb5da1b" alt="A task to do with Start and Skip task buttons leads to two outcomes: Completed, when its completion conditions are met or a CTA completes it, and Skipped, when users click Skip task. A Statistics table below has separate Clicked, Skipped, Completed and Completion rate columns."><figcaption><p>Completed and skipped are two separate outcomes.</p></figcaption></figure>

### CTAs actions

The **CTA actions** section plays a crucial role in shaping the **progression of the checklist** by offering flexible control over how tasks are completed and how users engage with the tasks. These actions allow you to design alternative flows, set rules for task completion, and provide users with access to key resources. Each action is described in [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions.md).

#### Primary CTA action

This action drives the **main progression** of the checklist. By default, if no custom action is added, the Primary CTA will trigger the **Main Task action**, such as launching an experience. This action is key to maintaining the flow but can also be customized to suit alternative designs or interactions.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FR0x9nikmIGIGY3cKKi2F%2Fimage.png?alt=media&amp;token=4ae91978-326e-44f5-b4e0-7c5ff4a0e729" alt=""><figcaption></figcaption></figure>

#### Secondary CTA action

Offers more flexibility, typically defaulting to a **Skip task** action, unique to this element. It marks the task as skipped, not completed: skipped and completed are two separate outcomes, counted apart in the checklist **Statistics** (Skipped and Completed columns). Use it to let users move past a task that does not apply to them. Like the Primary CTA, this action can be replaced with custom actions for additional functionality.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F84cO5EGQELifyuYkB3jg%2Fimage.png?alt=media&amp;token=d75fff5c-159a-4222-9101-a6c9de1d48ec" alt=""><figcaption></figcaption></figure>

## From your assistant

Ask: *"In the checklist Get set up, make the task Invite a teammate complete itself when the URL contains /settings/team."* The assistant sets the task's completion conditions: one group of up to 10 conditions, all or any of them, on an experience (completed, seen, dismissed or their opposites), a tracked event, the URL, an element, a typed value or a delay. It also sets a task's buttons to open a URL, launch an experience, skip the task or complete it. On a live checklist it shows a preview before the change.

It cannot set **Auto expand**, **Dismissible**, **Draggable**, the completion order, the expand task behavior, the dismissing behavior of the completion step, a **Launch Agent** action or JavaScript: set those in the builder. More in [What to ask?](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md)

## Go further

* [Steps Triggers](https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers.md): the conditions and actions task settings reuse.
* [Experience links](https://help.usejimo.com/docs/build/actions/experience-links.md): a task that launches an experience holds a link to it.
* [Chain experiences](https://help.usejimo.com/docs/build/actions/chain-experiences.md): show the next experience after the checklist.
* [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions.md): the actions a task or a CTA can run.
* [Events](https://help.usejimo.com/docs/analyze/success-tracker/events.md): the tracked events a task condition can wait for.
* [Schedule, recurrence and priority](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/planning-your-experience.md): the recurrence behind the dismiss warning.
* [Resource Center components](https://help.usejimo.com/docs/experiences/resource-center/components.md): how the checklist block shows the active checklist.
* [Analytics](https://help.usejimo.com/docs/analyze/analytics.md): follow how users engage with your experiences.

**Next page:** [Resource Center](https://help.usejimo.com/docs/experiences/resource-center.md)
