Customer Feedback for Support Teams
Capture feature requests in seconds, answer “is this planned?” on the spot, and let customers hear back.
On this page
Support teams hear about missing features every day, usually in the middle of solving something else. This guide covers what feedback gives a support team, the UserVoice features that save the most time, how to answer customers' questions about requests, and a routine that keeps capture quick.
Why feedback matters to you
Every “can it do this?” ticket is a piece of product feedback. Captured well, it stops being a dead end for the customer and a lost signal for your company.
Add the request to an idea, and the customer gets an email when it moves.
See whether a request is planned, in progress, or not planned, while the customer waits.
Point customers to an existing idea they can vote on and follow.
Reports show how much of the feedback your product team uses comes from support.
What UserVoice gives you
| You need | UserVoice gives you |
|---|---|
| Capture in seconds | The browser extension in your support tool, email, or chat, and the Slack app |
| An answer for the customer | The idea's status, and a link they can follow |
| Updates without follow-up | Subscribed customers, and you, get an email when the idea changes |
| Credit for your work | The Activity Report shows feedback by source and by team |
Feature request or bug?
UserVoice is for what customers want the product to do, not for what's broken. Sort each ticket before you capture it.
| The customer says | It's a | Send it to |
|---|---|---|
| “It used to work and now it doesn't.” | Bug | Your bug tracker or engineering queue |
| “It's down” or “it's slow.” | Outage | Your incident process |
| “How do I…?” | Question | Answer it, or link the help article |
| “Can it do…?” or “I wish it…” | Feature request | UserVoice |
| A bug that engineering says works as designed | Feature request | UserVoice, in the customer's words |
| A bug with a workaround the customer finds painful | Both | Fix it as a bug, and capture the missing piece in UserVoice |
“Works as designed” is a feature request. When engineering closes a bug as expected behavior, the customer still wants it to work differently. Capture that request so it isn't lost when the ticket closes.
Features to know
Support teams need only a few parts of UserVoice. These save the most time.
Search for the idea, add the customer's words, and subscribe them, without leaving the ticket.
Send a customer's message to an idea from Slack, with a link back to the conversation.
See ideas by status, to answer “is this planned?” in one look.
A link customers can use to vote, add detail, and follow along.
Feedback connectors. A Zendesk connector will find feedback in tickets on its own.
Getting to the data
Support agents usually capture as contributors. Team leads may also want view-only admin access for reports.
| Way in | Best for |
|---|---|
| The browser extension | Capturing from your support tool, email, or chat |
| The Slack app | Capturing from internal escalation channels |
| The Idea Status Board | Checking where a request stands |
| The UserVoice agent | Finding the right idea, and its status, by describing it |
A routine that works
Make capture part of closing a ticket, not a separate task.
| When | What to do |
|---|---|
| Every feature request | Search first, add the customer's words to the idea, and subscribe them. |
| Every bug report | Route it to engineering. Capture only the request behind it, if there is one. |
| When asked “is this planned?” | Check the idea's status, share the link, and say they'll hear when it changes. |
| Weekly (team lead) | Look for requests captured as new ideas that should have been added to existing ones. |
| Monthly (team lead) | Share the Activity Report's source chart, so the team sees its contribution. |
Add a saved reply. “I've added your request to our ideas portal so our product team sees it. You'll get an email when its status changes: [idea link].”
Go deeper
| Guide | Read it for |
|---|---|
| Rolling Out UserVoice to Sales, Success, and Support | What a good capture holds, capture tools, and launch week |
| Collecting Feedback with Your Portal | Support saved replies, and pointing customers to the portal |
| Closing the Loop with Statuses | What customers hear when an idea changes |
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 |
|---|---|
| Is there an idea about [what the customer asked for]? What's its status? | The right idea, fast |
| What are the most requested ideas from support this month? | A summary for your team lead |
| Which ideas have the most feedback from support but no status update? | Requests to raise with product |
| Find ideas similar to [request] so I can add this customer's feedback to the right one. | Fewer duplicates |
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 7-page PDF. It adds one thing that isn't on this page:
- A six-step checklist to put the guide into practice
