Ticket Merging is the administrative action of combining two or more separate support inquiries into a single conversational thread. This is typically done when a customer submits multiple tickets about the same issue across different channels, or when multiple users at the same company report the same underlying bug or outage.
?
Why is Merging essential for Support hygiene?
It prevents "Duplicate Work." Without merging, three different agents might spend time troubleshooting the same issue for the same customer. It also ensures the customer gets a single, unified resolution rather than confusing fragments from different agents.
?
How is Merging used during Major Outages?
During an outage, a helpdesk might receive 500 identical tickets. "Bulk Merging" allows a team to move all these into a single "Incident Ticket." Resolving the master incident then automatically notifies and resolves all 500 individual tickets simultaneously.
?
What is the "Golden Rule" of Ticket Merging?
Always merge the *newest* ticket into the *oldest* one (or the master incident). This preserves the original "Ticket ID" and ensures that the SLA timer reflects the customer's true wait time from their first interaction.
?
Should you notify the customer after a merge?
Yes. Most helpdesks send an automated note: "We've noticed you have several open requests on this topic and have combined them here to better assist you." This maintains transparency and prevents customer confusion.
Knowledge Challenge
Mastered Ticket Merge? Now try to guess the related 5-letter word!
Type or use keyboard