What is a feature request?

Feature requests arrive however customers happen to reach you: a support ticket, a tweet, a sales call note, a one-off email. On their own, they're just scattered opinions — the value comes from collecting them in one place, letting other customers add their voice, and treating the volume of agreement as a prioritization signal rather than reacting to whichever request was loudest or most recent.

Not every feature request should be built. Some conflict with the product's direction, some are one-off needs that don't generalize, and some are really a symptom of a different problem. The discipline is separating the request (what someone asked for) from the underlying need (why they asked for it), and deciding deliberately rather than by default.

How Feevox handles this

On a Feevox board, a feature request becomes an idea: customers submit it, others vote on it (one vote per user or IP, so counts stay honest), and it moves through a visible status pipeline — Pending, Under Review, Planned, In Progress, Completed, or Declined — so the person who asked can see what happened to it.