Support deflection
A big share of tickets are someone who cannot find a button. Pepper answers those on the page, by showing the button, so your team gets the questions that need a human.
Reduce support tickets →Tourless onboarding: an AI guide for your website
Your users say what they want. Pepper shows them where to click.
Wayhint is an AI onboarding assistant you add with one script tag. It walks visitors to the right button, step by step, across pages. No flows to build, and no recorded flows to fix when your UI changes.
Live demo coming soon: you’ll be able to ask Pepper to show you around this site.
- Never reads input values
- Emails and numbers masked in the browser
- Origin allowlist per site key
- Shadow DOM: your CSS stays yours
- Works on any framework
How it works
Ask. Pepper looks. Pepper walks.
No tour script, no recording session. Pepper decides each step from the page the user is looking at.
Your user asks
In their own words: “download my tax statement”, “add a dependent”, “where do I change the invoice logo?”
Pepper reads the live page
The buttons, links and fields that are on screen right now, with labels only. Never the values people typed.
Walks, points, repeats
Pepper walks to the right control, points, and says what to do. After the click, the next step. Across pages, until it is done.
No flows to author
It learns your app by itself.
Product tours break on every release. Pepper reads the page as it is right now.
- Observe mode notes which control leads where while people use your app. Masked, no user ids, and a label only counts after several separate sessions have seen it.
- The explorer maps your app from a test account; we run it with you at onboarding. It clicks safe controls only and never submits forms or presses anything that looks like delete, pay or send.
- Ship on Friday. Nothing to re-record on Monday: the next step is chosen from the live page.
97.3%
of steps pointed at the right control, on our demo app with a learned app map.
88.9%
of goals completed end to end on the same demo app, up from 66.7% without the map.
1 tag
to install. No SDK, no build step, no flows.
Numbers from our own eval harness on “Ledgerly”, a fake invoicing app we built for testing, measured with a local Qwen3 30B-A3B model, not the hosted Claude guide; the Claude eval is pending. Your app is not our demo app; we will show you the numbers on yours.
Use cases
Fewer “how do I…” tickets. Faster first wins.
Onboarding
New users skip tours. They do not skip help with the thing they came to do. Pepper takes them from “I want to send my first invoice” to done.
Onboard new users →Built for complex apps
For the screens people visit once a year.
Tax statements. Benefits enrollment. Admin settings nobody remembers. Nobody learns these, and nobody should have to.
Payroll portals, HR systems, insurance and banking back offices, B2B admin consoles. Apps where a lost user means a support call, and a tour shown on day one is forgotten by day 300.
Designing for the once-a-year user
Privacy
Sees the page, not your users’ data.
The guide gets a list like e12 button “New invoice” in main. Not HTML, not screenshots, not what anyone typed.
- Input values are never read.
- Emails and long numbers in labels are masked in the browser, before anything is sent.
data-guide-privateturns an area into “(private)”;data-guide-ignorehides it completely.- The server drops any step that points at something not on the page.
- Running the guide in your own infrastructure, with your own model, is planned for Business.
- Read the security page →
Compare
Not another product tour tool.
Product tours and enterprise digital adoption platforms make you build the help. Wayhint builds it from your app.
| Feature | Wayhint | Product tour tools | Enterprise DAP |
|---|---|---|---|
| Setup | Paste one script tag; the app map is learned from use or an explorer run | Install, then build each tour in an editor | Install, then build flows, often with a dedicated team |
| Flows to author | None required | Typically hand-built | Typically hand-built |
| When the UI changes | Reads the live page each step; no flows to re-record | Tours tied to page elements may need editing | Flows tied to page elements may need updating |
| Starts from what the user asks | Yes | Usually scripted | Varies (search, AI add-ons) |
| Free plan | Yes, 500 MAU | Usually a trial | Rare (Pendo has one) |
| Prices on the website | Yes | Varies by vendor | Usually quote only |
Detailed comparisons: WalkMe, Whatfix, Pendo, Userpilot, Appcues, UserGuiding, Frigade.
Pricing
Pricing on the page. Imagine that.
A free plan to start. Upgrade when Pepper is busy.
Early access: sign-up and billing aren’t open yet. These are the plans we intend to offer.
Free
$0
forever
500 monthly active users
Starter
$149
per month, once billing opens
2,500 monthly active users
Growth
$499
per month, once billing opens
10,000 monthly active users
Business
From $15k
per year, once billing opens
Custom volume
Questions
Will it slow my site down?
The script loads with async, after your page, so it never blocks your content. It is about 17 KB gzipped and shows Pepper as a small 2D badge. The 3D Pepper (about 165 KB gzipped of script, plus the model and its decoder) loads only when a visitor first interacts with the guide, and lite mode never loads it. Everything is cached after the first visit.
Which AI model does it use?
The hosted guide uses Claude from Anthropic. The guide API also runs with OpenAI-compatible model servers (Ollama, vLLM, llama.cpp, LM Studio); running it in your own network is planned for Business.
Can I keep Pepper out of some pages or areas?
Yes. Only load the script on the pages you want. Inside a page, add data-guide-private to an element to replace its text with "(private)", or data-guide-ignore to hide it from the guide entirely. Each site key also only works on the domains you allow.
What counts as a monthly active user?
A visitor who asks Pepper at least one question in a calendar month. People who never open the guide do not count, so the free 500 covers more traffic than it sounds.
Does Pepper click things for my users?
No. Pepper only walks, points and explains. Your user does the clicking, so nothing happens in their account without them.
What does it need from my side?
One script tag and a site key. Optionally, a few sentences about your product and a test account for the explorer, so Pepper knows the app before your first visitor asks.
Let Pepper take it from here.
Paste one script tag. Free up to 500 monthly active users. No card, no flows to build.