A customer sends an email, submits the form and calls the account manager about the same missing file. Each route creates work. Three colleagues start chasing, while the customer still waits for a useful answer.
Merge duplicate customer requests only after confirming that they concern the same underlying case and that combining their information is appropriate. Keep one owning record, preserve the references and decide which communications and actions survive. Similar wording alone is not enough.
Check that the cases are really duplicates
Compare the requester, client, affected deliverable, reported event and desired outcome. Two people may describe the same incident but have different permissions or individual actions. Several clients reporting one outage should not automatically have their private conversations merged together.
Platform behaviour matters. Zendesk states that its ticket merges are permanent and cannot be undone. That is a product-specific warning, not a statement about all systems. Check recipient, field, attachment and reporting behaviour in your actual tool before performing a merge.
Use a consolidation checklist
Confirm the common issue and record why consolidation is appropriate.
Select the surviving case and its accountable owner.
Check recipients, visibility and permission boundaries before copying material.
Preserve meaningful messages, attachments, promises and investigation results.
List open actions and cancel or transfer duplicate effort explicitly.
Keep old references linked to the surviving record.
Tell the client which reference to use and what happens next.
Check how closure and merge actions affect the reporting record.
Use the authoritative-record principle at case level. A surviving record is useful only if colleagues can identify it and see the next action.
An illustrative three-channel request
A client reports that an approved report download is unavailable. The email includes the error message, the form records the needed-by time and the account manager has promised a callback. The team confirms these relate to one event.
The case owner retains all three pieces of useful context. One technical investigation remains active, the callback promise stays visible and the client receives a single reference. The owner also confirms that no colleague is still preparing a separate response against an obsolete record.
Link rather than merge when the boundary is unclear
If two cases share a possible cause but need separate decisions or confidentiality, link them to a common investigation while keeping their communications distinct. Record the connection as a hypothesis if the shared cause is not yet confirmed.
Review how duplicates entered the workflow. Better references, form acknowledgements and shared-inbox triage ownership may reduce parallel handling. The goal is one coordinated response, not simply a lower ticket count.
If the same client issue creates work in several places, Hili Consulting can help define the case record, routing and consolidation checks your team needs.
