> ## Documentation Index
> Fetch the complete documentation index at: https://chatbase.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Merge duplicate tickets in the Helpdesk

> Combine duplicate tickets from the same customer so your team works on one.

Merging in the Chatbase Helpdesk combines a customer's duplicate tickets into the one ticket you keep, so your team answers the customer once. It's for cases like a customer who emails twice about the same order, or who opens a chat after already sending an email. Each merged ticket closes and links to the kept ticket, and you can still read its messages there. Both timelines record the merge. A merge cannot be undone, and the dialog warns "This can't be undone."

To keep a customer's new emails and chats on their open ticket from the start, turn on [reusing open tickets](https://chatbase.co/docs/user-guides/chatbot/help-desk/ticket-reuse.md).

***

## Merging a ticket

**1. Open the merge picker**

In the right-hand panel, click the merge icon in the **Customer History** header.

**2. Pick the other ticket**

The list shows the customer's 20 most recently active tickets. Search by ticket number or message text to find others.

**3. Choose which ticket to keep**

By default, the ticket you have open is merged into the one you pick. Click **Swap** to keep the open ticket instead.

**4. Click Merge**

You can only merge from the ticket view. There is no merge in the inbox's bulk selection bar, and the API has no merge endpoint.

![Ticket details panel with the merge icon in the Customer History header and its tooltip showing](https://mintcdn.com/chatbase/ye_joD2l7PTslSvm/user-guides/images/help-desk/merging/merge-icon.png?fit=max\&auto=format\&n=ye_joD2l7PTslSvm\&q=85\&s=cdede1562005ad186c26de42f2990961)

***

## Merging more than one ticket

Turn on **Select multiple** in the merge picker to merge up to 10 tickets into the one you have open. If one of them can't be merged, the rest still merge.

![Merge picker with Select multiple turned on and three of the customer's tickets ticked to merge into the open ticket](https://mintcdn.com/chatbase/l7bz8YqDdhVlUgi7/user-guides/images/help-desk/merging/select-multiple.png?fit=max\&auto=format\&n=l7bz8YqDdhVlUgi7\&q=85\&s=bb448d37431eb8504fdfad13bc7a56ee)

***

## Reading a merged ticket's messages

On the ticket you kept, **Show messages** on a merge opens the merged ticket's replies and notes below it. A merged ticket with merges of its own opens those the same way.

![Ticket timeline with a merge entry expanded, showing the merged ticket's earlier customer messages below it](https://mintcdn.com/chatbase/l7bz8YqDdhVlUgi7/user-guides/images/help-desk/merging/merged-messages.png?fit=max\&auto=format\&n=l7bz8YqDdhVlUgi7\&q=85\&s=ecef9be9ba30a74fb4a65611bc7a45cb)

[AI Draft Replies](https://chatbase.co/docs/user-guides/chatbot/help-desk/ai-draft-replies.md) on the ticket you kept also read the merged tickets' replies.

***

## Which tickets can be merged

Both tickets must belong to the same customer, and the ticket you keep must be open. A ticket that was already merged cannot be merged again, and nothing can be merged into it.

| Channel | Same customer means |
| - | - |
| Email, Chat Bubble, API, and tickets agents create in the Helpdesk | Same email address. Tickets from these channels can be merged with each other. |
| WhatsApp, Messenger, Instagram | Same contact on the same channel |

On WhatsApp, Messenger, and Instagram, keep the ticket for the customer's current conversation and merge older tickets into it. If you try to merge that ticket away, the picker shows "The customer's current conversation has to stay open. Try Swap."

> [!NOTE]
>
> Chat Bubble visitors type their own email address, so two tickets with the same unverified address may come from different people. When an address isn't verified, the merge dialog warns that "these tickets may not be from the same person. Only merge if you're sure." Check both tickets before merging.

***

## What happens to the merged ticket

It moves to your default closed status, or keeps its status if it was already closed. After that it can only move between closed statuses, and bulk reopening skips it.

Agents can add notes to it but cannot reply.

When the customer replies to the merged ticket's email thread, the reply goes to the ticket you kept, with a note showing which ticket it was sent to. If that ticket is later merged too, replies go to the newest ticket.

![A customer email reply on the kept ticket, labelled as sent to merged ticket #237](https://mintcdn.com/chatbase/ye_joD2l7PTslSvm/user-guides/images/help-desk/merging/rerouted-reply.png?fit=max\&auto=format\&n=ye_joD2l7PTslSvm\&q=85\&s=8ab6362cc403c3852901b158251cf0f5)

The merged ticket no longer appears in the customer's ticket list in the Chat Bubble.

Merging does not run triggers or send a [satisfaction survey](https://chatbase.co/docs/user-guides/chatbot/help-desk/satisfaction-surveys.md), and triggers do not run on a merged ticket afterwards. The kept ticket gets its survey as usual when it closes.

The customer isn't notified. Merging sends no email or message; it only adds the merge entries to both timelines. If the merged ticket has a [Slack ticket thread](https://chatbase.co/docs/user-guides/chatbot/help-desk/slack-ticket-threads.md), the AI close summary is posted there.

In [Helpdesk Analytics](https://chatbase.co/docs/user-guides/chatbot/analytics.md#helpdesk), merging an open ticket counts as a normal close, so it adds to the solved count.

### Fields stay on the merged ticket

The kept ticket doesn't inherit anything from the merged ticket. Tags, custom fields, priority and CC participants stay where they were. Copy anything you need onto the kept ticket before or after merging. The kept ticket's timeline links to the merged ticket's history.

### Live chat and takeover

If the merged ticket was open, its conversation goes back to the AI agent once no other open ticket remains on it, so the AI agent answers the customer's next message there. Exceptions:

* Email conversations never go back to the AI agent, so the customer's email replies keep reaching your team.
* API, Phone and mobile SDK conversations never go back to the AI agent after a ticket.

The kept ticket stays with your team.

In the [API](https://chatbase.co/docs/api-reference/v2/helpdesk.md), replying to a merged ticket or moving it to an open status returns a `TICKET_MERGED` error.

Merging requires the **Edit tickets** permission.

***

## Frequently asked questions

> [accordion] Is the customer told when I merge their tickets in the Helpdesk?
>
> No. Merging sends nothing to the customer. If they reply to the merged ticket's email thread, the reply lands on the ticket you kept.

> [accordion] Does the kept ticket get the merged ticket's tags and custom fields?
>
> No. Tags, custom fields, priority and CCs stay on the merged ticket. Add them to the kept ticket yourself if you need them.

> [accordion] Can I undo a merge?
>
> No. A merge is permanent. Check both tickets first, especially when the email address isn't verified.

> [accordion] Can I merge tickets in bulk or through the API?
>
> Not from the bulk selection bar or the API. From an open ticket, turn on **Select multiple** in the merge picker to merge up to 10 of the customer's tickets into it.

> [accordion] Can I merge tickets from two different customers?
>
> No. Both tickets must belong to the same customer: the same email address for Email, Chat Bubble, API and agent-created tickets, or the same contact on one messaging channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.