Use case
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.
- Steps in the loop
- 4
- Members
- Unlimited
- To first board
- < 10 min
- To start
- Free
The problem
What this usually looks like today
Requests come in from sales calls, support tickets, in-app widgets and random Slack DMs. By the time a PM sits down to plan a sprint, half of it is buried and the loudest customer — not the highest-value one — wins the roadmap slot. Nobody remembers who asked for what, so shipping it produces silence instead of goodwill.
The loop
How Looph handles it
Four moves, one workspace — no re-entry between them.
- 01Bring requests from Slack (the message shortcut and /looph submit), the Chrome extension, a CSV import and the board itself onto one searchable board. Similar posts appear while someone types a title, and the team merges any duplicates that get through.
- 02Triage from one inbox across every board: tag requests by plan tier or segment, assign an owner and filter by board, status or tag. On Growth and Business, connect Segment to sort by voters' MRR and filter by their plan or company.
- 03Publish a public roadmap that shows Planned, In progress and Complete, so 'is this on the roadmap?' stops being a support ticket.
- 04Publish a changelog entry linked to the posts it ships, and Looph can mark them Complete and notify everyone who voted, turning a backlog item into a retention touchpoint.
A worked example
A SaaS team moving requests out of Slack
An illustrative team, not a customer story. Every step uses features described in the docs.
A B2B SaaS company has four product managers, twelve people in support and customer success, and a few thousand active customers. Requests reach it through support tickets, sales calls and Slack threads, and nobody can say which ones matter most.
On day one the team creates a feature-request board and invites all sixteen colleagues as members, who are free on every plan, so nobody is left out to save money. Support uses the Slack message shortcut to turn requests that arrive as asides into posts, and similar-post suggestions point new submissions at existing posts, so votes pile up in one place instead of five.
Customers sign in with email or Google to vote, so every vote belongs to a real person, and support tags each request with the plan tiers asking for it. At planning time the PMs sort by top votes, filter by tag and move the top requests to Planned; they appear on the public roadmap, and the PMs create the Jira issues from the posts, so each post moves as its issue does. When the work ships, a changelog entry linked to those posts marks them Complete and everyone who voted hears about it. On Growth that is $59/mo for the whole company, with room for 10,000 tracked voters.
Questions
Frequently asked
More use cases
Other teams running the same loop
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.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 feedback board and roadmap for solo founders
Launch a public feedback board and roadmap in minutes. Built for solo founders who need signal without hiring a product team.
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