<?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 Re: Internal &amp;quot;CC&amp;quot; to team inbox not triggering new ticket on existing threads in Tickets &amp; Conversations</title>
    <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271258#M9438</link>
    <description>&lt;P&gt;Welcome to the Community&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/1056686"&gt;@chrismackey&lt;/a&gt;! An interesting use case. Thismay seem like a too-simple question, but I'm wondering if you've tried forwarding (and still cc-ing all involved) rather than replying? This may be a procedure fix rather than a technology fix. I ask because in my understanding and experience,&amp;nbsp;HubSpot’s default behavior is to keep a reply inside the existing conversation/ticket thread, even if you CC another connected inbox, so CC’ing billing@ will not “break” the thread and create a second ticket by itself. There isn’t a setting that makes a CC’d team inbox automatically spawn a new ticket from an existing reply; the built-in logic is tied to the original conversation thread and ticket association.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The cleanest approach is usually to forward, not reply, to a billing intake address that is connected as its own channel and configured to create tickets in the Billing Pipeline. Since billing@ is already a connected inbox, forwarding the message into that inbox is more likely to generate a separate conversation/ticket than CC’ing it on the support thread.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another option is to use a workflow or automation that copies ticket data into a new Billing ticket when a specific property or email pattern is detected, since HubSpot workflows can create tickets automatically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hopefully that helps!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Apr 2026 12:28:11 GMT</pubDate>
    <dc:creator>danmoyle</dc:creator>
    <dc:date>2026-04-28T12:28:11Z</dc:date>
    <item>
      <title>Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271071#M9434</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m looking for a way to automate a handoff between our Support and Billing teams. Currently, we are seeing a conflict with HubSpot’s email threading logic.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Situation:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;A customer is working with our team on an active Support Pipeline ticket.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;During the conversation, the customer asks a billing question or sends a PO.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Our internal team member replies to that email thread and CCs our billing@ inbox to loop in that department.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;The Issue:&lt;/STRONG&gt; Because the email is a reply to an existing thread already associated with a Support ticket, HubSpot simply logs the email (and the CC to billing) as an activity on the Support ticket. It does &lt;I&gt;not&lt;/I&gt; trigger the creation of a new ticket in the Billing Pipeline, even though billing@ is a connected team inbox.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Goal:&lt;/STRONG&gt; I want to find a way, either through settings or a specific Workflow, to force a new ticket creation in the Billing Pipeline whenever billing@ is looped into an existing thread by an internal user.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Has anyone successfully built a workflow or found a setting that allows a CC'd team inbox to "break" the thread and start its own ticket?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 18:02:47 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271071#M9434</guid>
      <dc:creator>chrismackey</dc:creator>
      <dc:date>2026-04-27T18:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271094#M9436</link>
      <description>&lt;P&gt;Hey &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/1056686"&gt;@chrismackey&lt;/a&gt;&lt;/SPAN&gt;,&lt;BR /&gt;&lt;BR /&gt;Thanks so much for posting this use case in the Community!&lt;BR /&gt;&lt;BR /&gt;I was able to find &lt;A href="https://community.hubspot.com/t5/Tickets-Conversations/Send-tickets-to-different-pipelines/m-p/873312/thread-id/5968#M5992" target="_blank"&gt;this Community post&lt;/A&gt;, which seems to outline a similar setup to the one you're describing. It looks like the user ultimately &lt;A href="https://knowledge.hubspot.com/workflows/create-workflows-from-scratch" target="_blank"&gt;created a ticket-based workflow&lt;/A&gt; that updated the "Ticket Pipeline and Status" property value via the "Set Property Value" action.&lt;BR /&gt;&lt;BR /&gt;For additionally context and best practices, I'd like to also tag in some Community experts who might have some suggestions for us! &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;&lt;/SPAN&gt;, and &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/2062"&gt;@Josh&lt;/a&gt; - any thoughts here?&lt;BR /&gt;&lt;BR /&gt;Shane, Senior Community Moderator&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 19:09:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271094#M9436</guid>
      <dc:creator>STierney</dc:creator>
      <dc:date>2026-04-27T19:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271258#M9438</link>
      <description>&lt;P&gt;Welcome to the Community&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/1056686"&gt;@chrismackey&lt;/a&gt;! An interesting use case. Thismay seem like a too-simple question, but I'm wondering if you've tried forwarding (and still cc-ing all involved) rather than replying? This may be a procedure fix rather than a technology fix. I ask because in my understanding and experience,&amp;nbsp;HubSpot’s default behavior is to keep a reply inside the existing conversation/ticket thread, even if you CC another connected inbox, so CC’ing billing@ will not “break” the thread and create a second ticket by itself. There isn’t a setting that makes a CC’d team inbox automatically spawn a new ticket from an existing reply; the built-in logic is tied to the original conversation thread and ticket association.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The cleanest approach is usually to forward, not reply, to a billing intake address that is connected as its own channel and configured to create tickets in the Billing Pipeline. Since billing@ is already a connected inbox, forwarding the message into that inbox is more likely to generate a separate conversation/ticket than CC’ing it on the support thread.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another option is to use a workflow or automation that copies ticket data into a new Billing ticket when a specific property or email pattern is detected, since HubSpot workflows can create tickets automatically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hopefully that helps!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 12:28:11 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271258#M9438</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2026-04-28T12:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271259#M9439</link>
      <description>&lt;P&gt;Thanks as always&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/756167"&gt;@STierney&lt;/a&gt;!&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 12:28:36 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271259#M9439</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2026-04-28T12:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271434#M9442</link>
      <description>&lt;P&gt;Thanks a lot&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;! This sounds like a great, straightforward solution. I'll give that a shot. I appreciate the reply.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 22:17:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271434#M9442</guid>
      <dc:creator>chrismackey</dc:creator>
      <dc:date>2026-04-28T22:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: Internal "CC" to team inbox not triggering new ticket on existing threads</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271972#M9447</link>
      <description>&lt;P&gt;Happy to help,&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/1056686"&gt;@chrismackey&lt;/a&gt;! I'm glad it made sense. And I hope it works for you!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 12:32:41 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Internal-quot-CC-quot-to-team-inbox-not-triggering-new-ticket-on/m-p/1271972#M9447</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2026-04-30T12:32:41Z</dc:date>
    </item>
  </channel>
</rss>

