---
title: "Merge two conversations: which one stays"
description: "To merge a duplicate into the conversation you want to keep, open the duplicate first and pick the one that stays."
url: https://help.gleap.ai/en/articles/16751959-merge-two-conversations-which-one-stays
collection: "Inbox and tickets"
updated: 2026-11-16
language: en
---

# Merge two conversations: which one stays

To merge a duplicate into the conversation you want to keep, open the duplicate first and pick the one that stays.

When the same customer writes twice about one problem, or one problem arrives by email and by chat, merge the two so your team answers once. Anyone who can work the inbox can merge.

**Rule: open the conversation you want to get rid of, then pick the one you want to keep.**

1.  Open the duplicate, the conversation that should disappear.
    
2.  In its **⋯** menu, choose **Merge with similar**, then search for and click the conversation you want to **keep**.
    
3.  Check the **Merge ticket** dialog. The conversation you started from is on the left, and the arrow points to the one you picked, which is marked with a target icon. That one is the one that stays.
    
4.  Click **Merge**.
    

![Ticket actions screen in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/3L4G5WMKuLpKcCobtJr2WJYAKppIPMrdGgu2iKnPteK1bp77WBs4Up4wH3aIsNIiATbwt5d6CvA.png)

Afterwards, the kept conversation gets the duplicate's contacts, tags, upvotes and linked tasks, plus an internal note that names the merged conversation and usually summarises it. The duplicate's messages stay in the duplicate, which is **archived and linked** to the kept one. It isn't closed and keeps its status, so if it needs to read _Closed_ in your reports, close it before you merge.

> **Warning:** A merge can't be undone. The duplicate's contacts are added to the kept conversation and can see all of its messages, so don't merge conversations from different customers who shouldn't see each other's messages.

_Example: to keep #937 and get rid of #940, open #940, choose Merge with similar, pick #937, and confirm when the preview shows the title of #940 on the left and the title of #937 on the right._

Merge before you reply where you can. Merging after two people have answered separately leaves a thread that reads oddly. For thirty customers reporting the same outage, use a tracker instead of merging.

### Related

-   [Merge, snooze and archive conversations](https://help.gleap.ai/en/articles/303-merge-snooze-and-archive-conversations.md)
    
-   [Link tickets and group an outage under one tracker](https://help.gleap.ai/en/articles/301-link-tickets-and-group-an-outage-under-one-tracker.md)
    
-   [How the inbox works](https://help.gleap.ai/en/articles/291-how-the-inbox-works.md)
