Login
Start free trial

Product tours for apps and websites.

More users adopt the features you ship.

Book a demo Start free trial
Lukas

Find all your projects here.

1 of 3

A tour walks users through the real screen at the moment they need it, and Kai Support offers it when someone asks how. Build it in a visual editor on your live app and trigger it by event, page and audience.

★ 4.6/5 on G2 Trusted by 4,500+ teams worldwide

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

Trusted by 4,500+ teams
Show the feature where it lives. Pick the element, write the step, choose how it advances. The tour runs on your interface, not on screenshots.

How a tour is built.

Steps, triggers, a hand-off to chat.
Message, pointer and video pointer. Each advances on Next, an element click or an input.
Event, page rules and audience decide who sees it. Send once or every time the rules match.
Enable Kai Support suggestions on a tour with a start page. When a customer asks for it, Kai Support replies with a button that starts it.

A checklist step starts the tour.

Progress stays visible in the widget.
Each onboarding task can launch a tour, a help article or a conversation. The checklist tracks what the user completed.
See onboarding checklists

When the tour is not enough.

Questions go to Kai, same widget.
Kai Support answers from your knowledge base and can offer the right tour. From Team, it investigates hard questions with the logs and click trail attached.
Meet Kai Support

Built for AI agents.

Tours your agent can draft.
Through the Gleap MCP, an AI agent drafts the steps on elements it knows from your code, targets the tour by page and audience, and checks the reach. Check the steps in the tour builder before you publish.
See the MCP server
Tours, checklists and support in one place.
Partfox moved from per-seat tooling to Gleap, integrated custom data in 10 days, and now runs live chat, AI support, bug reporting, feature requests, tours, checklists and surveys on one platform.
Maic Fankhauser
Product Manager, Partfox
About product tours
What is product tours software?
Product tours software lets you build guided walkthroughs that run on top of your own interface. In Gleap, a tour is a sequence of steps anchored to elements of your web app: message steps, pointer steps and video pointer steps. You build it in a visual editor with the Gleap SDK installed, and it runs for the users you target.
Which step types does a Gleap product tour support?
Three: message, pointer and video pointer. A message step is a centered card, a pointer step is anchored to an element, and a video pointer plays a short clip beside it. Each step advances on Next, on a click of the target element, or on an input, and you can show a Back button and let users dismiss the tour.
When does a product tour start?
A tour starts by rule, by link, by code or from a Kai Support suggestion. Rules combine an event trigger, page rules and audience conditions with a frequency: send once, or every time the rules match. You can also start a tour from a URL parameter, from the SDK, from a checklist step, a banner or an info card button.
Can Kai Support suggest a product tour?
Yes. Enable Kai Support suggestions on a tour and write a short description of what it shows. When a customer asks a matching question in the widget, Kai Support offers the tour with a button, and the tour starts from its configured start page. Your team authors the steps and keeps them current.
What is a co-browse tour?
A co-browse tour guides the user screen by screen with authored actions. It points at elements, clicks them or types a prepared value, waits for the user's own input where needed, and can read each step aloud with a synthetic voice. It is a prepared walkthrough your team builds, not remote control of the user's session.
Do we need a developer to build product tours?
Only once. A developer installs the Gleap JavaScript SDK; after that, your team selects elements and writes steps in the visual editor. Engineering helps with stable anchors: the SDK supports data-gleap-tour attributes so a step survives markup changes. See the product tour documentation.
Does the tour editor need access to our code?
No. The editor opens your website with the SDK installed and stores CSS selectors or data-gleap-tour anchors. Nothing is written to your code base, and tours are served to users by the SDK at runtime.
Do product tours work in native mobile apps?
No. Product tours run in the JavaScript SDK on websites and web apps. Native iOS, Android, React Native and Flutter apps use the other Gleap engagement formats, such as in-app banners, info cards, checklists, push notifications, news and surveys. Talk to us if you need guidance in a native app.
What can we measure?
Gleap shows tours sent and tours completed per tour. Combine those with the product event you want users to reach and with the questions arriving in support to judge whether the tour did its job.
How are product tours different from tooltips, checklists and info cards?
A tour is a sequence of steps on the interface. A tooltip explains one element on hover. A checklist is a list of tasks with actions and progress. An info card is a modal with media and a button. All four share customer records and audience targeting, with delivery controls that depend on the format, audiences and customer records in Gleap.
Can AI agents create product tours?
Yes, as drafts. An agent connected to the Gleap MCP server writes tour steps on CSS selectors it knows, for example from your code, and targets the tour by page, events and contact attributes. Open the draft in the tour builder to check every step on your live app before you publish.
How do tours fit the rest of the Gleap platform?
They share the customer record with support. A user who gets stuck asks Kai Support in the same widget, and a bug found mid-tour becomes a ticket with session replay attached. See how the platform shares context, how Gleap closes the loop from report to shipped fix and AI customer support for SaaS.
Switching from Userpilot, Appcues or Pendo?
Gleap fits when tours should sit next to support, feedback and the chat in one widget, on one customer record. Teams that need deep product analytics or an enterprise adoption platform may keep a dedicated tool. Compare Gleap vs Userpilot, Gleap vs Appcues, Gleap vs Pendo and Gleap vs WalkMe.
Which plan includes product tours?
Product tours are part of outbound messaging, included from Team ($149 per month, billed annually), with unlimited seats. See pricing for plan details.
More users adopt the features you ship.
Start free trial
See pricing

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

4.6/5
on G2