Templates
Feedback board templates: setups that work, and why
Eight recommended board setups — feature requests, bug tracking, public roadmap, changelog, beta feedback, customer portal, internal IT and design review — each with the statuses, tags and setup steps to follow in Looph, and why. You set each one up by hand for now; one-click templates are coming soon.
Each template is guidance, not a preset: statuses are renamed from Looph's built-in set, tags are created in your workspace, and every setup step links to the doc that covers it.
- Templates
- 8
- Setup steps, each documented
- 49
- On every plan
- Free
- Members
- Unlimited
8 templates
Pick a starting point
Each one lists the statuses, tags and details to ask for that the workflow actually needs, with the steps to set them up.
- 01
Feature request board template
Product teams that need a single public place to collect and prioritize customer-driven feature ideas. - 02
Public bug tracker board template
Teams that want bug reports separated from feature requests, with triage by impact that reporters can follow. - 03
Public product roadmap template
Any team that wants to publicly show what's coming next and reduce 'is this being worked on?' questions. - 04
Changelog page template
Teams that want shipped work to automatically close the loop with the customers who asked for it. - 05
Beta feedback board template
Teams running a private or invite-only beta that need structured, votable feedback before a general release. - 06
Customer feedback portal template
B2B teams and agencies that want a single branded destination per account instead of scattered email threads. - 07
Internal IT request board template
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet. - 08
Design feedback board template
Design and product teams collecting structured critique on in-progress work from stakeholders or users.
Side by side
What each template recommends
A template is a recommended set of statuses, tags and things to ask for in the post details. The counts below come from each template's own page, along with the lowest plan it works on as described.
| Template | Statuses | Tags | What to ask for | Lowest plan |
|---|---|---|---|---|
| Feature request board | 6: Open, Under review, Planned, In progress, Shipped, Not planned | 5 | 4 | Free |
| Public bug tracker board | 5: Reported, Confirmed, In progress, Fixed, Won't fix | 5 | 5 | Free |
| Public product roadmap | 4: Exploring, Planned, In progress, Shipped | 4 | 3 | Free |
| Changelog page | 2: Draft, Published | 3 | 5 | Free |
| Beta feedback board | 4: Open, Under review, Planned, Complete | 4 | 4 | Starter |
| Customer feedback portal | 5: Submitted, Under review, Planned, In progress, Shipped | 4 | 3 | Growth |
| Internal IT request board | 5: Submitted, Approved, In progress, Complete, Denied | 4 | 4 | Starter |
| Design feedback board | 4: Open, Discussing, Applied, Not applying | 4 | 4 | Starter |
Choosing one
When each template is the right start
Taken from the “when to use it” section of each template. Each page also says when not to use it.
Feature request board template
Requests reach you through support tickets, sales calls and chat, and nobody can say which one has the most demand behind it. A public board gives every request one URL, lets customers add a vote instead of asking again, and lets you sort by demand when you plan.
Public bug tracker board template
Customers report bugs you then have to chase for details, and several people report the same bug through different channels. A public bug board shows reporters that a bug is already known, lets them vote to say it affects them too, and lets them follow it until it is fixed.
Public product roadmap template
Customers, prospects and your own sales team keep asking whether something is being worked on. A public roadmap answers that on a page they can bookmark. Because its columns are statuses on your feedback board, it stays current as you move posts rather than on a quarterly update ritual.
Changelog page template
You ship regularly, and the people who asked for things never find out. A changelog in the same tool as your board fixes that: link an entry to the requests it resolves and you can tell their voters when you publish, with no follow-up list to maintain.
Beta feedback board template
You are running an invite-only beta and want testers' feedback in one place you can triage before general availability. A private board is visible only to your team and the testers you add, and testers can still vote on each other's posts, so you see which problems are widespread rather than which tester writes the most.
Customer feedback portal template
You work with named accounts, B2B customers or agency clients, and feedback arrives in email threads and account calls where nobody else can see it. A portal gives those customers one branded place to submit and vote, see the roadmap and read the changelog, signed in with an email and password or a Google account.
Internal IT request board template
Employees ask IT and internal tools teams for the same things in Slack, by email and in the corridor, and nobody can see what has already been asked. An internal board lets them search first, vote on an existing request and follow it, while IT gets a ranked view of demand.
Design feedback board template
You share mockups, prototypes or a staging build with stakeholders or test users, and their comments end up scattered across chat threads and meeting notes. A board gives each piece of feedback its own post, linked to the frame it is about, with a status and votes from other reviewers who agree.
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