Use case · Release notes and changelog
“Can it do that yet?” — answered from your changelog
Your product changes every week and your docs lag behind. Sync your changelog and release notes daily so the help center knows what shipped, when, and on which plan.
The problem
Sales and support keep answering “is that live?”
A feature shipped two weeks ago, the help article is not written yet, and customers are still being told it is on the roadmap.
How PageTruth handles it
What changes
Daily URL sync
Point PageTruth at your changelog page or feed; it re-reads it on a schedule so new releases are searchable the same day.
Dates in the answer
Answers cite the release entry, so customers see when something shipped and which plan has it.
Newest wins
When an older guide disagrees with a newer release note, the assistant says which is newer instead of blending them.
What to put in the knowledge base
- Changelog page
- Release notes
- Roadmap and beta announcements
- Deprecation notices
What to watch in insights
- Feature demand
- Questions about features you do not have yet, counted.
- Adoption questions
- What customers ask about new releases in their first weeks.
- Stale docs
- Articles contradicted by a newer release note.
Other ways teams use it
- Support deflectionAnswer the repeat questions before they become tickets, and hand the rest to your team with context.
- In-app onboarding helpA side panel inside your product that explains the screen a new user is stuck on.
- Developer and API docsLet engineers ask your API reference a question and get the endpoint, the parameter and the example.
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.