Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsMerge support records only after confirming they describe the same underlying issue—not simply because they belong to the same customer. Choose the record that should remain primary, review what the platform will carry over, and confirm the consequences before proceeding. Zendesk and Intercom handle comments, fields, participants, and recovery differently; in both, a merge can have lasting effects.
Decide whether the records are true duplicates
Two records from the same person may concern separate questions, orders, incidents, or stages of a problem. Compare the issue itself: what happened, when it began, which product or transaction is involved, and what response or resolution is already underway. Similarity suggestions can surface candidates, but they do not establish that two records are duplicates.
As an Amazon Associate I earn from qualifying purchases.
- Merge when: the records concern the same issue and keeping both active would split replies, work, or reporting.
- Keep separate when: the customer has raised a different issue, even if the requester, channel, or wording is similar.
- Pause for review when: merging could disclose one customer’s conversation history to another, or when ownership, privacy, or the correct primary record is unclear.
Before acting, identify which record has the clearest useful history, appropriate owner, and status for continuing work. Do not assume the other record’s entire timeline or fields will be copied into it.
How Zendesk and Intercom merges differ
| Platform | Eligible records and status | Identity and participants | What happens to history and fields | Source record and recovery |
|---|---|---|---|---|
| Zendesk Support | One or more tickets can be merged into another. Tickets must be below Solved; an unsolved source can be merged into a Solved destination, which is not reopened. With custom statuses, the status must be in a category below Solved. | With ticket CCs enabled, different requesters are allowed; the source requester and existing CCs are added as destination CCs. Without CCs, the requesters must match. | The most recent public comment from the source appears in the merge window and can be edited or removed. Earlier comments remain on the source. Source fields such as tags, type, priority, and status are not carried over. | Source ticket closes and receives the closed_by_merge tag. Zendesk says merges are permanent and cannot be undone. |
| Intercom | Conversations and Customer tickets are supported; Back-office and Tracker tickets are not. Channel and item-type combinations have restrictions. | Multiple-participant items cannot be merged. Cross-user merging is disabled by default; when enabled, the secondary user becomes a participant on the primary. | Secondary message history is not appended to the primary thread. The secondary retains its own ID and reporting/API details and links to the primary with a summary note. | Secondary closes and becomes read-only; only the primary receives new messages. Standard UI cannot reverse the merge; Intercom says to contact support to unmerge. |
| Salesforce Service Cloud | Salesforce Help search result says representatives can merge up to three cases into a master case. | Not stated in the cited Salesforce search result. | Not stated in the cited Salesforce search result. | Non-master cases are deleted if “Delete duplicate cases after merge” is enabled. Full current procedure and remaining effects are not established by the cited search result. |
Platform behavior and eligibility can change. The Zendesk and Intercom links below describe their documented workflows; use Salesforce’s current full guide before merging cases there.
#1 Best Overall
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Merge tickets in Zendesk Support
Check eligibility and choose the destination
Zendesk allows agents to merge one or more tickets into another ticket. Both source and destination must be below Solved, though an unsolved ticket can be merged into a Solved destination; that destination stays Solved. For custom statuses, the status must be in a category below Solved. On Enterprise, agents with custom roles need the merge permission.
Zendesk warns when tickets have different organizations, brands, or requesters. Requester rules depend on whether ticket CCs are enabled: with CCs enabled, tickets with different requesters can be merged, and the source requester is added as a CC to the destination along with existing CCs. Without CCs, the requesters must be the same. Review those participants before continuing.
Review the merge content and confirm
- Open the ticket that should remain as the destination, then use the ticket merge action to select the source ticket or tickets. Zendesk’s related-ticket panel can also present merge suggestions and similar tickets.
- Check the destination and source identities, organizations, brands, and requester/CC details. Confirm they represent the same issue.
- Inspect the merge window’s comment. It displays the source ticket’s most recent public comment; edit or remove it if needed. If retained, it is included in the destination comment with a link to the closed source ticket.
- Confirm the merge only after reviewing the outcome. The source ticket closes, and the destination is not reopened just because an unsolved source was merged into a Solved destination.
Earlier source comments remain reviewable on the closed ticket rather than appearing directly on the destination. Source fields—including tags, type, priority, and status—are not copied over; only fields filled in on the destination are saved. The closed source receives the closed_by_merge tag. Zendesk notes this tag can help exclude merged tickets from reports, but reports cannot be based on the closed ticket’s fields.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Zendesk states, “Merges are permanent and can’t be undone.” Read its current ticket-merging instructions before using the workflow.
Merge conversations or Customer tickets in Intercom
Confirm the item and channel combination
Intercom supports merging conversations and Customer tickets, but not Back-office or Tracker tickets. Items with multiple participants cannot be merged. The permitted channel combinations are specific: WhatsApp, Facebook, and Instagram items must be from the same user on the same channel; Slack items must be from the same Slack channel. Intercom documents additional phone, Messenger, email, and Customer-ticket combinations, including that phone-to-email is supported while email-to-phone is not. Check its capability table for the exact item types involved rather than assuming all cross-channel pairs work.
Use the merge preview
- Open the conversation or ticket that should remain primary.
- Use the keyboard shortcut ⌘ / Ctrl K or open the three-dot menu and select Merge into.
- Search for and select the secondary conversation or ticket. Review the interface preview to verify that the intended records are being combined.
- Check the status outcome and participant implications before confirming. If the tickets have different statuses, the secondary assumes the primary’s status. If the primary is in a resolved state, the secondary is assigned the first resolved state in that ticket type’s configured order.
The secondary closes and becomes read-only. Its message history is not appended to the primary thread; it remains separately accessible with its own ID and reporting/API details, and a summary note links it to the primary. New messages go to the primary. Intercom says the ordinary workflow cannot reverse a merge; unmerging requires contacting Intercom support. See Intercom’s merge guide for its channel-combination table.
Take extra care with cross-user merges
Cross-user merging is disabled by default. If enabled, the secondary user is added as a participant to the primary item. Intercom cautions that participants may see the full primary conversation history when history is turned on. Treat this as a privacy and customer-communication decision, not a routine duplicate cleanup. Do not merge across users unless the identity and disclosure consequences are understood.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Salesforce cases and duplicate customer accounts are separate workflows
Salesforce Service Cloud
Salesforce Help’s search result says support representatives can merge up to three cases into a master case. It also says non-master cases are deleted when the “Delete duplicate cases after merge” setting is enabled. Because the cited result does not establish the full current procedure or all effects on case history and fields, do not treat the Zendesk or Intercom steps above as Salesforce instructions. Consult the current Salesforce guide to merging duplicate cases in Lightning Experience before acting.
Zendesk duplicate user accounts
Merging duplicate user profiles is not the same as merging their tickets. Zendesk documents a separate user-account merge process. In that process, the source profile loses its tags, notes, and user fields, and the account merge cannot be undone. First decide whether the identity records truly belong to the same person; ticket consolidation alone does not require an account merge. See Zendesk’s duplicate-account instructions.
Rank #4
- Get push notifications when tickets are assigned to you or when you get responses to a ticket. Take your support desk everywhere you go.
- Respond to your tickets, assign it to agents, change its priority, mark it as spam or send them to trash. Stay on top of tickets that matter the most with 9+ default Views and unlimited custom Views.
- Create new tickets, choose scenarios to execute and log times spent on a ticket on the fly.
- Insert canned responses when needed and attach files as necessary directly from your device or from Dropbox when you reply to your tickets
- Quickly search your list of customers or the right solution in your knowledge base for a question or for that one ticket that you know has popped up earlier somewhere.
What to check before clicking Merge
- Same issue: compare the substance and context, not just the customer name or similar wording.
- Primary record: choose the record that should receive future work and replies; verify its owner and status.
- Eligibility: confirm status, channel, item type, requester, and participant restrictions for the platform.
- History and fields: identify what will remain only on the source and what, if anything, is copied or summarized.
- Privacy: check whether participants or requesters will be added and what history they may see.
- Irreversibility: treat the confirmation as final unless the platform explicitly provides a recovery path.
Reduce duplicate conversations at the source
Merging is cleanup, not a substitute for sound intake and identity handling. Zendesk notes that multiple messaging conversations do not merge with prior conversations and that delaying end-user authentication may result in duplicate tickets. Review and test authentication timing in the messaging setup so returning end users are identified appropriately; do not assume later ticket merges will reunite every conversation.
Automated duplicate-ticket research also illustrates why matching needs context: an arXiv paper describes iPACK, which combines customer-side ticket information with cloud-side incident information to aggregate duplicate cloud-support tickets. Its record does not provide a performance figure, so it does not establish a measurable accuracy or reduction claim. See the iPACK paper record.
Recommended Free Tools
Frequently Asked Questions
Can I merge two tickets from different channels?
It depends on the platform and exact item types. Intercom allows some cross-channel combinations but restricts others; for example, WhatsApp, Facebook, and Instagram items must match by user and channel, and phone-to-email is supported while email-to-phone is not. Check Intercom’s current compatibility table. Zendesk’s cited ticket-merging guide does not establish a general cross-channel rule.
Do comments and messages move into the surviving ticket?
Not in full on the documented workflows. Zendesk places only the source’s latest public comment in the merge window; earlier comments stay on the closed ticket. Intercom does not append the secondary conversation’s message history to the primary thread, though the secondary remains accessible and linked by a summary note.
Can I undo a merge?
Zendesk says ticket merges cannot be undone. Intercom says unmerging requires contacting its support team rather than using the standard workflow. Salesforce’s cited search result does not establish a recovery method.
Should I merge duplicate customer accounts as well as tickets?
Only if the profiles themselves are confirmed duplicates. Zendesk treats account merging as a separate action; its source profile loses tags, notes, and user fields, and that account merge cannot be undone.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
