Turn a Messy Backlog into a Clear Signal
Clearing a large idea backlog and keeping it healthy afterward, with the admin console and the UserVoice MCP.
On this page
Clearing a large idea backlog and keeping it healthy afterward, with the admin console and the UserVoice MCP.
What we are trying to accomplish
A backlog the team can trust: every open idea has an owner and a status that reflects reality, duplicates are consolidated so votes count in one place, and the customers who shared an idea get a clear answer.
By the end you should have
- A smaller, cleaner set of open ideas the product team can plan from.
- Closed ideas that were closed thoughtfully, with a message that explains why and where to go next.
- An intake process that keeps the backlog from building back up.
The work runs in two tracks that start together: a cleanup pass (Steps 1 to 3) and a few intake changes that make it last (Step 4).
Ask Claude, or any MCP-compatible assistant, about your ideas in plain language. It can apply labels, assign owners, set internal and public statuses (25 ideas at a time), merge duplicates, and link ideas to Jira or Azure DevOps. You approve each change before it happens. The UserVoice agent in the admin console can do the same, no assistant setup needed.
Use the console when a batch is bigger than 25 ideas, such as closing a whole forum, and for bulk moves between forums. Bulk merges, moves, and deletes in the console can be undone.
Find and label first, then update. Every set of ideas gets a cleanup label before its status changes, so the whole pass can be reviewed before anything reaches a customer. Update small sets with the MCP and whole forums by label in the console.
Set the rules
Agree on what should happen to each kind of idea before anyone changes a status. A shared set of rules keeps the cleanup consistent and makes it easy for a second person to review.
Start with an inventory
One prompt shows where the backlog actually sits. Most teams find it lives in a few forums and a few years, which makes the job feel smaller.
Sort ideas into buckets
Adjust the thresholds to fit your team.
| Bucket | Rule of thumb | What happens |
|---|---|---|
| Sunset product | The product is no longer taking requests | Close with a “no longer pursuing” message |
| Stale, low signal | Over 2 years old, fewer than 3 supporters, quiet for 12 months | Close with a note, or park in a private forum |
| Duplicate | Same request as an existing idea | Merge into the primary idea |
| Unclear | Title is a product name or a single word, no problem described | Ask for more detail, or close with a note |
| Keep | Everything else | Assign an owner and an internal status |
Label with the MCP, then act
Ask the MCP to apply a cleanup label (cleanup: close, cleanup: merge, cleanup: review) to each set it finds, so the whole pass can be reviewed and updated by label before anything goes out.
If you would rather review a set as a group, ask the MCP to save it as a list in the Ideas grid instead.
Choose one closing status
Pick one public status that means closed (Declined, Not Planned, or Will Not Pursue) and give it a default message under Settings › Ideas › Templated Status Messages. The message fills in whenever someone picks that status in the console, and the MCP posts it by default too, so every update starts from the same wording. You can still edit it, ask the MCP for your own text instead, or post no message. Suggested wording is in Step 2.
A closing status also closes voting. Once an idea moves to a status that isn’t open for votes, the portal shows “Voting has closed.” Whether people can still comment depends on that status’s comment setting.
Close with care
Work in order of confidence: whole forums first, then clear rules, then judgment calls.
A whole forum is a console job: filter the grid to the forum, select all, and apply the closing status with its message. This is the last update those supporters will receive, so it is usually worth sending the email.
Run the Step 1 rule with the MCP and review the list once. Then ask the MCP to set the closing status 25 at a time, or close by label in the console. If leadership would rather not decline publicly yet, move them to a private forum in the console to park them quietly, and set a date to revisit.
Ask the MCP for ideas about a product area rather than keyword-searching, so you get a ranked list with a match grade instead of every idea that happens to contain the word.
Suggested messaging
Short, warm, and specific about what happens next. Replace the brackets and keep each under 80 words.
| Situation | Message |
|---|---|
| Sunset product | Thank you for sharing this idea. [Product] is no longer accepting new feature requests, so we are closing the ideas in this forum. We appreciate everyone who contributed, and you can share feedback on our current products at [portal link]. |
| Older idea without support | We are tidying up ideas that have been open for a while without gathering support, so our team can focus on what customers are asking for most. If this is still important to you, please resubmit it with a note on the problem you are trying to solve and we will take a fresh look. |
| Not planned | Thank you for this suggestion. After reviewing it against our current roadmap, we are not planning to build this in the near term. We are keeping it on record and will update this idea if that changes. |
| Need more detail | Thanks for this idea. To make sure we understand the request, could you add a few lines on what you are trying to accomplish and what is getting in the way today? That helps us route it to the right team. |
| Merged | We have merged this idea with a similar request so your vote and comments count toward the combined idea. You will receive updates there as it progresses. |
The MCP can draft variations in your own voice:
Before you send
Status changes can’t be undone. That holds in the console and through the MCP. Merges, moves, and deletes in the console can be undone, but a status change and the email it sends are final. Review the labeled list once more before you send.
Supporters get one email per idea. Each idea in a status update sends its own email to its supporters, so someone who supported twelve stale ideas receives twelve emails. The MCP and the agent only email supporters when you ask. Teammates who captured feedback on an idea are emailed about public status changes either way, unless they have turned those emails off, so give Sales, Success, and Support a heads-up before a big close. In the console, consider turning off the notify option for large stale batches and letting the public status speak for itself.
Close rather than delete. A deleted idea disappears from the portal, your lists, and your counts, and its supporters never hear what happened. A closed idea keeps its history and tells people the outcome.
Mark spam as spam. If the cleanup turns up junk submissions, mark them as spam rather than closing them, so they leave the portal and help train the spam filter.
Merge duplicates with the MCP
Merge after closing, so you are not reviewing matches on ideas that are about to be declined. Merging moves votes, supporters, comments, and feedback onto the primary idea, leaving a shorter list with stronger signal.
- Ask the MCP to cluster. It groups by meaning rather than by keyword, so paraphrased requests land together.
Find groups of open ideas in [forum] that ask for the same thing. For each group, list the ideas with supporter counts and explain in one line why they match.You
- Let it suggest the primary. Most supporters first, then oldest, so the idea with the most history survives.
For each group, suggest which idea should be the primary and label the others cleanup: merge.You
- Review, then merge. Look over the groups and adjust anything that seems off. Then filter the grid by cleanup: merge and use bulk merge in the console, which you can undo if a group was wrong. The MCP can also merge a group directly (up to ten ideas into one), but the assistant can’t undo a merge, so save it for groups you are sure about.
- Use Merge Match as a second pass. The grid’s Merge Match filter shows its own suggested pairs, limited to ideas inside your current filters. It is a helpful check after the MCP pass, and it gets better as custom questions (Step 4) collect clearer descriptions.
Catch duplicates as they arrive
Decide whether a merge should email voters. The console’s merge dialog emails subscribed voters unless you untick it; the MCP merges without emailing unless you ask. Someone who supported several of the duplicates is counted once on the primary idea.
Keep it clean
These can start in the same week as the cleanup. Each one addresses a source of the backlog, so the cleanup holds.
Add custom questions to the portal’s idea form. Ask “What are you trying to do?” as the one required question, and “What stops you today?” as an optional one. They give PMs what they need and give Merge Match something to compare.
A short note on what makes a good idea, what happens next, and when to expect a response reduces incomplete submissions and sets expectations kindly.
Ideas tend to stall where no one owns them.
For ideas in the Unclear bucket that are worth keeping, the MCP can rewrite the title and move the idea to the right category.
Set a gentle SLA and check it weekly
An internal status within 14 days and a public status within 30 is a reasonable starting point. If your AI client supports scheduled tasks and has Slack or email connected, it can run the check every week.
Use auto-label suggestions and review them monthly
Auto-labeling suggests labels for new ideas, and an admin accepts them. It will occasionally miss, so a quick monthly check keeps things tidy.
Link kept ideas to engineering work
When an idea in the Keep bucket already has a Jira issue or Azure DevOps work item, the MCP can link the two, so the ticket points back to the customer request and the idea shows the work behind it.
Hold a 30-minute weekly triage
New ideas get an owner, an internal status, and labels within the week. The MCP can write the agenda: new ideas since last week, ideas that crossed a supporter threshold, and ideas past SLA.
Read next
Get the full guide
We'll email you the 13-page PDF. It adds two things that aren't on this page:
- A 15-step checklist to put the guide into practice
- Ten AI prompts for Claude, ChatGPT, or your assistant of choice, all using the UserVoice MCP to work with your own feedback data
