Onboarding that starts with what the user wants
New users close the welcome tour. They don’t close help with the thing they signed up to do. Pepper takes them from “send my first invoice” to sent.
Why tours get skipped
A product tour runs on your schedule: ten tooltips, in your order, before the user has a reason to care. Most people click through to get to the app, then look for the one thing they came for.
Wayhint flips it. Nothing happens until the user asks. When they do, Pepper guides them to that goal and nothing else, starting from the screen they are on.
- First invoice, first project, first teammate invited: whatever the user names.
- Multi-page tasks keep going across page loads and SPA routes.
- Your “Get started” checklist can call
Wayhint.ask()for each item.
Onboarding never really ends in rarely used apps
In payroll, benefits, insurance or expense tools, most users are new every time. They visit once a quarter, or once a year, and the UI has changed since.
The annual task
Open enrollment, tax documents, year-end reports. A tour from onboarding day is long forgotten.
The occasional admin
The office manager who adds a new hire twice a year and has to relearn the screen each time.
The changed UI
You redesigned the settings page in spring. Pepper reads the new one; there is no old tour to fix.
More on this: Onboarding for rarely used apps.
Set up before your first user arrives
- Install the script tag on your app (staging first if you like).
- Run the explorer against a test account so Pepper knows what is behind each menu.
- Optionally, write two or three sentences about your product and the tasks new users care most about.
- Turn on observe mode with the guide hidden for a week if you want it to learn from real use before launch.
Compare with authored tours: Userpilot, Appcues, UserGuiding. Or see support deflection.
Let Pepper take it from here.
Paste one script tag. Free up to 500 monthly active users. No card, no flows to build.