Use case
Feature request tracking software
Track feature requests from every channel on one board: merge duplicates, rank by votes, show status and tell requesters when it ships.
- Steps in the loop
- 4
- Members
- Unlimited
- To first board
- < 10 min
- To start
- Free
The problem
What this usually looks like today
Feature requests arrive everywhere: a line in a support ticket, a remark on a sales call, a reply to an onboarding email, a thread in Slack. Each one is logged where it landed, if it is logged at all, so the same request exists five times in five wordings and nobody can say how many customers asked, which accounts they were, or whether anyone told them when it shipped.
The loop
How Looph handles it
Four moves, one workspace — no re-entry between them.
- 01Capture requests where they arrive: customers post on the board, the Chrome extension posts from any page, and the Slack message shortcut turns a message into a post. When support or sales hear a request, they post it themselves and note which customer asked in a team-only internal note. An in-product widget is coming soon.
- 02Stop duplicates at the source: similar posts surface while someone types a title, and merging moves votes, comments and followers onto one request.
- 03Rank by demand you can see: sort by top votes or trending, filter by status and tag, and tag requests by segment or account so you can see who is asking. On Growth and Business, the Segment integration adds sorting by the MRR and number of customers behind each request.
- 04Show status and close the loop: statuses drive the public roadmap, and publishing a changelog entry linked to the post can mark it Complete and tell everyone who voted or followed it. From Starter up, a post linked to a Jira or GitHub issue moves as the issue does.
A worked example
One request, from first mention to shipped
An illustrative team, not a customer story. Every step uses features described in the docs.
A customer writes to support asking to export a filtered view as CSV. The support rep searches the board, finds a similar request with eleven votes, adds an internal note saying which customer asked, and sends the customer the link so they can sign in and vote. A week later a prospect raises the same need on a sales call; the account executive adds the account to the internal notes and shares the link too.
At planning, the product manager sorts the board by top votes and filters by the enterprise tag. The export request is near the top, so it moves to Planned, appears on the public roadmap, and the product manager creates the Jira issue from the post. When engineering finishes, the issue moves to Done and the post follows it to Complete. The product manager then publishes a changelog entry linked to the post, which tells all thirteen voters it shipped, including the customer who first wrote to support.
Nobody kept a spreadsheet, and nobody had to remember who asked. On Starter that costs $19/mo for the workspace, with every support and sales colleague invited as a free member and up to 1,000 customers voting.
Questions
Frequently asked
More use cases
Other teams running the same loop
Customer feedback management for SaaS product teams
Stop triaging feature requests in spreadsheets and Slack threads: collect every request on one board, rank it by votes and tell voters when it ships.Feature voting and roadmaps for mobile app teams
Collect feature requests and bug reports from iOS and Android users in one place, and close the loop with changelog updates that notify voters.A shared feedback system for enterprise CS and product
Give enterprise CSMs a structured way to log customer asks and prove they're heard — without another spreadsheet or QBR slide.
Related
Features and templates for this workflow
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime