<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Ticket Management in Data Hub</title>
    <link>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1157211#M3078</link>
    <description>&lt;P&gt;We're currently having issues with tickets being created from multiple sources — forms, calls, and emails — all generating separate tickets for the same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’d like to explore how we can better manage this, ideally by finding a way to merge duplicate tickets. Whether it's through a workflow, automation, or an easy manual trigger that the sales team can use, we’re open to suggestions.&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Mon, 26 May 2025 22:58:34 GMT</pubDate>
    <dc:creator>Psc2147</dc:creator>
    <dc:date>2025-05-26T22:58:34Z</dc:date>
    <item>
      <title>Ticket Management</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1157211#M3078</link>
      <description>&lt;P&gt;We're currently having issues with tickets being created from multiple sources — forms, calls, and emails — all generating separate tickets for the same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’d like to explore how we can better manage this, ideally by finding a way to merge duplicate tickets. Whether it's through a workflow, automation, or an easy manual trigger that the sales team can use, we’re open to suggestions.&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 22:58:34 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1157211#M3078</guid>
      <dc:creator>Psc2147</dc:creator>
      <dc:date>2025-05-26T22:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: Ticket Management</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1157255#M3079</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/936561"&gt;@Psc2147&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like you have contacts who submit their requests via different channels repeatedly – do I understand that correctly?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Without having more context, I would say that the biggest challenge here is to automatically determine with certainty that a ticket is an actual duplicate. For example, an incoming email would have a different email text than, maybe, a submitted form. So there wouldn't be anything to go by to automatically duplicate, since these two records do not share something that is exactly the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could of course assume that two open tickets of the same category on a contact are duplicates and merge them – with the risk that these might actually be separate issues. If this risk is acceptable, one way to go about this would be Koalify which lets you set custom deduplication rules: &lt;A href="https://koalify.io/" target="_blank"&gt;https://koalify.io/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lastly, I think there's a component of human merging here as well. When a customer support/service rep works a ticket, you could train them to check for other open tickets – and merge, if necessary: &lt;A href="https://knowledge.hubspot.com/records/merge-records" target="_blank"&gt;https://knowledge.hubspot.com/records/merge-records&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Tue, 27 May 2025 03:54:57 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1157255#M3079</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2025-05-27T03:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: Ticket Management</title>
      <link>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1189944#M3168</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/936561"&gt;@Psc2147&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You’re on the right track already.&lt;BR /&gt;&lt;BR /&gt;A couple of extra thoughts that might help you move forward:&lt;/P&gt;
&lt;P&gt;When multiple channels are feeding into Service Hub, duplicates are almost always about context.&lt;BR /&gt;HubSpot doesn’t have an automatic dedupe for tickets the same way it does for contacts, so out of the box you’re left with either training reps to check related tickets &lt;A title="Merge records" href="https://knowledge.hubspot.com/records/merge-records" target="_blank" rel="noopener"&gt;(https://knowledge.hubspot.com/records/merge-records)&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Or introducing a third-party tool like Koalify that lets you define stricter duplicate rules.&lt;/P&gt;
&lt;P&gt;What I’ve seen is that the “duplicate” problem often starts upstream. If your form submissions, emails, and call notes are siloed in other systems, each one can push a new ticket into HubSpot without awareness of the others.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That’s why workflows or manual merges only solve the surface issue. If you want tickets and contacts to really stay consistent, the safer long-term play is to keep your systems in real-time sync so HubSpot always receives and updates the same record rather than creating fresh ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That way, when a customer calls after sending a form, your team sees one unified ticket thread instead of three scattered versions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if this makes sense for your setup.&lt;/P&gt;
&lt;P&gt;Curious to hear if you’re mainly looking for a quick fix (like a merge step in reps’ process) or if you’d consider cleaning it up at the integration level so duplicates don’t keep appearing. Hope this helps.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Aug 2025 15:27:01 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Data-Hub/Ticket-Management/m-p/1189944#M3168</guid>
      <dc:creator>RubenBurdin</dc:creator>
      <dc:date>2025-08-18T15:27:01Z</dc:date>
    </item>
  </channel>
</rss>

