HeyTappr for
Needs-attention: broken guides and missing ones
The needs-attention list catches the two ways in-app guidance goes stale: selectors that broke when your ui changed, and real questions from users that no published guide answers. It tells your team what to fix and what to write next.
Broken selectors surface themselves
When a step’s CSS selector no longer matches the live page, it appears in the needs-attention list instead of failing silently in front of users. Your team can edit the selector in the console and republish, or pause the guide meanwhile.
Unanswered demand is a roadmap
Every question the AI could not match to a published guide is logged as unanswered demand. That is a ranked view of the help content your users are actually asking for, in their own words.
Filterable like the rest of analytics
The list can be narrowed by date range and platform, so you can check what broke after last week’s web release or what Android users keep asking. It sits inside the same analytics view as the outcome funnel.
See it in your product
A demo takes fifteen minutes: HeyTappr guiding real users through a real interface.
Questions teams ask
- How do we find out a guide broke after a release?
- Broken selectors show up in the needs-attention list in analytics, filterable by date range and platform. From there you can open the guide in the console, fix the selector, and publish the update.
- Do we see the exact wording of unanswered questions?
- Question text storage is controlled by a privacy toggle in your workspace. With it on, unanswered demand includes the questions users asked; with it off, you still see that unmatched demand occurred.
More use cases
Or just email us and see it in your own product.