<?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: Linking Non-team emails to Ticketing pipelines in Tickets &amp; Conversations</title>
    <link>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/918097#M6432</link>
    <description>Thank you so much! This was helpful.&lt;BR /&gt;</description>
    <pubDate>Tue, 06 Feb 2024 18:59:11 GMT</pubDate>
    <dc:creator>CNolan21</dc:creator>
    <dc:date>2024-02-06T18:59:11Z</dc:date>
    <item>
      <title>Linking Non-team emails to Ticketing pipelines</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/914910#M6402</link>
      <description>&lt;P&gt;My client wants me to create a Hubspot ticket pipeline, and link 2 of his employees' inboxes to it.&lt;/P&gt;&lt;P&gt;This means every email that these employees receive would auto generate a ticket, and be tracked in a pipeline, with the intention of having everything in one place.&lt;/P&gt;&lt;P&gt;This would include Sales emails, customer success, and everything in between (e.g. promotions, etc.). Reminder, this is their individual work emails. Not personal emails (which I know is recommended against).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before I say yes to this, I would like to understand if this is a good idea. I recognize that this could present an issue ethically(I wouldn't love having every work email in plain sight of my boss, and potentially others) - but was more wondering if it would present any logistical / operational risks / challenges.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 17:36:09 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/914910#M6402</guid>
      <dc:creator>CNolan21</dc:creator>
      <dc:date>2024-01-31T17:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Linking Non-team emails to Ticketing pipelines</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/915223#M6403</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/702365"&gt;@CNolan21&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Without having the organizational context, it's hard to say whether it's a good idea or a bad one. If these contacts receive personal emails in their inboxes, I'd lead towards the latter. In that case, it would be better to set up an another email address for them (e.g. &lt;A href="mailto:john@acme.com" target="_blank"&gt;john@acme.com&lt;/A&gt; instead of &lt;A href="mailto:john.doe@acme.com" target="_blank"&gt;john.doe@acme.com&lt;/A&gt;) and connect that inbox to HubSpot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once you have a separate inbox like this, the employees would have to make sure that their non-ticket related emails stay under the old email address and they use the new one for anything tickets.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can then connect this email address as a team channel by following these steps: &lt;A href="https://knowledge.hubspot.com/inbox/connect-channels-to-the-conversations-inbox#connect-and-customize-a-team-email-channel" target="_blank"&gt;https://knowledge.hubspot.com/inbox/connect-channels-to-the-conversations-inbox#connect-and-customize-a-team-email-channel&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ticket creation can be enabled by following these steps: &lt;A href="https://knowledge.hubspot.com/records/create-tickets#create-tickets-in-your-conversations-inbox" target="_blank"&gt;https://knowledge.hubspot.com/records/create-tickets#create-tickets-in-your-conversations-inbox&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This of course also works with their current email address, as long as it's not yet connected as a personal connected email. In that case however it might make sense to run this by the client's HR or legal department, to be on the safe side.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 05:56:53 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/915223#M6403</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2024-02-01T05:56:53Z</dc:date>
    </item>
    <item>
      <title>Re: Linking Non-team emails to Ticketing pipelines</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/918097#M6432</link>
      <description>Thank you so much! This was helpful.&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Feb 2024 18:59:11 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/918097#M6432</guid>
      <dc:creator>CNolan21</dc:creator>
      <dc:date>2024-02-06T18:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Linking Non-team emails to Ticketing pipelines</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/918098#M6433</link>
      <description>&lt;P&gt;Thank you so much! This was helpful&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 18:59:30 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Linking-Non-team-emails-to-Ticketing-pipelines/m-p/918098#M6433</guid>
      <dc:creator>CNolan21</dc:creator>
      <dc:date>2024-02-06T18:59:30Z</dc:date>
    </item>
  </channel>
</rss>

