<?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: Archive Ticket in Customer Feedback Tool</title>
    <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/247316#M97</link>
    <description>&lt;P&gt;Hi there Wholesale-Solar,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for this answer. I'm just getting started setting up the ticketing side and it's nice to have this insight ahead of time. I think I'll add in an "archived" stage right out of the gates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jan 2019 18:33:57 GMT</pubDate>
    <dc:creator>JamesCousins</dc:creator>
    <dc:date>2019-01-23T18:33:57Z</dc:date>
    <item>
      <title>Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/197918#M18</link>
      <description>&lt;P&gt;Our agency uses HubSpot Tickets to handle our internal projects between departments, similar to a scrum board or trello. The issue we have is that we don't ever want to delete tickets permanently, however we have to move tickets off our pipeline once they're completed otherwise it causes A TON of clutter.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2018 19:34:09 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/197918#M18</guid>
      <dc:creator>kelseyhalverson</dc:creator>
      <dc:date>2018-07-17T19:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/198220#M21</link>
      <description>&lt;P&gt;&lt;FONT color="#999999"&gt;&lt;STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_hubspot-button-accept-as-solution-gif-v00.gif" style="width: 300px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/10050i6024F3877E1DFF1A/image-size/large?v=v2&amp;amp;px=999" role="button" title="_hubspot-button-accept-as-solution-gif-v00.gif" alt="_hubspot-button-accept-as-solution-gif-v00.gif" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#993300"&gt;&lt;STRONG&gt;Help other HubSpot searchers find this post quickly by accepting the solution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Excellent suggestion &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/65865"&gt;@kelseyhalverson&lt;/a&gt;. You may wish to add to a new or existing thread in &lt;A href="https://community.hubspot.com/t5/custom/page/page-id/ideaslandingpage" target="_blank"&gt;HubSpot Ideas&lt;/A&gt;.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You'll typically get much more traction from the HubSpot Community AND the Ideas Forum is where HubSpot Product Teams monitor suggestions for popularity -- i.e., VOTES! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does that help answer your question? If so, remember to accept this 'solution' so other searchers will find it.&lt;/P&gt;&lt;P&gt;Best,&lt;BR /&gt;Frank&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="hubspot-solutions-signature-mfrankjohnson-v03.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/10258i9C01B01250C2AC00/image-size/large?v=v2&amp;amp;px=999" role="button" title="hubspot-solutions-signature-mfrankjohnson-v03.png" alt="hubspot-solutions-signature-mfrankjohnson-v03.png" /&gt;&lt;/span&gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.mfrankjohnson.com/?utm_source=hs-forum" target="_blank"&gt;www.MFrankJohnson.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 12:22:08 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/198220#M21</guid>
      <dc:creator>MFrankJohnson</dc:creator>
      <dc:date>2018-07-19T12:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/205464#M58</link>
      <description>&lt;P&gt;I agree, there should be some standard archiving methodology to get stuff to drop off of boards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For now...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Add an Archived stage to your pipelines&lt;BR /&gt;2. Setup a tickets workflow&lt;BR /&gt;3. Enrollment Trigger&lt;BR /&gt;Pipeline&amp;nbsp;is any of&amp;nbsp;Tech Support&lt;BR /&gt;and&lt;BR /&gt;Ticket status&amp;nbsp;is any of&amp;nbsp;Done (Tech Support)&lt;BR /&gt;and&lt;BR /&gt;Close date&amp;nbsp;is more than&amp;nbsp;1 day ago&lt;BR /&gt;THEN&lt;BR /&gt;Set a property value&lt;BR /&gt;Set&amp;nbsp;ticket&amp;nbsp;property&amp;nbsp;Ticket status&amp;nbsp;of the associated&amp;nbsp;ticket&amp;nbsp;to "Archived"&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;4. The you can filter your board/tables to exclude Archived&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 15:39:20 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/205464#M58</guid>
      <dc:creator>Wholesale-Solar</dc:creator>
      <dc:date>2018-09-06T15:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/247316#M97</link>
      <description>&lt;P&gt;Hi there Wholesale-Solar,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for this answer. I'm just getting started setting up the ticketing side and it's nice to have this insight ahead of time. I think I'll add in an "archived" stage right out of the gates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 18:33:57 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/247316#M97</guid>
      <dc:creator>JamesCousins</dc:creator>
      <dc:date>2019-01-23T18:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/321890#M229</link>
      <description>&lt;P&gt;We've found it easier to create a workflow that places the ticket in a separate archive pipeline with a single stage - saves messing with filters and creating unnecessary columns in the main pipeline:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ticket enrolment trigger:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Ticket status is Closed&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;and&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Last modified date has not been updated in the last 2 days&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Set property value&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Set ticket property pipeline and status&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;to Archived (Archive pipeline)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 10:33:38 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/321890#M229</guid>
      <dc:creator>BubblePPM</dc:creator>
      <dc:date>2020-02-26T10:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/816047#M880</link>
      <description>&lt;P&gt;Agreed, a built-in solution for archiving tickets is a must. Coming from Zendesk, we're used to tickets going from solved to closed automatically after a few days, then automatically archiving in a separate searchable area after that. The fact that closed tickets stay on a pipeline indefinitely unless someone uses a filter or deletes the tickets is not ideal.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 21:08:24 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/816047#M880</guid>
      <dc:creator>LJam23</dc:creator>
      <dc:date>2023-07-05T21:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: Archive Ticket</title>
      <link>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/969144#M1099</link>
      <description>&lt;P&gt;How do you handle preventing those Archived Tickets from reopening if a customer replies?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also what about reporting? Do you just combine reporting off your Archive Pipeline and "Active" Pipeline?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2024 13:05:10 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Customer-Feedback-Tool/Archive-Ticket/m-p/969144#M1099</guid>
      <dc:creator>SSmith184</dc:creator>
      <dc:date>2024-04-30T13:05:10Z</dc:date>
    </item>
  </channel>
</rss>

