Customer Feedback for Product Managers
Triage your area, write specs from real customer words, and close the loop on what you ship.
On this page
Product managers own an area of the product: they triage what comes in, decide what to build, write the spec, talk to customers, and tell them what happened. This guide covers what customer feedback gives a product manager, the UserVoice features you'll use every week, how it fits with analytics and research, and a routine that keeps your area current.
Why feedback matters to you
Analytics shows what customers do. Feedback tells you why, and what they need that your product doesn't do yet.
Customers describe what they're trying to do and where it breaks. The solution they suggest may be wrong. The problem is real.
A missing capability leaves no usage data. Customers who need it can still tell you, often in the same words.
Votes, accounts, revenue, and importance on one idea show who needs something and how much.
People who hear back keep sharing. People who never hear back stop.
What UserVoice gives you
| You need | UserVoice gives you |
|---|---|
| One place for your area | Ideas from your portal and every customer-facing team |
| Who is asking | The people, accounts, and revenue behind each idea |
| Context for a spec | Every customer's own words on an idea, and the issues it links to |
| A way to close the loop | Status updates that email the people who asked |
Start from the question. Analytics answers how many and how often. Research answers why, in depth. Feedback shows what's missing and who needs it.
Features to know
These are the parts of UserVoice a product manager uses week to week.
Filter and sort ideas by revenue and accounts. Save a grid view for your area.
Select an idea to see its feedback, supporters, accounts, and status in one panel.
Suggested duplicates on the idea grid. Votes and feedback move to the idea you keep.
Ideas by status, filtered to your area or one account. Drag a card to update it.
A public status and message, emailed to subscribers. Internal statuses track your workflow.
Link ideas to the issues that answer them. Linking never changes an idea's status.
Getting to the data
Most product managers work as admins, so they can triage, merge, and post updates.
| Way in | Best for |
|---|---|
| A saved grid view | Weekly triage of your area |
| The Idea Status Board | Seeing what's stuck, or what one account is waiting on |
| Jira or Azure DevOps | Customer context while you plan and write tickets |
| The agent and MCP | Themes, quotes for a spec, and drafts of updates |
A routine for your area
A short routine you keep does more than an elaborate one you skip. Adjust it to your release cycle.
| When | What to do |
|---|---|
| Weekly | Open your grid view. Merge duplicates with Merge Matches, give each new idea an owner and an internal status, and answer comments. |
| Before a spec | Read the feedback on the idea sheet. Ask its subscribers one question, such as “What do you do today instead?”, with Email subscribers. Link the idea to its issue. |
| Every release | Post a public status update on what shipped, with Notify users, so subscribers and the teams who captured feedback hear about it. |
| Quarterly | Sort your area by revenue and accounts, and bring the top ideas into planning next to analytics and research. |
Go deeper
| Guide | Read it for |
|---|---|
| Strategies for Forums, Categories, and Labels | Forums, categories, labels, and owners for your area |
| Prioritize by Revenue, Not Just Votes | Account data, segments, and Account Insights |
| Linking Customer Feedback to Jira and DevOps | What each side shows once ideas are linked |
| Closing the Loop with Statuses | Statuses, messages, and who gets notified |
| Customer Feedback for Designers and Researchers | Recruiting from an idea's supporters |
Ask the UserVoice agent
The UserVoice agent in the admin console answers in a table you can sort, open, and save. With the UserVoice MCP, you can ask the same questions from Claude, ChatGPT, or Codex.
| Ask | You get |
|---|---|
| Summarize the feedback on [idea], with three customer quotes for a spec. | The problem in customers' words |
| Which ideas in [forum] have the most revenue behind them and no status update in 90 days? | What to triage or decide next |
| Which ideas is [account] waiting on, and how important is each to them? | Context before a customer call |
| Draft a status update for [idea] saying it's Completed, for the people who asked. | A message to edit and post |
It sees what you can see. The agent uses your permissions, and every change waits for your confirmation.
Read next
Get the full guide
We'll email you the 6-page PDF. It adds one thing that isn't on this page:
- A six-step checklist to put the guide into practice
