Merge duplicate tickets when the same customer opens more than one ticket about the same issue and your team needs one clean conversation to work from.

Merging keeps the support history together, reduces duplicate replies, and helps the next teammate understand the full context before responding.

When to merge tickets

Merge tickets when multiple threads are really part of the same support request, for example:

• A customer sends a follow-up as a new email instead of replying to the original thread
• The same customer opens the same issue twice from different channels
• Two tickets describe the same bug, order, invoice, or account question
• A teammate needs one timeline before replying or escalating

Do not merge unrelated tickets just because they come from the same customer. If the customer is asking about different problems, keep the tickets separate so status, ownership, and follow-up stay clear.

What happens when tickets are merged

When tickets are merged, initdesk keeps the conversation history together in the resulting ticket. Your team can review the combined timeline and continue from one place instead of switching between duplicate threads.

Merging is an internal organization action. Customers do not need to know that duplicate tickets were combined unless you choose to mention it in your reply.

How to merge tickets

1. Open the ticket you want to keep as the main conversation.
2. Use the ticket actions menu and choose the merge option.
3. Search for the duplicate ticket from the same customer.
4. Review the ticket you are merging before confirming.
5. Confirm the merge.

After the merge, continue the customer conversation from the resulting ticket.

Best practices

Keep the clearest ticket as the main one

When possible, keep the ticket with the best subject, most complete context, or current owner as the main conversation.

Check the timeline before replying

Review the merged history before sending a response. The customer may have added details in the duplicate ticket that change the right answer.

Use tags after merging

If the merged ticket represents a bug, billing question, cancellation, or urgent request, add the right tags so it stays visible in filters and reporting.

Avoid merging separate issues

One customer can have multiple active problems. Keep tickets separate when each issue needs its own owner, status, or resolution.

Troubleshooting

I cannot find the ticket I want to merge

Confirm that the ticket belongs to the same customer and that you have access to the inbox where it lives.

I merged the wrong tickets

Review the merged conversation and add an internal note for your team. If the tickets should remain separate, contact support with the ticket references so we can help evaluate the best recovery path.

The merged ticket still needs follow-up

Set the right assignee, status, and tags after merging so the ticket appears in the correct queue or saved filter.