# Automatically Find Potential Duplicate Tickets **URL:** \ **Category:** HubSpot Ideas\ **Tags:** help-desk\ **Created:** [July 8, 2021, 11:39pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422 "2021-07-08T23:39:28Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![KNault](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/knault/32/63860_2.png) [@KNault](https://community.hubspot.com/u/KNault)\ **Post date:** [July 8, 2021, 11:39pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/1 "2021-07-08T23:39:28Z")
On the ticket object, it would be helpful if there was functionality that automatically identified any potential duplicate tickets. This would avoid multiple people working on the same request. We previously used Sales Force and an app by Internet Creations “Case Merge Premium” Duplicate cases are known to wreak havoc. When there are multiple cases for the same issue, agents waste time trying to find the information they need to help the customer. Not only that, but more than one agent might spend time troubleshooting the same issue. If a customer gets multiple responses from different agents, it creates an inconsistent customer experience and looks unprofessional. It’s frustrating for everyone. It was a game changer for our Service Team. ---
**Author:** ![ariellincoln](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ariellincoln/32/19464_2.png) [@ariellincoln](https://community.hubspot.com/u/ariellincoln)\ **Post date:** [November 29, 2021, 7:41pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/2 "2021-11-29T19:41:38Z")
I think this idea would be super helpful! I run a Support Team, and duplicate tickets are a concern of ours. We do not want multiple reps reaching out to the same company related to the same concerns. Currently, my team uses the ticket board view to skim the company and contact associated, but this is no longer scalable with our ticket volume increasing. However, I found a meh workaround for my team to help find any open duplicate tickets or open tickets from the same company by saving a filtered list ticket view. The list pulls in any tickets in 3 of our support pipelines that are not closed, and the rep can skim the list for associated companies that are the same and then merge them. If anyone has another workaround until Hubspot provides a solution, let me know! ---
**Author:** ![SBoylan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sboylan/32/76463_2.png) [@SBoylan](https://community.hubspot.com/u/SBoylan)\ **Post date:** [April 20, 2022, 8:16am UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/3 "2022-04-20T08:16:07Z")
Hi everyone, we use one workaround that helps us to identify some duplicates. In the case where a form submission generates the ticket, we reply and then the prospect replies to the email, we get a second ticket generated from the reply (because we use a shared general email address for the response, we do need that email box to generate tickets as well, for those cases where the contact was solely via the generic email and no form submission occurred before). What helped us significantly was adding the prospect’s Company name to the subject line. We currently use a snippet to generate the subject line in the email body, then cut & paste into the subject line. This makes identifying the duplicate simple, as the subject line contains “Re: Company Name” right there. Hope it’s useful to anyone in a similar situation! ---
**Author:** ![CBerwick](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@CBerwick](https://community.hubspot.com/u/CBerwick)\ **Post date:** [June 22, 2022, 3:21pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/4 "2022-06-22T15:21:16Z")
Any updates on this issue? We are hoping to move over our order processing tracking into Hubspot but need a way to be alerted if a customer accidentally submits a PO twice. ---
**Author:** ![KDarrah](https://avatars.discourse-cdn.com/v4/letter/k/6a8cbe/32.png) [@KDarrah](https://community.hubspot.com/u/KDarrah)\ **Post date:** [March 8, 2023, 3:58pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/5 "2023-03-08T15:58:31Z")
There is currently a way to manage duplicate contacts in HubSpot and I would love if this feature could be extended to service hub as well for tickets. Our team currently has the same struggle as stated by KNault in the original idea. Zendesk and Jira seem to have add-ons that can assist with managing duplicates, but I haven’t found one that integrates with HubSpot. Integrations can be unreliable, so I would prefer if it was a system function similar to the duplicate manager for contacts. ---
**Author:** ![RBozeman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rbozeman/32/8786_2.png) [@RBozeman](https://community.hubspot.com/u/RBozeman)\ **Post date:** [April 6, 2023, 11:02pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/6 "2023-04-06T23:02:47Z")
Hey @KNault, Yes, this is definitely a huge issue. Expanding the ways to detect and merge duplicate tickets would be helpful, as the ticket name isn’t always a great option, particularly if the ticket was created automatically by default, such as through an inbox message or Facebook Messenger. I wanted to mention that Insycle can help with this. Full disclosure, I work for Insycle. But Insycle can help you to rewrite ticket names for easier deduplication. Then, you can deduplicate tickets in bulk, using any field as a matching field. Then you can automate it to run on a set schedule (daily or weekly for instance) or inject Insycle templates directly into HubSpot Workflows. We recently published an in-depth article on dealing with duplicate HubSpot tickets and the problems companies run into, you can [check it out here](https://blog.insycle.com/fix-duplicate-hubspot-tickets). Best, Ryan ---
**Author:** ![KSoderholm0](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@KSoderholm0](https://community.hubspot.com/u/KSoderholm0)\ **Post date:** [August 30, 2023, 1:17pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/7 "2023-08-30T13:17:31Z")
I totally agree that this is needed. We get sometimes an order twice from a customer. We also get separate tickets from customers using outlook and replying, because the subject has RE: or FW: in the beginning and it is nightmare. ---
**Author:** ![RCharnock2](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@RCharnock2](https://community.hubspot.com/u/RCharnock2)\ **Post date:** [November 10, 2023, 9:11pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/8 "2023-11-10T21:11:36Z")
I completely agree that this is needed. For all of the same reasons. ---
**Author:** ![eddygearup](https://avatars.discourse-cdn.com/v4/letter/e/ed655f/32.png) [@eddygearup](https://community.hubspot.com/u/eddygearup)\ **Post date:** [December 27, 2023, 12:30am UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/9 "2023-12-27T00:30:23Z")
Please implement this. Duplicate tickets are a time-waster and they convolute reporting by skewing toward the vocal minority ---
**Author:** ![ENguyen5](https://avatars.discourse-cdn.com/v4/letter/e/ad7895/32.png) [@ENguyen5](https://community.hubspot.com/u/ENguyen5)\ **Post date:** [August 16, 2024, 7:11am UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/10 "2024-08-16T07:11:17Z")
+1 urgently needed ---
**Author:** ![MereMcV](https://avatars.discourse-cdn.com/v4/letter/m/7c8e57/32.png) [@MereMcV](https://community.hubspot.com/u/MereMcV)\ **Post date:** [October 17, 2024, 1:06pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/11 "2024-10-17T13:06:10Z")
Please!!! This is a DAILY battle and takes so much time when AI could be doing the grunt work! ---
**Author:** ![OdeOliveira](https://avatars.discourse-cdn.com/v4/letter/o/b4bc9f/32.png) [@OdeOliveira](https://community.hubspot.com/u/OdeOliveira)\ **Post date:** [June 5, 2025, 8:08pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/12 "2025-06-05T20:08:29Z")
Sem soluções? ---
**Author:** ![OdeOliveira](https://avatars.discourse-cdn.com/v4/letter/o/b4bc9f/32.png) [@OdeOliveira](https://community.hubspot.com/u/OdeOliveira)\ **Post date:** [June 5, 2025, 8:10pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/13 "2025-06-05T20:10:56Z")
Please implement this. ---
**Author:** ![agirard](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/agirard/32/55643_2.png) [@agirard](https://community.hubspot.com/u/agirard)\ **Post date:** [October 5, 2026, 9:18pm UTC](https://community.hubspot.com/t/automatically-find-potential-duplicate-tickets/40422/15 "2026-10-05T21:18:05Z")
Hi team, Alex on the duplicate management team here. We are well aware that we need to extend our duplicate management checks to fit the entire data model. Our current plan is to up-level our existing toolset within our current scope of support objects, before we extend to begin supporting the full data model. Once we have improved duplicate detection, better bulk handling, and a way to create an automated process around resolving duplicates, we will 100% look to expand to other parts of the data model. Because we are not planning this immediately, I’m marking this idea as not currently planned – but know that it is definitely on our radar and something we want to support in time.