Use case · In-app onboarding help
Help that opens next to the screen they are stuck on
New users do not read the docs; they click around until they are stuck. Put the answers where they are stuck: a side panel inside your app, opened from a Help button or a keyboard shortcut, answering from your guides.
The problem
Onboarding questions arrive as churn
A trial user who cannot work out how to connect their calendar does not file a ticket. They close the tab. The answer was on page 4 of your getting-started guide.
How PageTruth handles it
What changes
One script tag
Load the widget once in your app shell. Open it from your own Help menu with PageTruth.open(), or let customers press ⌘K.
Ask on their behalf
Call PageTruth.ask("How do I connect Google Calendar?") from an empty state or a tooltip to answer before they have to type.
Stays out of the way
The panel slides in beside your UI instead of covering it, so the customer can follow the steps as they read them.
What to put in the knowledge base
- Getting-started guides
- Feature walkthroughs
- Integration setup pages
- Video transcripts
What to watch in insights
- Top questions by page
- Which screens generate the most questions, so product knows where the UI is unclear.
- First-week questions
- What new accounts ask in their first days, separated from long-time customers.
- Unanswered setup steps
- Setup questions the docs missed, ready to turn into an article.
Other ways teams use it
- Support deflectionAnswer the repeat questions before they become tickets, and hand the rest to your team with context.
- Developer and API docsLet engineers ask your API reference a question and get the endpoint, the parameter and the example.
- Implementation and customer successGive B2B customers a private knowledge base for their rollout: runbooks, SOWs and training notes.
Give your customers answers, not a ticket number
Point PageTruth at your docs, publish a help center and drop the widget into your app. The free plan is enough to see it answer your own questions.