At a glance
Key takeaways
- Capture the outcome the customer wants, not only the feature name they suggested.
- Group requests by the problem behind them, and count the customers, not the messages.
- Use votes as one signal beside customer impact, frequency, strategy, and effort, and answer every request.
Why feature requests get messy so quickly
The same idea arrives in five forms: a support ticket, a sales note, an email, an in-app message, and a roadmap comment. If each channel becomes its own list, nobody knows whether demand is growing or the same request is being counted five times.
The other problem is language. Customers naturally suggest a solution ("add CSV scheduling"). Your job is to understand the job they are trying to finish, who is affected, and what happens today when the capability is missing.
The feature request process in six steps
| Step | What you do | Who does it |
|---|---|---|
| 1. Capture | Log every request in one place, with the customer's words and a link to the conversation. | Whoever receives it |
| 2. Clarify | Ask what they were trying to do and how they handle it today. | Support or the founder |
| 3. Group | Merge requests that describe the same problem; count the customers behind it. | Triage owner |
| 4. Prioritize | Ask the same questions of every group (see below). | Product owner |
| 5. Decide | Build now, later, or not at all, with a review date for "later". | Product owner |
| 6. Answer | Tell each requester the decision, and again when it ships. | Request owner |
The feature request template gives you a form that collects steps 1 and 2 in one go.
A feature request tracker you can copy
If you are starting with a spreadsheet, use these columns. Each row is one problem, not one message:
Problem (in the customer's words) | Requests (links) | Customers | Segment
| Current workaround | Frequency | Impact | Status | Owner | Next review | Decision and why
- Problem: "Sending the same report to clients every Monday by hand", not "scheduled exports".
- Requests: links to each original ticket, email, or submission, so you can reply to everyone later.
- Customers: the number of distinct customers, not messages.
- Status: received, evaluating, planned, building, shipped, or declined.
- Decision and why: one sentence you could say to a customer.
Worked example: one month of requests
Here is an illustrative month for a small B2B reporting tool. Forty requests arrived: 22 through the in-app feedback button, 11 in support tickets, and 7 from sales calls.
Grouping them by problem turned 40 messages into 9 problems. Three of those problems covered 26 of the 40 requests:
| Problem | Customers | Example wording |
|---|---|---|
| Sending reports to clients by hand every week | 11 | "Add CSV scheduling", "email my report every Monday", "automate exports" |
| Can't give clients view-only access | 8 | "Client logins", "read-only users", "share a dashboard link" |
| Dashboards slow with 12 months of data | 7 | "Speed up big reports", "timeouts on yearly view" |
The team scored the three with RICE and made three decisions: build scheduled reports this quarter, investigate client access with two customer calls, and treat slow dashboards as a performance bug rather than a feature. All 26 requesters heard back within the week. The other six problems stayed on the list with a review date.
Notice the first group: "add CSV scheduling" and "email my report" sound like different features but describe one job. Before merging, check that customers really need the same outcome. One may want a personal reminder, another an auditable team distribution. If the needs differ, keep separate groups.
How to prioritize feature requests fairly
Fair does not mean "most votes wins." It means asking the same questions of every request. A feature with ten votes from casual users may matter less than a workflow blocker hurting three long-term customers.
| Signal | Question to ask |
|---|---|
| Customer impact | What becomes possible or less painful if we solve this? |
| Frequency | How many customers have the problem, and how often? |
| Strategic fit | Does solving it strengthen the product we are trying to build? |
| Confidence | Do we understand the problem well enough to choose a solution? |
| Effort | What is the smallest useful version, and what does it cost to maintain? |
When several groups compete, a quick RICE score (reach × impact × confidence ÷ effort, the framework Intercom's product team published) makes the trade-off easier to explain. Try it in the free RICE score calculator.
A request can matter without being ready to build
Take an illustrative request for "a dashboard for every client." Ask who needs access, what they must see, and what is wrong with sharing today. A new dashboard, a saved view, and a scheduled report solve different versions of that request.
Keep three states separate: evidence collected, decision made, and delivery work created. A popular item can still need research, and an accepted problem can still have an undecided solution. Create engineering tickets only after the problem is understood and selected; that keeps the request list useful for discovery and the issue tracker useful for execution.
Answer every request
Every request deserves a reply, including "not now" and "no". Acknowledge it the same day, give a clear answer when you have one, and tell the requester when it ships. How to respond to feature requests has reply templates for each outcome, and feature voting best practices covers how to read votes once requests are public.
Signs you have outgrown the spreadsheet
A spreadsheet works for the first few dozen requests. It starts to fail when:
- requests arrive from more than two or three channels and someone copies them in by hand;
- you cannot see the original conversation without searching email;
- customers ask "is this planned?" and the answer lives in a private sheet;
- nobody remembers to tell requesters when something ships.
At that point, a feature request tool earns its place: one intake form inside the product, an inbox with statuses, a public roadmap, and notifications to requesters.
How to manage feature requests in TellTide
Turn on the feature request category in the TellTide widget, and requests arrive separately from bug reports and reviews, with the page and browser attached. They land in the Features view of a private inbox, where you can search, set status and priority, and add internal comments.
When a request is ready for wider visibility, publish it to the public roadmap and place it in the right stage. Customers can vote and comment without an account, and the person who asked gets an email when its status changes. Grouping and decision notes remain a team habit; TellTide gives you the place to do it.
Manage requests in one place: Get TellTide Pro for a built-in feature request form, or start with the free feature request template.
Questions teams ask before choosing this workflow
What is feature request management?
Feature request management is the process of collecting customer ideas, clarifying the underlying need, grouping related requests, prioritizing them, and communicating decisions.
How do I track feature requests?
Keep one list with the customer's words, a link to the original conversation, the problem behind the request, how many customers share it, a status, and an owner. A spreadsheet works at first; a feedback tool helps once requests come from many channels.
Should every feature request go on a public roadmap?
No. Keep the intake list broad and publish only requests that are clear, appropriate for public discussion, and useful for validation or communication.
How do I track feature requests without a spreadsheet?
Use a feature request tool with structured intake, searchable inbox states, voting, and a public roadmap, so context and progress stay connected.
Research notes
Sources reviewed
These references support the discussion above. Specific pricing checks are dated in the article; its editorial update date does not imply that every linked page was reverified. Confirm plan availability with each vendor.
By 


