A public feedback board for your SaaS, in the same plan as support
Feature requests turn up in support chats and emails and then get lost. A feedback board gives them one public home: customers suggest, upvote and comment, and you set a status.
By the Roper team · Published
The short answer
Roper includes a public feedback board with suggestions, one upvote per visitor, comments and statuses (Under review, Planned, In progress, Complete, Closed). Embed it in your app with one script tag, build your own interface on the Feedback API, or link to the hosted page. It is part of every plan, so you do not need a separate feedback tool.
Roper is made by the team that wrote this post. Figures for other tools come from their own public pages, listed under Sources, and are list prices in US dollars that can change.
What customers can do
- Suggest a feature with a title and a description. The author's upvote is added automatically.
- Upvote the ideas they want. One vote per visitor per post; clicking again removes it.
- Browse by Top or New, filter by status and search titles and descriptions.
- Comment on a post. Replies from your team are highlighted and labelled Team.
There are no accounts to create. If your app passes a user id, votes follow that user across devices; otherwise they follow the browser.
What you can do
| Status | What customers see |
|---|---|
| Open | Under review |
| Planned | Planned |
| In progress | In progress |
| Done | Complete |
| Closed | Closed |
Three ways to use it
- Embed in your app. Put an empty element where the board should appear and load the
feedback.jsscript with your workspace key. The board's height follows its content, so there is no inner scrollbar. - Build your own interface. The Feedback API lets you list posts, vote and comment from your own UI.
- Link to the hosted page. Every workspace has a board at
/w/<your-slug>/feedback. See the sample board.
Why keep it next to support
Support is where feature requests start. When a customer writes "can you add X?", you can point them to the board, so the request is counted once instead of living in ten threads. You decide what to build from votes, not from whoever wrote last.
What it does not do
- It does not merge duplicates automatically. You delete or close them.
- It does not import requests from other tools or from support chats.
- It is not a full roadmap or changelog product.
- Votes are not verified unless your app passes a user id. Anonymous votes follow the browser, so clearing storage lets someone vote again.
Questions
Common questions
- Is the feedback board a separate product?
- No. It is part of every Roper plan, starting at $19 a month, and uses the same workspace as your inbox and help center.
- Can I embed the board in my app?
- Yes. Add an empty element and the
feedback.jsscript with your workspace key. The board sits on your page's background and resizes to its content. - Do customers need an account to vote?
- No. Votes follow your user id if your app passes one, and otherwise the visitor's browser.
- Can I stop spam?
- Posting is rate-limited and has a honeypot field, and you can delete any post. You are still responsible for moderating what appears on your board.
- Is it a replacement for Canny or Featurebase?
- For a small team that wants votes, comments and statuses next to its support inbox, often yes. It does not match their integrations, duplicate merging or roadmap views. See Roper vs Featurebase.
Keep reading
Sources
Answer the repeat questions once, and keep the human path open.
One inbox, one help center, one flat price. $19 a month for Pro.