Suggestions while someone types
Once someone has typed three or more characters of a title, the form shows up to four existing posts with similar titles under the heading Similar posts — vote instead?, the most-voted first. Many duplicates are never created because the person votes on the existing post instead, which is the outcome you want, since it concentrates demand in one place.
The suggestions match on the words in titles; they are not an AI judgement of meaning, so a request worded very differently can still slip through. The Chrome extension runs the same kind of title search as your team types, before they file a request.
Merging a duplicate
A merge moves the duplicate's votes and comments onto the post you keep. Votes are counted once per person, so someone who voted on both counts once. The duplicate's author, commenters and followers become followers of the kept post, so they hear about it from then on.
The duplicate is closed and becomes read-only, with a Merged into notice linking to the kept post, and its old address redirects there, so links in emails and tickets keep working. The kept post shows how many duplicates were merged into it, and one merge notification goes out.
- 1Open the duplicate post and open its menu.
- 2Choose Merge into another post….
- 3Search for the post to keep by title, then select it.
Merging several at once
In the admin Posts inbox, select the duplicates, then use Merge into… to pick the post to keep. Merges are also available through the REST API and to AI agents through the MCP server.
Check before you merge
There is no undo for a merge in the web app, so check which post you are keeping before you confirm. Merging the wrong way round leaves the votes in the right place but the wrong title and description on the surviving post. The only undo is a 24-hour undo offered to AI agents that made the merge through the MCP tools.
What a merge does to points, notifications and integrations
If rewards are on, voters and commenters keep the points they earned on the duplicate. The duplicate's author loses the points that post earned, so posting the same request twice never pays twice.
A merge also sends the post.merged event to your webhooks, so a relay, spreadsheet or reporting job built on the API can follow the move instead of pointing at a post that no longer stands alone.
When not to merge
Merge when two posts ask for the same outcome, even if they are worded differently. Do not merge when they share a feature name but describe different problems: CSV export for accounting and CSV export for a data warehouse may need different solutions, and merging them hides which customers need which.
When in doubt, keep both and link them to each other in a comment. A later merge is easy; separating votes after a merge done too early is not possible.