The fastest way to find out whether your documentation is working is to ask the people reading it. Doxbrix adds lightweight feedback to every published page so r...
The fastest way to find out whether your documentation is working is to ask the people reading it. Doxbrix adds lightweight feedback to every published page so r...
The fastest way to find out whether your documentation is working is to ask the people reading it. Doxbrix adds lightweight feedback to every published page so readers can tell you — in one click — whether a page helped, and optionally why. That signal flows into your analytics and points you at the pages that need attention.
Configure all of this in Settings → Project → Feedback Workflows (/settings/project).
Page helpfulness
The Page helpfulness widget shows a simple prompt at the bottom of every page:
Was this page helpful? 👍 👎A single click registers a reaction. This low-friction design maximizes response rate — most readers won't fill out a form, but many will click a thumb. After they react, a Thank-you message (configurable) confirms their input.
Feedback comments
With Feedback comments enabled, a reader can leave a short free-text note alongside their reaction — what they expected to find, what was unclear, or a suggestion. This is where the why behind a low score comes from.
Request an article
Request an article lets readers ask for documentation that doesn't exist yet. Each request captures the topic they wanted and the page they were on, turning reader demand into a prioritized backlog of what to document next.
Unresolved questions queue
The Unresolved questions queue collects questions the site assistant couldn't confidently answer. It's a direct list of gaps in your docs — the questions readers asked that your content doesn't yet cover.
The Feedback settings
| Setting | What it does |
|---|---|
| **Page helpfulness** | Show the 👍 / 👎 prompt on pages. |
| **Feedback comments** | Allow a free-text note with feedback. |
| **Request an article** | Let readers request missing documentation. |
| **Unresolved questions queue** | Collect questions the assistant couldn't answer. |
| **Thank-you message** | The confirmation shown after a reader gives feedback. |
Where feedback goes
Reader feedback is aggregated so it doesn't get lost:
- Analytics — helpfulness rolls up per page and per space in analytics.
- Docs Health — low-helpfulness pages surface in Docs Health alongside quality and freshness signals.
Acting on feedback
In analytics, find your lowest-rated pages.
Feedback comments and the unresolved-questions queue tell you why and what's missing.
Use Improve with AI and Scan with AI to address issues.
Helpfulness trends over time show whether your fix worked.
Feedback and the AI assistant
These complement each other: feedback widgets tell you which existing pages underperform, while the unresolved questions queue tells you which questions your docs don't answer at all — covering both "what we have isn't good enough" and "what we're missing entirely."