Feature Request Inbox
Capture, vote on and triage product feature requests.
Overview
The Feature Request Inbox is a lightweight triage queue for the suggestions that pour into product teams every day. Customer support tickets, sales call mentions, partner feedback, internal wishlist items, and roadmap candidates all need a single home where they can be captured, deduplicated, voted on, and either scheduled, parked, or politely declined. Without that home, requests vanish into Slack threads or live as one-off Jira tickets that nobody can prioritise.
This tool gives product managers and founders a place to land every idea quickly and keep score on which ones come up most often. Over time, the inbox becomes a representation of what your customers actually care about, which is enormously useful when you are deciding what to build next or trying to push back on a loud minority.
How it works
You add a request by entering a title, a description, a requester or source, and an initial category. Each request carries a status (new, under review, planned, in progress, shipped, or declined) and an internal priority. Stakeholders can upvote a request when the same idea surfaces again, so the count reflects real demand rather than recency.
Filter by status, priority, or category to focus on the slice you need. When a request is shipped, mark it complete and the inbox keeps it as a historical record so you can show customers their suggestion made it through.
Examples
- Customer-driven roadmap. Sort by upvote count to see the top ten requested features going into your quarterly planning meeting.
- Support escalation. When the same friction shows up in five tickets, log it once and link the tickets in the description rather than creating five duplicates.
- Founder triage. Spend 30 minutes a week reviewing new entries, declining what is out of scope, and promoting promising ideas to planned.
- Sales feedback loop. Capture feature gaps that came up in lost deals so they feed into the next strategy review.
FAQ
Is this a Jira replacement?
No. It sits upstream of your engineering tracker. Once a request is planned, the engineering ticket gets created in your usual tool.
Should every customer comment go in here?
Only the ones that describe a feature, change, or enhancement. Bug reports belong in your defect tracker.
Can customers submit directly?
The inbox is internal. Funnel external requests through support and have an owner log them here.
How do I avoid duplicate entries?
Search before adding. If a duplicate slips in, merge by combining notes into the primary entry and declining the duplicate.
What does declining a request communicate?
Pair the status with a short reason in notes so future questions about the decision are answered without a meeting.