Use this article to merge duplicate conversations or tickets into one primary conversation or ticket, merge several conversations at once with bulk merge, check which channels and users can be merged together, and report on merged conversations and tickets. Merging keeps all relevant information in one place and prevents duplicated effort. To merge conversations, a teammate needs the Inbox > Can merge conversations permission.
Note: Merging combines two conversations or tickets into one, and can't be reversed in the product. If you just want to associate multiple conversations with the same underlying issue or case without merging them, link them all to the same Tracker ticket instead, from the right sidebar's Links section. This keeps each conversation independently manageable while a team works the linked Tracker ticket.
How to merge a conversation or ticket
To merge a conversation or customer ticket, use ⌘ / Ctrl K or the three-dot menu and select Merge into to combine one conversation or ticket into another. You can also press ⌘ ⇧ M to open Merge into….
To choose the primary conversation or ticket, search for it in the Merge into list and select it. Each row in the Merge into list shows the conversation's assignee and team, so you can pick the right one.
You will then see a preview of what you are merging to help you verify that you are merging the correct items. If the customer has other conversations that can be merged into the same primary conversation, the bulk merge dialog opens instead, so you can merge multiple conversations at once.
If you're merging conversations from different users, the user from the merged (secondary) conversation will be added as a participant to the primary conversation. If this is the case, you’ll be shown an additional message to confirm that the users will be added. Keep in mind that merging can't be reversed in the product and may result in sharing conversation history with participants.
Note:
You can only merge conversations or Customer tickets. It's currently not possible to merge Back-office or Tracker tickets.
When merging WhatsApp conversations, the newer conversation will always be chosen as primary as long as the newer one is an open conversation. If both conversations are closed, it will pick the primary conversation to the one that the user selects and we will not show that banner.
Conversations or tickets with multiple participants cannot be merged. The Merge into search supports queries by Conversation content, Conversation title, and Conversation or Ticket ID.
Merged conversations will still have their own tracking/reporting/API details associated to when the conversation is started even after merging
How to merge multiple conversations at once (bulk merge)
Bulk merge lets you merge up to 100 of a customer's conversations or tickets into one primary conversation in a single step, so you don't need to merge each duplicate one at a time. You can start a bulk merge from a conversation or from a selection in your inbox list.
Note: Bulk merge is available in the web Inbox only. To merge conversations, a teammate needs the Inbox > Can merge conversations permission, which can be turned on under the teammate’s Inbox permissions.
How to bulk merge from a conversation
To bulk merge starting from one of the customer's duplicate conversations:
Open one of the customer's duplicate conversations. This conversation is merged into the primary conversation, so don't start from the conversation you want to keep.
Click the three-dot menu in the conversation header and select Merge into. You can also press
⌘ ⇧ M, or open⌘ / Ctrl Kand select Merge into.Under "Recent conversations", select the conversation you want to keep as the primary conversation, or type to search for it.
In the bulk merge dialog, the conversation you started from is already selected. Select the checkbox for each of the customer's other conversations you want to merge into the primary conversation.
Click Merge conversations.
The three-dot menu in the conversation header shows the Merge into… option and its keyboard shortcut. If the customer has no other conversations that can be merged into the primary conversation, the single merge confirmation appears instead of the bulk merge dialog. Nothing is merged until you click Merge conversations, and clicking Cancel changes nothing.
How to bulk merge from the inbox list
To bulk merge conversations you've selected in your inbox list:
Hover over a conversation's avatar in the inbox list and select its checkbox. Select 2 or more conversations.
Click the three-dot menu at the top of the list, or open
⌘ / Ctrl K, and select Merge into. This option only appears when 2 or more conversations are selected.Under "Select a primary conversation", select the conversation you want to keep. The primary conversation can be one of the conversations you selected (labeled "Selected") or a different conversation. Only conversations that every selected conversation can be merged into are listed.
In the bulk merge dialog, every conversation you selected in the inbox list is already selected. Clear the checkbox for any conversation you want to leave out.
Click Merge conversations.
How to choose which conversations to bulk merge
The bulk merge dialog shows one conversation at a time on the left and the primary conversation, labeled "Primary", on the right, with a full preview of each. In the bulk merge dialog, you can:
Include a conversation by selecting the checkbox in its header. Conversations that aren't selected are grayed out.
Step through every conversation, selected or not, with the arrows at the bottom of the dialog.
Select or clear all conversations with the checkbox at the bottom left of the dialog, next to the count of selected conversations.
Only conversations that can be merged into the primary conversation are listed in the bulk merge dialog. See Merge conversation/ticket capabilities for which conversations and tickets can be merged together.
If there's no conversation that your selected conversations can be merged into, the Merge into… picker shows "No conversations found" with the reason, for example "Conversations from different customers can't be merged."
If the primary conversation you select is closed, the bulk merge dialog shows a "Merging into a closed conversation" warning before you merge.
If the conversations you select would add new participants to the primary conversation, a confirmation lists those participants before the bulk merge starts. New participants may see the full conversation history once a reply is sent.
If something changes while the bulk merge dialog is open and the conversations can no longer be merged, the dialog shows "These conversations can no longer be merged. Close this dialog and try again." Close the dialog and start the bulk merge again.
What happens after a bulk merge
After you click Merge conversations, the bulk merge dialog closes and a "Merging N conversations" message appears. The merges then run in the background, one after another. After a bulk merge:
Each merged conversation is treated exactly as if it had been merged on its own. It's closed, its SLA is removed, Fin stops replying in it, a merged ticket is resolved, and a "merged" note is added to it.
Followers and replies move to the primary conversation. Followers of each merged conversation are added to the primary conversation, and later customer replies are added to the primary conversation.
One merged card is added to the primary conversation for the whole bulk merge, listing every conversation that was merged. Click a conversation ID on the card to open a preview of that conversation.
Grouped asks appear on the merged card when AI Compose & Summarize is turned on in Settings > AI & Automation > Inbox AI. The merged card groups the merged conversations by what the customer asked: each ask gets a one-line summary in your workspace’s language, and conversations about the same ask are listed together under it. Conversations with 100 visible characters or fewer are listed without a summary, under “Other conversations”. When AI Compose & Summarize is turned off, the merged card lists the merged conversations without summaries.
Conversations that couldn't be merged are reported in an "N conversations couldn't be merged" message. They aren't listed on the merged card.
Reporting counts each merged conversation as its own merge, so a bulk merge of 10 conversations counts as 10 merges.
After a bulk merge, the merged card on the primary conversation shows who merged the conversations, a summary of each customer ask, and the ID of each merged conversation. In this example, 2 conversations about the same duplicate charge are listed together under one ask.
Each merged conversation is closed and shows a "Conversation merged. Continue in the primary conversation." banner. Click Go to primary to open the primary conversation.
Bulk merge limitations
Bulk merge has the following limitations:
Up to 100 conversations can be merged in one bulk merge, including the conversation you start from.
Web Inbox only. Bulk merge can't be started from the Intercom mobile apps, and the merged card in the mobile apps names only the first merged conversation.
Not available in Operator. Operator's Merge duplicate step still merges one conversation at a time.
No bulk merge API. To merge several conversations through the API, call the merge endpoint once for each conversation.
No AI summary attribute. Conversations merged with bulk merge don't get the AI conversation summary attribute. Merging a single conversation is unchanged and keeps its AI summary.
Merging conversations and tickets from different channels
Conversations and tickets that started on different channels can be merged together. For example, a user may contact you via the Messenger, then again by email. You can merge the email conversation into the Messenger conversation to maintain a single place for handling their issue.
Note: Not all channels support merging into conversations on other channels. See Merge conversation/ticket capabilities for more information.
Once merged, you’ll see a notification confirming that the conversations have been successfully merged, with a link to continue the conversation from the primary thread.
The primary conversation will also have a notification in the thread to show another conversation has been merged into this one. You will also see a summary note added to the conversation. After a bulk merge, the primary conversation gets one merged card that lists every conversation that was merged into it.
These merge notifications can't be deleted in the interface. Please reach out to our support team if you need it to be deleted.
Note:
Merging does not append or combine the message history from the secondary conversation into the primary thread. The secondary conversation is closed and linked to the primary via a summary note and link (both conversations remain individually accessible with their own conversation IDs). Only the primary conversation can receive new messages after the merge.
Once a conversation or ticket has been merged, the secondary conversation becomes read-only. This means you can no longer change its assignee, send new messages, or update its ticket attributes through the UI or API. If you need to unassign a secondary conversation after merging, the only option is to unmerge first (contact our support team) and then make the change.
Merging conversations and tickets from different users
Merging conversation and tickets from different users is also supported, but it is disabled by default to prevent unintentional data sharing.
To enable cross-user merging, go to Settings > Workspace > Security > Data Security Settings and select "Enable cross-user conversation merging".
Once enabled, conversations and tickets from different users will be available to select when you initiate a merge. The user from the merged (secondary) conversation will be added as a participant to the primary conversation.
After the merge, if the primary conversation is on Messenger, the participants on the primary conversation will see that participants of the secondary conversation have been added.
What do customers see in the Messenger after a conversation is merged?
When a Messenger conversation has been merged into another conversation, the user won’t be able to reply to the secondary conversation any longer. If they are able to access the primary conversation within the Messenger, they'll be able to click on a button to take them there.
However, the button won't appear if the primary conversation isn’t accessible in the Messenger, for example, if it's an email conversation.
Note: Support for this in the Mobile Messenger is available with iOS SDK version 18.7.2 and Android SDK version 15.16.1. In earlier versions the "Continue the conversation" button will always appear in the Mobile Messenger. In scenarios where the user can’t access the primary conversation in the Messenger, the button won’t do anything.
Which conversations and tickets can be merged together?
The following table shows which secondary conversations or tickets (the ones merged) can be merged into which primary conversations or tickets (the ones kept), by channel or type:
Secondary | Primary | Allowed? |
Messenger | Messenger | Yes ✅ |
Messenger | Yes ✅ | |
Yes ✅ | ||
Messenger | Yes ✅ | |
Phone call | Phone call | Yes ✅ |
Phone call | Yes ✅ | |
Phone call | Messenger | Yes ✅ |
Phone call | Customer ticket | Yes ✅ |
Customer ticket | Customer ticket | Yes ✅ |
Conversation | Customer ticket | Yes ✅ |
Customer ticket | Phone call | No ❌ |
Phone call | No ❌ | |
Messenger | Phone call | No ❌ |
Note:
Tickets follow the channel rules above based on the channel they originally started on. For example, a ticket converted from a phone call is treated as a phone call, so a Messenger conversation can't be merged into it.
WhatsApp, Facebook and Instagram conversations can only be merged into conversations from the same user and on the same channel.
Slack conversations and tickets can only be merged with other Slack items from the same Slack channel, not with Messenger, email, or other channel types.
Merging Phone calls into customer tickets is only supported when the ticket originated from a phone call, email, or Messenger conversation.
Discord conversations and tickets can only be merged with other Discord items from the same Discord channel.
How to report on merged conversations and tickets
Conversation and tickets that have been merged will be included in all report metrics by default. You can track merged conversations by applying a filter using the custom attribute “Merged is true”. This will display all conversations that have been merged, or you can exclude merged conversations from your report by selecting "Merged is false".
FAQs
Will Fin still reply after a conversation is merged?
Will Fin still reply after a conversation is merged?
Fin continues to work on the primary conversation as normal. The secondary conversation is closed when it's merged and customers can't send new messages to it, so Fin won't carry on there. If a customer replies again, their reply is added to the primary conversation, where Fin (along with any workflows or Custom Answers) can continue to respond.
Can I merge conversations from different users?
Can I merge conversations from different users?
Yes, you can merge conversations from different users, but there are some constraints.
How does merging affect SLAs?
How does merging affect SLAs?
If the secondary has an active SLA, this will be removed and the SLA of the primary conversation will be used instead.
Will a secondary user see the full conversation history?
Will a secondary user see the full conversation history?
If conversation history is turned on, new participants may see the full thread of the primary conversation. However, teammates can always remove participants if necessary.
Can I merge Customer tickets across users?
Can I merge Customer tickets across users?
Yes, you can merge Customer tickets from different users, and the secondary user will be added as a participant in the primary ticket.
Can I merge Back-office or Tracker tickets?
Can I merge Back-office or Tracker tickets?
No, you can only merge Customer tickets or conversations.
What happens when I merge two tickets with different statuses?
What happens when I merge two tickets with different statuses?
When tickets with different statuses are merged, the secondary ticket assumes the status of the primary ticket. If the primary ticket's status is a resolved state, the secondary ticket will be set to the first resolved state defined in that ticket type — determined by its position in the ticket type's state configuration (i.e., the topmost resolved state). If you need a distinct resolved state for merged duplicates (e.g., "Merged as duplicate"), add it as the first resolved state in your ticket type settings.
Which resolved state is applied to the secondary ticket when merging?
Which resolved state is applied to the secondary ticket when merging?
When a secondary ticket is set to a resolved status during a merge, it's assigned the first resolved state defined in the ticket type — the topmost resolved state in the ticket type's state configuration.
For example, if your ticket type has two resolved states — "Resolved" and "Closed" — and "Resolved" is listed first, the secondary ticket will always be set to "Resolved" on merge.
Tip: If you want merged duplicates to land in a specific resolved state (e.g., "Merged as duplicate"), create that state and place it above your other resolved states in Settings > Inbox > Tickets.
Can a conversation be merged more than once?
Can a conversation be merged more than once?
A conversation can only be merged into another conversation once. After a conversation has been merged, it can't be merged again: it can't be merged into a different conversation, and other conversations can't be merged into it. To merge several conversations into one primary conversation in a single step, use bulk merge.
How many conversations can I merge at once?
How many conversations can I merge at once?
You can merge up to 100 conversations at once with bulk merge, including the conversation you start from. Bulk merge is available in the web Inbox and needs the Can merge conversations permission.
Can I reply to a secondary conversation?
Can I reply to a secondary conversation?
No, once a conversation has been merged you cannot send any new messages in the secondary conversation.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts















