Skip to content
Hypamoon

For teams that run on Zendesk

Zendesk duplicate tickets: merged by your rules

A customer who does not hear back in an hour often writes again, through another channel. Each message becomes its own ticket in Zendesk, two agents may answer, and a view that shows the duplicates is not possible.

How it goes today

  1. Spot the duplicates while working the queue.
  2. Search the customer for other open tickets.
  3. Merge them by hand, one at a time.
  4. Apologize when two agents answered.

How it can go

One question, one ticket, one agent.

When a new ticket comes in, open tickets from the same customer in the last days are compared on subject and content. Clear duplicates are merged into the oldest ticket by the rules you set, and the customer gets one thread. Doubtful cases get an internal note with a link instead, and you get a weekly list of what was merged.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Zendesk key in the portal, never in the chat.

Your request

With Hypamoon, when a new Zendesk ticket arrives, check for open tickets from the same customer in the last three days about the same question. Merge clear duplicates into the oldest one by the rules I give you, and add a note with a link where you are not sure. Send me a weekly list of merges.

An administrator creates an OAuth client in Zendesk Admin Center, under Apps and integrations, APIs, OAuth clients, and limits what it may read and change. It stays yours.

More for teams on Zendesk