Macha
Helpdesk Concepts

Ticket Merge

Definition

Ticket merge is the action of combining two or more support tickets about the same issue into a single ticket, consolidating their conversations so the request is handled in one place.

Also known as: merge ticketsticket consolidationcombine tickets

How it works

When a customer emails twice, or the same problem arrives across two channels, an agent merges the duplicate into a primary ticket. The help desk copies or links the messages so the full history lives together, then usually closes the merged-away ticket with a note pointing to the survivor.

Merging is distinct from linking: a merge collapses duplicates of the same issue into one, while linking associates separate-but-related tickets that should stay individual.

Why it matters

Duplicate tickets waste agent time and risk two people answering the same customer differently. Merging keeps the conversation and its context in a single thread, produces cleaner volume and resolution metrics, and spares the customer from getting fragmented replies to what is really one request.

Frequently asked

What is the difference between merging and linking tickets?

Merging combines duplicate tickets about the same issue into one ticket; linking keeps tickets separate but records that they're related. Merge for duplicates, link for connected-but-distinct issues.

What happens to a ticket after it's merged?

The merged-away ticket is typically closed with a note referencing the primary ticket, while its messages are moved or linked into the surviving ticket so no history is lost.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial