Demand you can trust
Counts are people, not clicks. Ask a teammate in an internal note on the thread, “@Raj can we size this?”, and the customer sees none of it.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 1 · Collect · Votes, comments & mentions
One vote per person per post, comments with replies and @mentions, and internal notes the customer never sees. Voting on something follows it, so the people who asked hear when it moves.
Try it
Vote to follow the post. Type @ in the reply to mention someone, and switch on Internal note to write for your team only.
Step by step
One press, once per person. From then on, they follow the post.
People comment and reply, and vote up the comments that help most.
Internal notes and @mentions sit on the same thread, out of the customer's sight.
Pin the comment that answers the post, or close the discussion with a short note.
When the post moves, everyone following it gets an email, if their settings allow it.
Who it's for
Counts are people, not clicks. Ask a teammate in an internal note on the thread, “@Raj can we size this?”, and the customer sees none of it.
Everyone who voted hears when their request moves. When a decision is made, lock comments with a note that says why, and the thread stays readable.
Voting twice through the API changes nothing, and the counts are kept by the database itself. A webhook can tell you about every new vote, and it never says who voted.
The details
Voting on a post follows it, and so does writing it or commenting on it. Followers get an email when its status changes. Taking a vote back doesn't stop someone following, because following is its own choice, and every email has a way to stop.
Comments have replies, and people can vote on comments to lift the best answer. An admin can pin one comment above the thread as the answer, or lock comments with a short note when a discussion is done. People can edit their own posts and comments.
Type @ and pick someone. They get one email, and that's all: being mentioned doesn't sign them up to the thread. When identity masking is on, only your team can mention, because names are what the workspace chose to hide.
Switch a comment to internal and only your team sees it: "Larkspur asked for this on today's call." The customer reads a clean public thread.
Admins can tidy a post's title, delete a post or a comment, and bring either back. Nobody edits someone else's comment, admins included, so nobody is ever shown saying something they didn't.
The API, the events, and what you can rely on when you build on it.
Vote and comment counts are kept by the database, so a list never has to add anything up. Each person has one vote per post. Voting twice through the API leaves one vote and sends one event, and removing a vote twice is just as safe.
Posting, voting and commenting each make someone a follower. Once they stop following, only their own Follow button starts it again, so no later vote or comment quietly signs them back up.
A mention is saved in the text as [@Name](user:<id>) and shown as the name in bold. The person gets one email, under a switch of its own that starts switched on. A mention doesn't make anyone a follower.
Who voted is shown only to your team: not on the board, not in the activity log, not in webhooks. You receive vote.added only if you ask for it by name. It carries the new total, with the voter's name and id left empty.
{ "type": "vote.added", "actor": null, "data": { "count": 249 } }You can vote and take a vote back, list comments oldest first so paging never skips one, add a comment or an internal note, and vote on comments. Comment events say which post they belong to and whether they're internal, and locking or unlocking a thread sends an event too.
Each of these is a REST endpoint and, with the same name, an MCP tool.
POST/v1/posts/{post_id}/votevote_post Safe to repeat: voting twice still counts as one vote and sends one event.DELETE/v1/posts/{post_id}/voteunvote_post Take a vote back. It's safe to repeat.GET/v1/posts/{post_id}/commentslist_comments Oldest first, in one flat list. A comment written while you page through is added at the end, so the pages you haven't read yet don't shift.POST/v1/posts/{post_id}/commentsadd_comment Reply on a post, as the person the key belongs to.POST/v1/posts/{post_id}/comments/{comment_id}/votevote_comment Add a vote to a comment, as the person the key belongs to. Voting twice still counts as one vote.DELETE/v1/posts/{post_id}/comments/{comment_id}/voteunvote_comment Take a comment vote back. It's safe to repeat. Voting on a comment doesn't follow anything, so there's nothing to unfollow.7 event types from this feature reach your webhooks. Each line shows what its data carries.
comment.createdpost_id, is_internalcomment.deletedpost_idcomment.restoredpost_idcomment.updatedpost_idpost.comments_lockednotepost.comments_unlockedno extra detailsvote.addedcountPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Votes on posts and comments | Included | Included | Included |
| Following and status emails | Included | Included | Included |
| @mentions | Included | Included | Included |
| Internal notes | Included | Included | Included |
| Pinned answer and locked comments | Included | Included | Included |
Something else? Write to us, and a person answers.
No. Only your team can see who voted. Customers see the count.
No. Writing a post, voting on it or commenting on it makes you a follower. Voting on a comment doesn't.
Your team can still see that it was there, and can restore it. Nobody can edit it into something else.
Not yet. Recording a vote for a customer is planned.
On changelog entries, yes. Posts have votes and comments instead.
Press Follow again on the post, or use the link at the bottom of any email about it.