What a feedback board is
A feedback board is a shared page where customers post product requests, vote on the ones they want and follow each request as your team moves it through statuses. It replaces feedback scattered across email, chat, sales notes and support tickets with one list that customers can read and add to, and that your team can search, filter and answer in one place.
In Looph, the board is where the rest of the loop starts. Votes rank a post, its status puts it on your public roadmap, and a changelog entry linked to it tells everyone who followed it that it shipped. If you are weighing whether a board suits your product at all, the explainer below covers how boards compare with surveys and a support inbox, and when a board is the wrong tool.
Set up each board around a decision
Customers do not know your org chart, so create boards around the decision being made rather than the team that owns it: feature requests, bug reports, integrations wanted. Each board has its own name, description, emoji icon and colour, and you can drag boards into the order customers see them, or archive one when it has run its course. Tags are shared across the workspace and give you the finer cuts: customers filter by them on the board, and your team assigns them in the inbox.
Statuses are the public contract with the people who voted. Every workspace starts with the same set: Open, Under review, Planned, In progress, Complete, Closed and Rejected, plus Pending approval for boards that moderate first. You can rename, recolour or hide any of them except Open, so Complete can read Shipped and Rejected can read Declined. Every post shows its status history, and a status change can carry a public comment explaining the decision.
A six-step setup guide walks a new workspace from its first board and first post to a logo and colour, an invited teammate, a shared link and a first changelog entry.
Public, private and who can take part
A public board can be read by anyone with the link, on your workspace subdomain or on your own domain. A private board is visible only to your workspace members and to the people you add, either one email at a time or a whole company domain such as @acme.com. Each person you add individually gets an email telling them they have access. That suits enterprise accounts that cannot post in public, beta programmes under NDA and internal request queues.
On top of visibility, each board sets who can post, who can vote and who can comment, each one separately: anyone who can see the board, workspace members only, or admins only. A board can be open for everyone to read and vote on while only your team posts to it, for example.
Every post also has internal notes that customers never see. The restriction is enforced in the database, not just hidden in the interface, so effort guesses, account context and the reason behind a decision can sit next to the public thread. If a post belongs elsewhere, move it to another board: its votes, comments and followers go with it, and its internal notes stay visible to your team only.
Search, filters and the team inbox
On the board itself, search runs full-text across titles and details from the second character typed, and the / key jumps to the search box. Status and tag filters each take several values and stack with search. Customers can sort by Trending, Top voted, Newest, Oldest or Recently updated, or narrow the list to their own votes, their own posts or the posts they follow. The list loads 50 posts at a time, and new posts, votes and comments appear without a refresh.
Your team works from an inbox across every board, filtered by board, status and tag, or by the posts assigned to you. From there you can change status, add tags, move posts between boards, merge or delete them in bulk, assign an owner who is notified, and export the current view to CSV.
Duplicates and merging
From the third character of a title, the post form shows up to four existing posts with similar titles, most-voted first, under the prompt to vote instead. Each post page also lists related posts, so readers find the existing request before they write a new one, and the demand stays on one post.
When a duplicate does get through, merge it. Its votes move to the post you keep, and a person who voted on both is counted once. Comments move too, and the duplicate's author, commenters and followers start following the post you keep. The duplicate closes, shows which post it was merged into, and its old link takes readers there. Followers get one notification about the merge, and posts can be merged in bulk from the inbox.
Moderation
Each board can require approval before posts go live. With it on, new posts wait in a moderation queue until a moderator approves them, or rejects them with a reason, and the author is told either way. Posts written by your team skip the queue. With approval off, posts publish immediately.
A workspace word list works on every board: a post that matches it is held for approval, and a comment that matches it is blocked. You can ban a person by email with a reason, and unban them later, and any post or comment can be deleted or removed as spam.
Votes, follows and notifications
Each person gets one vote per post, and can take it back. Voting needs a sign-in, so every vote belongs to a real account: a visitor who clicks vote is asked to sign in, and the vote is cast when they return. Posts that cross 10, 25, 50, 100, 250, 500 and 1,000 votes notify their author and followers.
Writing a post, voting on it or commenting on it makes you a follower, and anyone can follow a post or subscribe to a board by hand. Followers hear about status changes, merges and the changelog entry that ships their request, by email, in the app and by push, and each person chooses which of those they receive. The same status announced twice within 24 hours sends one email, not two, and every email carries a one-click unsubscribe. Comments thread to any depth, support @mentions of teammates and take emoji reactions.
Boards that search engines can read
Public boards and their posts are served as finished pages, with a title, description, social card and canonical link on each one, and structured data that marks each post as a discussion with its vote and comment counts. Each workspace publishes its own sitemap of public boards and their posts. Every board has its own search title, description, sharing image and canonical URL, plus a switch to keep it out of search results. Private and archived boards are never listed.
Coming soon
These are planned for feedback boards but are not available yet, so nothing on this page depends on them. Where something that ships today covers part of the need, it follows the item. This page will say when each one arrives.
Ready-made board templates with statuses and fields already set. Today: set up one board the way you want it and duplicate it; statuses and tags are workspace-wide, so every board shares them already.
Custom fields on the post form. Today: use tags for the categories a field would hold, and internal notes for details only your team should see.
Voting and posting without an account. None yet: visitors sign in with an email and password or with Google, and a vote they clicked is cast when they return.
Weighting votes by a customer's plan or revenue. Today: tag posts by plan or account and filter the admin inbox by that tag, or, on Growth and Business, connect Segment to sort the inbox by the MRR and number of customers behind each post.
A priority score that combines votes with your team's effort estimate. Today: record effort as a tag, such as Small or Large, then filter the inbox by that tag and sort it by Top.
Automatic rate limits and spam detection on the board. Today: require approval before posts go live, hold posts that match your word list, limit who can post or vote on each board, and ban people by email.
Undoing a merge from the app. None in the app yet; a merge made through Looph's MCP server for AI agents can be undone there within 24 hours.
Which plans include feedback boards
Every plan includes feedback boards, duplicate merging and moderation, and voter notifications. Free costs nothing and needs no credit card: unlimited members, 2 admin seats, 1 public board, 100 tracked voters, the public roadmap and changelog, Slack and Discord notifications and the Chrome extension.
Starter, at $19/mo, adds private boards, 1,000 tracked voters, automations, CSV import, the GitHub, Jira, Zapier and Make integrations, and the API and webhooks. Growth, at $59/mo, adds a custom domain, removal of Looph branding, the rewards engine, the Segment integration and 10,000 tracked voters. Business, at $179/mo, removes the limits on admin seats, boards, voters and automations and adds an admin IP allowlist. Members are free on every plan. Single sign-on is not on any plan yet.