# Feature Request Tracking: A Practical Guide and Template > Track feature requests across calls, tickets and Slack. Use a copyable template to preserve customer evidence, count demand and connect requests to… --- [Skip to main content](#main-content)Strategy # Feature Request Tracking: From Calls and Tickets to a Clear Roadmap Track feature requests across calls, tickets and Slack. Use a copyable template to preserve customer evidence, count demand and connect requests to decisions. cl **ClosedLoop AI Team**Oct 26, 2026 · 6 min read [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fclosedloop.sh%2Fblog%2Ffeature-request-tracking)Copy link On this page - [Start with the problem behind the requested feature](#start-with-the-problem-behind-the-requested-feature) - [Keep a needs list and an evidence log](#keep-a-needs-list-and-an-evidence-log) - [Turn six messages into two tracked needs](#turn-six-messages-into-two-tracked-needs) - [Merge evidence carefully](#merge-evidence-carefully) - [Add context before setting a priority](#add-context-before-setting-a-priority) - [Connect each request to an owner and a decision](#connect-each-request-to-an-owner-and-a-decision) - [Choose a tool by the work it removes](#choose-a-tool-by-the-work-it-removes) [Product Feedback](https://closedloop.sh/tag/product+feedback)[Customer Feedback](https://closedloop.sh/tag/customer+feedback)[Product Management](https://closedloop.sh/tag/product+management) A customer asks for single sign-on during a sales call. Another raises it in a support ticket. The first customer follows up twice in Slack. Your team now has four mentions, two customers and one problem to investigate. A list of four tickets hides that distinction. Feature request tracking connects each need to the customers who raised it, their original words and the decision your team makes. It should answer three questions quickly: who needs this, what is happening to them, and what are we doing about it? You can start with a spreadsheet. The useful part is the relationship between the evidence and the need, which should survive whichever tool you choose. ## Start with the problem behind the requested feature Save the customer's suggestion, then record the outcome they are trying to achieve. A request for an export button might mean someone needs to prepare a weekly report, move data into another system, or recover from a broken integration. Those are different problems with different possible solutions. Ask what they were doing, what stopped them, and how they handle it today. If the conversation does not answer a question, record it as unknown and follow up. An AI-generated interpretation should remain distinguishable from the customer's actual words. A useful need title describes an outcome: “Access the workspace through the organization's identity provider.” The evidence can still preserve “Please add SSO” exactly as it was said. ## Keep a needs list and an evidence log Give each underlying need a stable identifier. Keep one list of needs and a separate log of the conversations supporting them. A single need can have many evidence entries; a conversation can contain several different needs. Copy these two templates into separate spreadsheet tabs. The example rows and customer labels below are invented for this guide. **Needs list** Need ID Underlying need Affected customers Impact Owner Status Decision and next review N-01 Sign in through an identity provider A, B Access review cannot finish Product owner Investigating Confirm requirements with both customers this week N-02 Export a complete weekly report C Report preparation requires a workaround Product owner Needs clarification Reproduce the export limit before proposing a feature **Evidence log** Need ID Customer Source and link Date Original words Workflow impact Deal or renewal context N-01 A Call 1; add the source link Add date Add the exact quote Access review is blocked Add verified context, or mark unknown Keep the underlying records in a workspace your team can access appropriately. Customer conversations can contain sensitive information; a public roadmap should contain a separate, suitable description rather than copied private quotes. Do not let a broken source link become the only record of the evidence. Preserve the relevant wording and date, within your retention and access rules, alongside the link. ## Turn six messages into two tracked needs The following messages are entirely invented. Their purpose is to show how counting and grouping work, not to report customer results. Evidence Customer Message Need Call 1 A “Security needs us to use our identity provider before rollout.” N-01 Ticket 1 B “Can we sign in with our existing identity provider?” N-01 Slack 1 A “Any update on the identity-provider requirement?” N-01 Call 2 C “The weekly report export stops before all the rows are included.” N-02 Ticket 2 C “We are splitting the report into several exports each Friday.” N-02 Slack 2 A “The access review is still waiting on single sign-on.” N-01 N-01 has four mentions from two customers. N-02 has two mentions from one customer. Both needs retain every supporting conversation. The repeated follow-ups from A indicate persistence and urgency. They do not turn A into three separate customers. Similarly, the two export messages describe one customer's continuing problem, not two independent accounts of demand. ## Merge evidence carefully Before joining requests, compare the workflow, desired outcome and constraints. Similar wording alone is insufficient. “Export everything for a migration” and “Export a weekly summary for a meeting” may need different work. When the match is uncertain, leave the requests separate and record the question that would resolve it. Keep the original evidence attached if a need is later split or merged. Otherwise, your team loses the ability to explain why a particular customer appears in the count. Track unique customers and mentions separately. Where several people belong to the same customer account, distinguish the number of people reporting a problem from the number of accounts affected. Choose the measure that matches the decision, and label it clearly. ## Add context before setting a priority Frequency is a starting point. Review whether the problem blocks a task, has an acceptable workaround, affects a target segment, or has a deadline such as an access review or renewal. Attach CRM context where it is verified. A customer's annual contract value is the revenue associated with that customer; it is not automatically revenue at risk, and it is not a promise of revenue from building the feature. Keep open deals and existing contracts distinguishable, and do not add the same account value again for each mention. Then assess the work with engineering: the likely effort, dependencies, risks and fit with product strategy. The [guide to analyzing customer feedback](https://closedloop.sh/blog/how-to-analyze-customer-feedback)walks through that decision in more detail. ## Connect each request to an owner and a decision A small set of statuses is usually enough: captured, investigating, planned, shipped and declined. “Needs clarification” is useful when the evidence is incomplete. Decide who can change each status and what evidence they need. Link planned work to its delivery item in Linear or Jira. A tracker entry explains the customer need; a delivery item explains the implementation. Preserve the connection when the implementation changes or one need requires several pieces of work. Review new evidence regularly and update the decision when circumstances change. Record why something was declined or deferred, what could change that decision, and when to review it again. A stale “planned” label is a poor substitute for an honest explanation. After shipping, check whether the change addresses the original workflow, then contact the customers whose evidence supported it. A release announcement alone does not establish that their problem was solved. ## Choose a tool by the work it removes A spreadsheet can support a small evidence log when someone owns its maintenance. As conversations spread across sources, evaluate whether a tool can collect feedback, preserve its origin, group related needs, show distinct customers and connect the result to delivery. Test those steps on a sample with duplicates and ambiguous requests. Check the underlying conversations when a count looks surprising. The [product feedback tools guide](https://closedloop.sh/blog/best-product-feedback-tools)compares the different jobs these products serve. ClosedLoop AI reads feedback from connected calls, tickets, surveys and chat, turns it into product insights, and connects the evidence to customer and CRM context. You can examine the customers and quotes behind a need before deciding what to build. See the [customer feedback analysis tool](https://closedloop.sh/customer-feedback-analysis)or [book a demo](https://closedloop.sh/demo)using the kind of feedback your team actually handles. ClosedLoop AI Team We build tools that turn customer conversations into product decisions. ClosedLoop AI analyzes feedback from 44 native integrations to surface the insights that matter. [More about ClosedLoop AI →](https://closedloop.sh/) ### Get insights like this in your inbox Product insights delivered weekly. No spam. Unsubscribe anytime. Leave this field blank Subscribe Related ## More you might find useful [Strategy Jul 27, 2026 ### The Best Product Feedback Tools in 2026, Grouped by the Job They Do Eleven product feedback tools, grouped by the job they actually do, with the honest limit of each. Choose by what the tool still leaves you … 6 min read →](https://closedloop.sh/blog/best-product-feedback-tools)[Strategy Oct 26, 2026 ### How to Analyze Customer Feedback and Prioritize What to Build Learn how to analyze customer feedback, group evidence and prioritize product work using customer impact, revenue context and a practical wo… 6 min read →](https://closedloop.sh/blog/how-to-analyze-customer-feedback)[Strategy Feb 21, 2026 ### Best AI Product Discovery Tools in 2026 A detailed comparison of the 5 leading AI product discovery tools in 2026. Productboard + Spark, Dovetail, Enterpret, Chattermill, and Close… 14 min read →](https://closedloop.sh/blog/best-ai-product-discovery-tools-2026)[Browse all articles →](https://closedloop.sh/blog) --- ## More Information - Website: https://closedloop.sh - Documentation: /docs - Pricing: https://closedloop.sh/pricing - Contact: https://closedloop.sh/contact