Customer Feedback for Designers and Researchers
Find the right people to talk to, start from real problems, and test with the customers who asked.
On this page
Designers and researchers need to know where to look, who to talk to, and what customers are struggling with before a study starts. This guide covers what customer feedback gives a design and research team, the UserVoice features that matter most, how to recruit from feedback, and a routine that connects studies to what customers ask for.
Why feedback matters to you
Feedback won't replace research, but it makes research faster: it shows where the problems are, who has them, and how customers describe them.
Hundreds of requests point to the problem worth studying, before you write a guide.
An idea's supporters told you they care. Many are glad to talk.
How customers get around a gap shows what they actually need from a solution.
Invite the customers who asked to try a prototype or a beta.
What UserVoice gives you
| You need | UserVoice gives you |
|---|---|
| Where to look | Themes across ideas, ranked by customers and revenue |
| Who to talk to | Each idea's supporters, with their accounts, segments, and how important it is to them |
| How customers describe it | Every piece of feedback, in the customer's words |
| Somewhere to test | A private beta forum, by invitation |
Features to know
These are the parts of UserVoice that matter most for design and research.
Ask the UserVoice agent to group ideas into themes, then look at a theme's workarounds, challenges, and research questions.
The idea sheet lists who supports an idea, with their account and importance rating.
Ask for context such as role or use case when an idea is posted.
Invite testers, collect structured feedback, and fold it back into the main forums.
Getting to the data
Designers and researchers usually work as admins with view-only permission, plus the agent.
| Way in | Best for |
|---|---|
| The UserVoice agent | Themes, theme analysis, and finding participants |
| The idea sheet | Quotes and supporters for one idea |
| Account Insights | Choosing participants across segments |
| A beta forum | Prototype and beta feedback |
Connect studies to feedback
A few habits keep research and feedback feeding each other.
| When | What to do |
|---|---|
| Before a study | Read the themes and feedback for the area. Write the research question from what customers describe. |
| Recruiting | Invite supporters of the related ideas, across a mix of accounts and segments. |
| Testing | Run a private beta forum for the people who asked, and collect their feedback there. |
| After a study | Add what you learned to the related ideas, so the product team sees it with the demand. |
Go deeper
| Guide | Read it for |
|---|---|
| Customer Feedback for Product Managers | How feedback fits with analytics and research |
| Running a Beta Program in UserVoice | Private forums for testers, step by step |
| Custom Questions That Make Ideas Actionable | Asking for context when ideas are posted |
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 |
|---|---|
| Group ideas about [area] into themes, and rank them by number of customers. | Where to focus a study |
| For the [theme] theme, what workarounds do customers describe? | What a solution has to replace |
| Suggest research questions for the [theme] theme, based on what customers said. | A starting interview guide |
| List the supporters of [idea] from [segment], with how important it is to each. | A recruiting list |
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 five-step checklist to put the guide into practice
