A feature feedback tool is where “could you add X?” goes to be counted. Without one, the same request turns up as a support ticket, a note from a sales call, a Slack message and a line in somebody’s notebook, and nobody can say how many people actually asked for it. With one, every request has an address, a vote count and a status, and the person who asked can check on it without emailing you again.
This page is about that job rather than about a feature list: the parts the work breaks into, what each part looks like when a tool does it properly, and how Upvoted does each one today. If you already know the job and want the inventory, the features page is the list. If you are choosing between tools, the buyer’s guide is written for that.
Most tools do four or five of these. The ones they skip come back as manual work: a spreadsheet of requests kept in parallel, or a list of people to email when something finally ships. What follows is one section per part.
When it works: nobody on your team has to decide where a request goes, and nobody outside it has to ask where to send one. Feedback that arrives somewhere else gets moved in rather than answered in place.
In Upvoted: requests arrive on a hosted board, through a widget in your own product, or through the REST API, which is on both plans. Guests can post with a name and an email, or you can require a sign-in. The widget has three shapes: the whole board, your changelog, or a plain feedback form, and it opens from a button, a link or a menu item you already have instead of a floating bubble, if you would rather.
Two things happen on the way in. New requests can be held for approval before they appear publicly, which is on both plans. On Max, a new request is tagged automatically from the tags the board already uses; it is off until you turn it on, and it never invents a tag of its own.
If you are moving from somewhere else, Upvoted reads a Canny post export and a CSV: titles, descriptions, statuses, tags and vote counts. One limit is worth knowing before you plan the move. An export gives you a number of votes, not the people behind them, so imported voters cannot be emailed when the request ships. Anyone who votes after the move is a real person again.
When it works: the board shows you demand, not the number of times people phrased the same thing differently. Duplicates are caught while they are being typed, and the ones that slip through are merged without losing the votes on either copy.
In Upvoted: while someone types a title, Upvoted lists the requests that already say something similar, with their vote counts, and links straight to them, so the vote can land on the one that exists. That hint is on every plan, because a board full of near-copies is not a Max problem.
When two requests do get filed, a Max admin merges them by searching the board for the one to keep. The votes come across, and somebody who voted for both is counted once rather than twice. The comments move with them, so the discussion is not stranded on a request that no longer exists.
When it works: you can answer “why is this one next?” with something better than a feeling, and the answer survives being repeated to a customer.
In Upvoted: votes are the base, and a collaborator’s vote is tallied apart from the public’s, so enthusiasm inside the building never quietly passes itself off as demand outside it.
On Max, an admin scores a request for impact and effort from 1 to 5, and the priority that comes out of it is votes times impact divided by effort. Each request lands in one of four quadrants (quick wins, big bets, fill-ins, money pits) so you can see the shape of the backlog rather than read it row by row. Those scores belong to your team: the public board, the widget, the API and Zapier never show them.
Two warnings keep the list honest, also on Max. A request that has sat untouched too long says so, and a status that has grown too crowded says so, before a quarter has gone by with forty things “planned”. The argument itself happens on the request, in internal comments and @mentions that customers never see, and a comment can be pinned so the next person to open it reads the decision first.
When it works: your roadmap is a page a customer can open, not a slide that gets forwarded. People check it before they file a request, which is the cheapest support you will ever get.
In Upvoted: the statuses your team already uses are the roadmap. An item can carry an estimate as a month or a quarter, shown publicly only if you choose to show it, and readers can react to one with an emoji instead of writing a comment they do not really have. When a request changes status, everyone with an account who asked for it, voted on it or commented on it gets an email, unless they have turned notifications off.
A board can also be private on Max, which is the answer when the roadmap is for a customer advisory group or for your own team rather than for the internet.
When it works: shipping closes the loop by itself. The person who asked eleven months ago finds out without anyone remembering they existed.
In Upvoted: a release note links to the requests it delivers, and when it is published, each person who filed one of those requests gets an email naming their own request. That happens for people with an account who have left notifications on, which is one good reason to let customers sign in rather than post anonymously. Release notes can be drafted and scheduled, labelled by product area, and embedded in your product with the changelog widget. Closing the loop is the part most feedback processes lose, and it is the part customers actually judge you on.
When it works: the feedback tool is not a tab somebody remembers to open on Thursdays. It arrives where the work already happens.
In Upvoted: on Max, new requests, comments and status changes are posted into Slack, Discord or Microsoft Teams, a request can be sent to Linear or GitHub as an issue, and events leave through Zapier or signed webhooks. An MCP server lets an AI assistant read the board and file or update requests for you. Board stats show how the board is moving over time, and CSV export hands the data back whenever you want it.
On both plans, a weekly digest puts the week’s new requests in the admins’ inbox, so a quiet board does not need checking daily.
A feedback board sends customers somewhere that is not your product, so how much it looks like you matters more than it sounds.
On Max, the board wears your logo, your favicon and your theme, with no Upvoted branding on the board or the widget, and emails about the board go out under the board’s own name. Custom CSS goes further: both the board pages and the widget expose documented class hooks and theme variables, so you can restyle them without waiting for us to add a setting. Your own users can be signed in with a JWT, so a customer who is already logged into your app does not make a second account to vote.
One thing Upvoted does not do: boards live on upvoted.io, with the widget for the in-app case. There is no custom domain.
Pro is one board and two seats, both admins. It includes the board, the widget, the REST API, imports from Canny or a CSV, holding new requests for approval, the duplicate hint, the roadmap with estimates and emoji reactions, release notes with scheduled publishing and the emails to whoever asked, per-request voting stats, realtime and email notifications, and the weekly digest.
Max lifts both limits to unlimited boards and unlimited seats, splits seats into admins and members, and adds the parts that are about running a board rather than having one: priority scoring and the priority matrix, stale request and crowded status warnings, internal comments, pinned comments and @mentions, merging duplicate requests, automatic tagging, private boards, board stats, CSV export, a custom board theme, background and CSS, your logo and favicon with no Upvoted branding and emails under your board’s name, single sign-on for your own users, Slack, Discord, Microsoft Teams, Zapier and signed webhooks, Linear and GitHub issues from a request, the MCP server, and priority support.
Neither plan caps feature requests, upvotes, comments or public users. The trial is Max for seven days with no credit card, so what you are trying is the whole thing rather than a tier of it.
A place where customers file feature requests, vote on each other’s, and see what you are doing about them. The useful ones cover all six parts above: collection, deduplication, prioritisation, a public roadmap, release notes that reach the people who asked, and a way to reach the team that has to build it.
A spreadsheet handles part one and nothing else. It cannot count votes from customers, it cannot tell two people they are asking for the same thing, and it has nobody’s email address to notify when the thing ships. If you are still copying requests into rows by hand, that is the work a feature feedback tool removes.
Yes, on Max. A private board is visible only to your team or to the customers you invite. Internal comments, also on Max, let your team argue about a request where customers cannot read it, and priority scores are never published anywhere.
Yes. Upvoted imports a Canny post export or a CSV with titles, descriptions, statuses, tags and vote counts, on both plans. Vote counts come across as numbers, so imported voters cannot be emailed when their request ships.
Pro has two seats, both admins. Max has unlimited seats, split into admins and members. Public users, the people voting and commenting on your board, are unlimited on both plans and are never charged for.
If you want the whole inventory with the plan each part comes on, read what Upvoted does. If you are weighing Upvoted against Canny, Nolt, Featurebase, Frill, UserJot, Sleekplan, UserVoice or Productboard, the comparisons go through each one, including the cases where the other tool is the better answer.
If this sounds like the job you have, start a free trial. Seven days on Max, no credit card.
Indie friendly lightning fast polling you can embed anywhere or share with one click. Generate polls with AI in seconds, get detailed stats, and configure everything in seconds.
Connect Stripe, Shopify, PayPal, GitHub and 10+ other platforms. Get instant push notifications on your phone when payments land, orders ship, or subscriptions cancel.
A text RPG of private descents. AI generates a fresh dungeon in real time every playthrough, shaped by your choices and never repeated.
