Understand customer requests and decide what to build

A feedback board brings requests, votes and discussions together. Use the people behind those requests to understand demand, then decide which work belongs on your roadmap.

For example, customers may ask for an export. Their comments explain what they need to export; their profiles and segments help you see who needs it. Scoring helps weigh that demand against the work involved.

Collect requests where your customers are

If you do not have a feedback board, create one first. In its Board settings → Customer posting, choose whether visitors can submit requests and whether they need to sign in. Share the board link so customers can post, vote and comment.

To collect requests inside your app, install a feedback widget. If customers should use their existing app login, connect SSO. You can also record a vote for a customer after a support conversation or sales call.

Need different forms for feature requests and bug reports? Set up custom post types and fields to collect the right details for each. For example, ask for reproduction steps on a bug report while keeping an idea form short.

Your board is usable at this point. The options below help you manage the feedback as it grows.

Keep incoming feedback useful

Want to check submissions before other customers see them? Set up moderation. Turn on AI review for the submissions you want it to check. Your team can review its decisions. Posts created by team members or a portal API token follow a different moderation path, so check this when collecting feedback through your own integration.

Categories and tags help organize requests. Auto-tagging can reduce manual sorting. Merge requests only when they ask for the same outcome; merging brings the discussion and votes together. Two export requests may concern different data and need to stay separate.

Understand who needs a change

Open a request's author or voter profile to understand the customer behind it. Request activity shows other requests they created or voted on. A cluster of reporting requests may explain the export need better than one vote.

Companies bring people from the same business together. Add customer data manually or through a connection such as Stripe, HubSpot or your own integration.

Revenue on requests shows the customer revenue associated with voters. A company counts once even when several of its users vote. This is existing customer context, not a prediction of what building the request will earn.

Compare demand from different groups

Create a user segment for the group you want to understand, such as customers on a particular plan. In the feedback table, compare Voter Segment % across requests or filter by Voter segment.

For the export request, this helps answer whether demand is spread across your customers or concentrated in a group you serve. Author segment describes who submitted a request; Voter segment describes who supports it. Read their comments alongside the numbers.

Decide what to take forward

Use prioritization when you want a consistent way to compare customer demand, impact and effort. Choose a built-in framework such as RICE or WSJF, or create your own weighted model.

You can score ideas directly, review AI suggestions, or ask your team to score them. A score helps structure a decision; it does not replace the reasons customers gave you.

Connect the decision to delivery

When you choose work to pursue, create or link a roadmap item. This keeps requests connected to the work that addresses them without requiring every request to become its own project.

Update the roadmap as plans change. When a change is available, publish a changelog update explaining what customers can now do. Check which emails are sent before sending an update: status followers and changelog subscribers are different audiences.

Bring existing requests into the board

Import feedback from CSV or Excel when you already have a list. Use the API for a connection built by your developer. If a customer sent a request by email, record it and their vote, or capture it with the Chrome extension.

Work through requests with your team

Assign an owner, discuss it privately and link related work. If one post contains several requests, split it before deciding what to do with each one.

Use saved filters to return to the requests your team handles. For work that should stay private, use internal posts or restrict board access.

Reply and explain the decision

When a customer asks for something you already offer, reply with instructions and keep the answer accessible. For duplicates, declines and planned work, Reply to feedback and close the loop explains the next steps. Comment emails and status emails have separate controls; the guide links to both.

Automate repeated tasks

Use automation rules to assign requests, add tags, change status or email team members when your conditions match. To find requests that may be about the same thing, review possible duplicates before merging.