HomeDocsUsing ReqioRequest categories
Using Reqio
Request categories
How the widget routes submissions into five flows, and which land on the public backlog versus the private inbox.
When a user opens the widget, the first thing they see is a short menu asking what kind of feedback they want to share. Each choice routes into its own dedicated flow and lands in a different place on your dashboard.
The five flows
The widget routes every submission through five tiles. Three categories cover a single flow each; the fourth, Error, splits into two flows sharing one category.
Make a requestFEATURESomething's brokenERROR (subtype BUG)Something was offERROR (subtype UNEXPECTED)Share feedbackFEEDBACKAsk a questionOTHER"Something's broken" and "Something was off" are both stored as the ERROR category. A nullable subtype field (BUG or UNEXPECTED) distinguishes which of the two flows a report came from, so your inbox can tell a crash apart from a surprise without a sixth category.
What users see
The widget's opening menu shows five tiles:
- Make a request: "I have an idea or feature request."
- Something's broken: a bug report, structured as what broke and what you were doing.
- Something was off: an unexpected-behavior report, structured as what happened and what you expected instead.
- Share feedback: free text plus a rating.
- Ask a question: a private conversation with the team.
Each tile leads into a flow shaped for that type of input. Users do not see a generic text box for every type of submission.
Request (Feature)
The user searches existing requests first. If their idea already exists, they can upvote it. If not, they submit a new one with a short title. Requests appear on the public backlog where other users can upvote and discuss them.
Error: something's broken
A two-step form asks what broke and what the user was doing when it happened. This structured input goes directly to your private inbox as a two-way conversation. Other users cannot see error reports.
Error: something was off
A two-step form asks what happened and what the user expected instead. Also private, also a two-way conversation, stored under the same ERROR category with the UNEXPECTED subtype.
Feedback
Free text plus a 1 to 5 star rating. Goes directly to your private inbox. Other users cannot see feedback submissions.
Question
A private, two-way conversation. The user asks something and your team replies from the dashboard Chat console. Fully private, like Error and Feedback: it never appears on the public backlog.
Public versus private
Only Request is public
Request submissions get a public entry on the backlog. Anyone using your widget can see them and vote. Commenting on that public entry is a paid feature, available on Pro and Scale. Pro +
Error, Feedback, and Question submissions are fully private. They arrive in your Inbox, not the public backlog. Only dashboard users can see them. This is enforced on the server, not just hidden in the widget, so the private content never reaches other users' browsers.
The requester's Progress view
A user who submits something can always see their own submissions in the widget's Progress tab, regardless of category. If they reported a bug, they can see when it was marked fixed. If they left feedback, they can see when the team replied. The Progress view is scoped to the individual user's own activity.
Filtering by category
In the dashboard backlog, use the category filter above the request list to view only Requests, only Errors, and so on. The inbox view defaults to showing all private submissions.