Walkthroughs
Walkthroughs that point at the real button, on the user’s own screen
Ask Skavelo how to do something and it shows the way on the live page. It highlights the next button, waits for the user to click it, then moves to the next step, across screens. Skavelo drafts walkthroughs from what it learned about your app, and builds one on the spot when nobody wrote one.
From a question to a finished task
Step 1
The user asks
In their own words in the widget, or by clicking one of the suggestions shown above it.
Step 2
Skavelo finds the way
It uses a walkthrough it drafted when one fits the question, and builds one for the question when none does.
Step 3
It points at each step
The next button is highlighted on the live page with a short instruction. Clicking it moves on to the next step.
Step 4
The user finishes
The walkthrough carries on across pages until the task is done. Every click is the user’s own.
Made for real apps, not demos
Finds the right element
Each step is matched by several signals: its position in the page, its accessible name and its text. If nothing matches well enough, the step is shown without highlighting the wrong thing.
Works across screens
A walkthrough carries on when the page changes or reloads, and skips steps that lead to a page the user is already on.
Fills in forms with the user
Asked to do a routine task, Skavelo fills in the fields with the details the user gave and stops on the final button for them to check and click.
Drafted from your app
After learning your app, Skavelo drafts walkthroughs for the tasks it finds, with a short title and explanation where a step needs one. Your team can review, edit, add or delete them on the Product map.
See where people stop
The Monday summary counts walkthroughs finished and left early, and names the step most people stopped at, often a button that moved.
Offer it at the right moment
Choose when Skavelo offers a walkthrough before anyone asks: on a page, for trial users, or after something they do. Each person sees the offer once, and it starts only when they click it.
Four ways to point, in your colour
Pick a highlight style and an accent colour in the dashboard, with a live preview. The widget uses them on every step.
Beacon
A ring with a pulsing dot on its corner. The default.
Spotlight
Dims the rest of the page around the button.
Trace
The ring draws itself around the button.
Ring
A plain ring that pulses twice.
Questions
Set it up with How walkthroughs work in the help center.
- Do we have to build walkthroughs?
- No. Skavelo drafts them from what it learns about your app, and builds one for a question when none fits. You can still edit, add or delete them on the Product map.
- Can it offer a walkthrough before anyone asks?
- Yes. Set up a walkthrough offer on the Product map: on a page, for users who match your rules, or after an event your app reports. Skavelo shows a short card above the widget, and clicking it opens the walkthrough. Each person sees it once, Not now means they aren’t asked again, and offers don’t count as conversations. Free includes 1 offer, Starter 3 and Growth unlimited.
- What happens when our UI changes?
- Skavelo re-learns your app on a schedule or after each deploy, and rereads only what changed. Each step is matched by several signals, and if none matches well enough the step is shown without highlighting the wrong element.
- Does Skavelo click buttons for the user?
- No. The user clicks each step themselves. When Skavelo fills in a form with them, it stops on the final button for the user to check and click.
- Does it work in single page apps?
- Yes. Walkthroughs carry on across route changes and full page loads, in React, Next.js, Vue, Nuxt, Svelte, Angular and plain HTML apps.
- Can we change how the highlight looks?
- Yes. Choose beacon, spotlight, trace or ring, and your accent colour, in the dashboard with a live preview.
See a walkthrough on your own product before you add any code.
Start free