How do you turn a customer request into a product decision?
Start with the task the customer could not finish. Keep the details you need to understand it, decide who can see them and record what the team will do next. When the change is available, tell the people it helps where to find it.
What should you record when someone gives feedback?
Write down what the person was trying to do, what happened and what they tried next. “I need a copy of a receipt for my records” gives the team a problem to solve. Ask where they expected to find it before choosing a solution.
Use a feedback board when several people want the same change and should be able to follow it. Use visual bug reporting when someone needs to point at the exact part of a page that failed. If the report contains private details, keep the screenshot and account information with the team that can handle it.
| What someone tells you | What to record |
|---|---|
| “I can’t download my receipt.” | If the app already offers a download, record what failed and the result they expected. |
| “Please email my receipts at month end.” | Record the task they want to do and what they do today to finish it. |
| “This receipt has someone else’s name.” | Keep the original report in the appropriate private support channel. Share only a safe summary with people who need it. |
Who should be able to see the request?
Decide who can open the board and who can read the individual request. Use a short description on a public board and keep account-specific details in a restricted record.
A request can contain a customer name, a screenshot or replies that were written for a smaller audience. Review those details before moving the request. Check who can open the destination and who can see it on the roadmap.
Choose how people identify themselves when they contribute. A person can give useful feedback without leaving contact details, but you need a way to reach them if you want to ask a follow-up question.
Compare tools
Scroll the table sideways to read every column.
| Tool | Who can see it?Where you set the audience for requests. | What happens to duplicates?Which evidence and people follow the retained item. | Who can hear about changes?How status and update audiences are chosen. | What affects cost?The entry limit or billing unit to count. | What can you keep?What you can save and what to check separately. |
|---|---|---|---|---|---|
| Canny | Separate internal ideas and portal posts. Private boards are admin-only on every plan. | Votes and comments move. Check who can see the kept post. | Voters and people whose feedback you logged can get updates. Check tracker and status rules. | Free covers 25 tracked users. Pro’s first tier covers 100. A credited post, vote or comment can count. Higher tiers cost more. | Managers or owners with permission can export a filtered Ideas CSV. No individual Insight notes or source links. |
| Featurebase | Check access to the portal, category and request. Moderation can hold a request. | The kept Request gets comments and people who asked. Insights hold the evidence. | Status changes add internal notes to linked Support conversations. Portal updates and Support replies are separate. | One full teammate seat on Free. Paid full seats are priced per teammate. Customers need no seat to give feedback. | Workspace Request CSV has author details and requester counts. A separate CSV lists people for one Request. |
| Frill | Guests give a name and email. Anonymous users give neither. Private ideas require Privacy. | Votes and comments move. Voters and commenters then follow the kept idea automatically. | Followers can get status updates. Choose announcement email when publishing. Anonymous users get no notifications. | Startup covers 50 active ideas. Business has unlimited ideas. Teammates and tracked users are unlimited. | Separate feedback and user CSVs. Check for vote and comment detail. |
| Nolt | Use a public or private board. Pro adds password and domain restrictions. | Merge similar posts into the one you want to keep. | Choose comment, status and merge notification audiences. People can opt out. | Global Essential includes one board. Pro includes five. Both list unlimited users and content. | Request a CSV on any plan. The real-time export API is on Pro. |
| Sleekplan | Collect suggestions through a portal or app widget. Check the board audience. | Merge posts that need the same change. Sleekplan says votes and subscribers come with the merge. | Link shipped changes to the original requests. Check announcement settings. | Billing is per workspace. Private boards are a paid feature. | Sleekplan documents feedback and changelog CSV. Inspect the columns you need. |
| Productboard | Keep evidence internal. Anyone with a private portal link can open the visitor view. | Link separate feedback notes to the same feature and retain each reason. | Portal card updates can reach voters or people with linked insights, depending on what you select. | Count makers who manage product work separately from contributors. | Export features to CSV as a maker or admin. Feedback has a separate export. |
| Fider | Choose the managed board or host it yourself. Check the private-site setting. | Mark a post as a duplicate. Its votes are added to the original. | Update the retained post. Its status explanation is visible to visitors who can see it. | Cloud Free lists a fair-use limit of 250 requests. Pro adds moderation and unlimited feedback items. | Posts are available through the API. Verify which other records and files you can preserve. |
| Quackback | Choose board rules for viewing, voting, commenting and submitting. | Merge duplicates and count each distinct voter once. The duplicate links to the retained post. | Subscribers can follow status or comments, subject to notification preferences. | Cloud Free lists one seat, one board and 50 posts. Private boards start on Business. | Eligible Cloud tiers offer a board CSV and workspace download. Self-hosted recovery needs database and files. |
| Marker.io | Widget reporters follow their own issues. Check which reports invited guests can see. | Compare the screenshot, screen size and steps before treating two reports as one issue. | Reporters can receive email for comments or resolution. | Count team members. Team includes session replay and developer diagnostics. | Admins or managers on Team or higher can export a CSV with screenshot links. |
| BugHerd | Collect pinned comments from project reviewers. On Premium and above, check the default client sharing. | Compare pins and expected fixes. Similar-task detection is a Premium and Enterprise beta feature. | Set whether clients receive a Done email for tasks they created. | Compare included team members and the client controls you need. | Pricing lists CSV, XML and JSON export across plans. Check attachments separately. |
When should two requests become one?
Merge requests when the same change would help both people finish the same task. Keep the clearest description and retain each person’s reason for asking. Check which votes, comments and followers the tool moves to the request you keep.
Two requests can sound alike and still need different work. Downloading a receipt helps someone who needs one today. An automatic monthly email helps someone who collects receipts in batches.
Use votes to find people you can ask about the problem. Consider how often the problem happens, how much work it creates and what customers do to get around it. Look for evidence from people who did not vote.
When should you mark work planned or shipped?
Mark a request planned when the team has decided to work on it. Give it an owner and a clear result to check. Mark it shipped after you verify that customers can actually use the change.
An update should say what changed and where to find it. “Open a completed booking and choose Download receipt” gives the reader something to do. Give a delivery date only when the team has a basis for it.
A roadmap status, a reply and a release announcement can reach different people. Check the actual recipients and any connected tools before making a live change. A merge can also change who follows the request.
Can you trace one request from report to release on paper?
Use a fictional booking app and four made-up reports. Keep the rehearsal on paper, including the merge, status and notification decisions.
- Sort the reportsWrite “I need to download a receipt for my records,” “I need a receipt file to share with finance,” “Please email my receipts at month end” and “A receipt shows a name I don’t recognize.” For each one, write the task or failure behind it.
- Keep the right details with each requestGive the first two one title, “Download a booking receipt,” and keep both reasons in the notes. Keep the monthly email separate. Put the account-specific report in the private support column and keep its details off the public card.
- Write the result you would verifyAssign one fictional owner. A customer should be able to open their own completed booking, download the receipt and find the expected details in it. On the paper card, mark the request planned after the team agrees, then mark it shipped only after imagining that check passes on the released version.
- Draft the update and its audienceWrite where the customer can find the download. List separately who could see the roadmap entry, who follows the request after a merge and who subscribes to announcements. Leave the update unsent.
What should you keep before moving to another tool?
Save a copy of the feedback and the decisions behind it. A CSV opens in a spreadsheet and may give you titles and totals. You may need a separate file or notes to keep individual votes, comments and source context.
- Check a sample with an original request, a discussion and a status. Verify what the destination can import before you retire the old board.
- Keep contact details and private feedback with the people allowed to read them. Record which settings control the audience, statuses and notifications so you can set them up again.