Feature requests
Collect feature requests from people who will never sign up for a board.
The standard way to collect feature requests is to send users to a second product, ask them to create an account there, and hope they come back. Most do not. The same button that takes bug reports on your site takes ideas, from anyone, in about fifteen seconds.
Start freeNo credit card required.
What a request costs the person
- No account.
- No password.
- No second site.
- One field, and an email if they want an answer.
Same widget
One button, two kinds of feedback
Splitting bugs and ideas into separate tools is a decision that makes sense on your org chart and no sense at all to a user. They noticed something. They want to tell you. Making them work out which product to open is how you stop hearing from them.
- They choose the type
- Bug or idea, picked when they submit. Your inbox filters by it, so triage does not mean reading everything.
- Requests arrive clean
- No stack traces or screen sizes attached to an idea — the technical collection only runs for bug reports.
- Five statuses, one model
- Pending, planned, in progress, shipped, rejected. The same pipeline for both, because the reporter cares about the same thing either way.
- An email when it ships
- Move a request to shipped and the person who asked is told, in the language they were browsing in.
The trade-off, stated plainly
You lose the board. You keep the requests.
Canny, Featurebase and UserJot are built around a public board with votes, and if you want customers ranking your roadmap in public, use one of them — we say so on the Canny comparison. What you get instead is every request from the ninety-odd percent of users who would never have made an account, and a private inbox your competitors cannot read. More on why in feature requests without a public board.
FAQ
Questions
- Do users need an account to submit a feature request?
- No. They press the button on your site, type what they want and leave an email if they would like to hear back. Requiring a signup to file a request filters for your most patient users, not your most useful ones.
- Is there a public voting board?
- No. Requests land in your private inbox. A public board is a product decision with real costs — it shows your roadmap to competitors and turns every no into a thread — and this tool takes the other side of that trade.
- How do bugs and feature requests stay separate?
- The person picks a type when they submit, and you can filter the inbox by it. Bug reports also carry the browser details, errors and steps; a feature request does not need any of that, so it arrives clean.
- What happens after I mark a request as shipped?
- The person who asked for it gets an email in the language they were browsing in, telling them it shipped. That single message is the difference between one request and a user who keeps telling you things.
Ask for a feature right now.
Open the widget on this page and send us one. You will see exactly what your users see, and we will see exactly what you would see.