Counts that finally add up
Forty posts ask for the same export in forty wordings. Merge them into one, and the vote count shows how many people really want 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 2 · Understand · Merge & duplicates
When two posts ask for the same thing, merge the copy into the original. Votes, comments and followers move across, nobody is counted twice, and the old link still lands on a page that says where the discussion went.
Try it
Twelve people voted on both posts. Merge, watch the counts, then undo it.
Step by step
You notice a copy in a similar-post suggestion, in a search, or because a customer points it out.
You merge from the copy, so open the post that repeats the other one.
Pick the post it repeats. HeedPost checks the merge is allowed before anything moves.
Votes, comments and followers move across, and anyone who voted on both is counted once.
Unmerge puts back exactly what came across, and nothing else.
Who it's for
Forty posts ask for the same export in forty wordings. Merge them into one, and the vote count shows how many people really want it.
People who asked in their own words still hear when it ships, because they now follow the post it was merged into. Posts merged in Canny arrive merged here.
Every moved vote and comment remembers where it came from, so unmerging puts everything back. A webhook tells your CRM which post the duplicate went into.
The details
Open the duplicate, choose Merge into, and pick the post it repeats. That's it. The duplicate keeps its own title, text and author, leaves every list, and stays readable at its old link with a pointer to the original.
Votes, comments and followers. Someone who voted on both is counted once. Someone who had stopped following one but follows the other keeps following, because an active follow on either side wins.
Unmerge puts back exactly what came across. Votes and comments added to the original since the merge stay where they are.
A post can't be merged into itself, or into a post that's already merged, so merge into that one instead. It can't be merged while other posts are merged into it, so unmerge those first and every undo stays exact. And a post can't be merged into one more visible than it is, because that would publish its thread.
The API, the events, and what you can rely on when you build on it.
Before anything moves, HeedPost reads who voted on both posts. People who already voted on the original keep that vote, everyone else's vote moves across, and the original's count grows only by new voters.
Unmerge moves back only what the merge moved. That includes following: if a merge restarted someone's follow, unmerging puts their choice back the way it was.
A merge answers with a 409, before anything changes, if the post would go into itself, into a merged post, or into a more visible post. The same goes for a post that's already merged, or one that others were merged into. Two people merging at the same moment can't build a chain.
post.merged tells you the original, the title, how many votes and comments moved, and how many voters were on both. post.unmerged tells you which post came back. Slack adds a line under the post. In the REST API a merged post shows merged_into_id. Merging itself is done in the app for now.
As someone types a title, HeedPost suggests the nearest posts they're allowed to see, so nobody is shown another person's private title. Pro matches by meaning. Everywhere else it matches by words, and a suggestion never gets in the way of posting.
Each of these is a REST endpoint and, with the same name, an MCP tool.
GET/v1/posts/{post_id}get_post One post in full, with its board, status, author, tags and demand.GET/v1/postslist_posts Posts on this workspace's boards, newest first unless you choose another sort. Filter by board, status, kind or free text.2 event types from this feature reach your webhooks. Each line shows what its data carries.
post.mergedinto, title, votes, comments, shared_voterspost.unmergedfromPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Merge and unmerge | Included | Included | Included |
| Similar posts while typing | By words | By words | By meaning |
| AI likely duplicates, judged after posting | Not included | Included | Included |
Something else? Write to us, and a person answers.
No. They now follow the original, and they'll hear when it moves.
Yes, as long as the original isn't more visible than the duplicate.
Admins can merge posts, and unmerge them.
They move to the original, and go back if you unmerge.
Yes. Merge them one at a time into the same original.
So that every undo stays exact. Unmerge those posts first, or merge into this post instead.