<?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: Distinguish between tasks in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015251#M9651</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/774541"&gt;@KRoos&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Task queues could indeed be helpful with what you're trying to do:&amp;nbsp;&lt;A href="https://knowledge.hubspot.com/tasks/use-task-queues" target="_blank"&gt;https://knowledge.hubspot.com/tasks/use-task-queues&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Generally however, I'd recommend solving this directly the source. A lot of companies and users make the mistake to use generic names in their tasks like "Follow-up", "Call" etc. When tasks are created, they should be given a distinct name, a type and a priority to make it easy to filter and complete them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This can of course feel like a chore when tasks are created manually but it's necessary. When tasks are created through workflows in large numbers, this is even more important. If workflows simply create tasks as "Follow-up", they're indistinguishable by title. Instead, check those workflows and make sure the "Create task" action also specifies priority and uses personalization tokens in the task title to better understand what the task is about.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For existing tasks that haven't been set up like this, there is unfortunately no magic wand. Activity-based workflows don't exist yet so the team would have to work through the existing tasks to the best of their capabilities&amp;nbsp;– and have better task hygiene from now on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if you have any follow-up questions!&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jul 2024 09:55:04 GMT</pubDate>
    <dc:creator>karstenkoehler</dc:creator>
    <dc:date>2024-07-24T09:55:04Z</dc:date>
    <item>
      <title>Distinguish between tasks</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015246#M9650</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the sales team has a lot of tasks, like acquisition tasks, follow-up tasks (like I've spoken to a client, he's interested, but wants me to call back in a couple of months), workflow tasks, tasks from deals (to follow-up on an offer). They are now overwhelmed with tasks and it's hard to distinguish between the tasks that need to be done and the tasks whereby it doesn't matter so much if it's being done that day.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the best practice to handle this? Is that to work with priority? Or make 2 seperate task lists (one for acquisition and one for existing customer and workflow tasks, with high priority)?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know what is the best way for a sales team to work with Hubspot and tasks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Kelly&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2024 09:46:40 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015246#M9650</guid>
      <dc:creator>KRoos</dc:creator>
      <dc:date>2024-07-24T09:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguish between tasks</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015251#M9651</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/774541"&gt;@KRoos&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Task queues could indeed be helpful with what you're trying to do:&amp;nbsp;&lt;A href="https://knowledge.hubspot.com/tasks/use-task-queues" target="_blank"&gt;https://knowledge.hubspot.com/tasks/use-task-queues&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Generally however, I'd recommend solving this directly the source. A lot of companies and users make the mistake to use generic names in their tasks like "Follow-up", "Call" etc. When tasks are created, they should be given a distinct name, a type and a priority to make it easy to filter and complete them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This can of course feel like a chore when tasks are created manually but it's necessary. When tasks are created through workflows in large numbers, this is even more important. If workflows simply create tasks as "Follow-up", they're indistinguishable by title. Instead, check those workflows and make sure the "Create task" action also specifies priority and uses personalization tokens in the task title to better understand what the task is about.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For existing tasks that haven't been set up like this, there is unfortunately no magic wand. Activity-based workflows don't exist yet so the team would have to work through the existing tasks to the best of their capabilities&amp;nbsp;– and have better task hygiene from now on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if you have any follow-up questions!&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2024 09:55:04 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015251#M9651</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2024-07-24T09:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguish between tasks</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015255#M9652</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've wondered if you would be the one to respond, you're very quick, thank you &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;Thanks for this. I think working with queues would be a big help. And looking at the task names is also something we should do.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2024 10:00:56 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1015255#M9652</guid>
      <dc:creator>KRoos</dc:creator>
      <dc:date>2024-07-24T10:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguish between tasks</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1022657#M9830</link>
      <description>&lt;P&gt;Could there be task tags similar to deal and ticket tags which would allow to categories tasks a bit more visually?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2024 08:01:00 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Distinguish-between-tasks/m-p/1022657#M9830</guid>
      <dc:creator>Dogtag89</dc:creator>
      <dc:date>2024-08-06T08:01:00Z</dc:date>
    </item>
  </channel>
</rss>

