Onboarding checklists for your app.

An onboarding checklist is a short list of tasks shown inside your app that leads a new user to a first result. In Gleap, each task has a title, a description, an estimated time, an action button and a completion rule. The widget shows the checklist card with progress and the next step, and a success screen when all tasks are done.

Its button can open a URL, a help article, a news item, a conversation workflow, a feedback form, a product tour, another checklist or a custom action your app implements. The description supports rich text with images and video.

Manually, automatically, or both. Manual completion shows a Mark as done control. Automatic completion resolves the task when a tracked event fires for that person, for example project_created sent through the SDK. Changing a task's completion rule re-checks the checklists still in progress; tasks people already finished stay done.

Three places. As a classic popup, inside the Gleap widget under Tasks, or embedded in your app as the gleap-checklist web component, with options for a floating bubble, progress bar and dark mode. You can also start a checklist from code, a banner, an info card or a shared key. The iOS and Android SDKs show checklists as well.

Yes. Each checklist has an event trigger and audience rules. Give admins and members different paths, or trigger a second checklist when the first is complete.

Checklists sent and completed, plus a funnel of how many people reached each step. The funnel is the signal to rewrite an unclear task or move a step that blocks people.

Only for setup. A developer installs the Gleap SDK and sends the events that complete tasks automatically; after that, your team writes and reorders tasks in the editor. See the checklist guide.

No. Completion is tracked per person, and you decide what follows. Use the tracked events to trigger an email or a survey from the same audience rules.

A checklist is a list of tasks with actions and progress. A tour is a sequence of steps on the interface. A tooltip explains one element on hover. An info card is a modal with media and a button. A checklist task can start a tour or another checklist; tooltips and info cards follow their own targeting.

They ask in the same widget. Kai Support answers from your knowledge base and brings your team in when needed. A technical problem becomes a ticket, which Kai Resolve investigates from Team. That is how onboarding feedback flows back into the product: see how Gleap closes the loop.

Gleap fits when onboarding checklists should live in the same widget as tours, chat and feedback, on one customer record. Compare Gleap vs UserGuiding, Gleap vs Product Fruits and Gleap vs Userpilot.

Yes. Through the Gleap MCP server, an agent drafts checklists with their steps and buttons, sets steps to complete when one of your tracked events arrives, targets the checklist by events and contact attributes, and checks the reach. If a step needs an event your app does not send yet, the agent gets the tracking code for your SDK. Drafts wait for your review.

Checklists are part of outbound messaging, included from Team ($149 per month, billed annually), with unlimited seats. See pricing for plan details.