<?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: Overlapping workflow best practices in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722523#M2809</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/9030"&gt;@InciteJoe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I agree with &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;, the email frequency safeguard feature and the option to remove contacts from workflows are great tools for this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Personally, I would never want to receive two overlapping series of emails. From a marketer's standpoint it also doesn't make a lot of sense: You designed a series of emails specifically to work towards a specific goal, a next conversion, a meeting booked etc. If two or more nurturing workflows overlap, it's unlikely that this goal will be achieved, too much going on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my opinion it comes down to whether you want to allow the first conversion to continue its nurturing or the last. The first makes more sense in my opinion. For your workflow design that means that the workflow that delivers the content should never contain the follow up emails. It should only deliver the content and then 'nominate' the contact for a nurturing workflow where they enter if they are not being nurtured already. (This can of course be solved with if/then branches in the original workflow but I'm not a fan of it. Especially with a large number of content pieces this becomes unmanageable at some point.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lastly, you want to think about how to deal with scenarios when contacts have already downloaded a piece of content they're about to receive in a nurturing workflow. Here you'll have to work with if/then branches referring to those specific form submissions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
    <pubDate>Thu, 24 Nov 2022 05:07:38 GMT</pubDate>
    <dc:creator>karstenkoehler</dc:creator>
    <dc:date>2022-11-24T05:07:38Z</dc:date>
    <item>
      <title>Overlapping workflow best practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722194#M2804</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Background&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I have around 10 different workflows for when someone requests different guides on my website, the form fill triggers a copy of the guide to be sent via email too.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Change to current process&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I am now thinking of adding more steps, so for example after a period of time send a series of follow up emails to the contact to ask how useful they found the content and attempt to schedule in a call with them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Potential issue&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Now say for example Contact A has filled in multiple forms for different guides, what is the best way for me to make sure they don't end up being spammed by multiple follow up emails for each guide?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 15:26:27 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722194#M2804</guid>
      <dc:creator>InciteJoe</dc:creator>
      <dc:date>2022-11-23T15:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: Overlapping workflow best practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722407#M2808</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/9030"&gt;@InciteJoe&lt;/a&gt;&amp;nbsp;such a great question. I love that you're thinking about the UX in your content.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Background for me: I used to be the marketer for a mortgage bank, where we created home buying guides galore. Each one had a workflow email sequence attached. For those who would download multiple guides, I always figured they'd want all the information. However, I recognize it can be a lot, even when the emails all offer different content.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have marketing hub enterprise, you can&amp;nbsp;&lt;A href="https://knowledge.hubspot.com/email/set-up-an-email-frequency-safeguard" target="_blank" rel="noopener"&gt;set up an email frequency safeguard&lt;/A&gt;. Otherwise, it's a matter of thinking about your workflows in levels. If you have 10, are they split up by buyer's journey stages (awareness, consideration, decision) or funnel (TOFU, MOFU, BOFU) to where you can remove from specific workflows?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For instance, once they download a MOFU offer, your workflow could remove them from any other TOFU workflows.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danmoyle_0-1669237313813.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/79834iE01BC17CA2664877/image-size/medium?v=v2&amp;amp;px=400" role="button" title="danmoyle_0-1669237313813.png" alt="danmoyle_0-1669237313813.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I hope that helps get the thoughts going for you.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 21:02:41 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722407#M2808</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2022-11-23T21:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: Overlapping workflow best practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722523#M2809</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/9030"&gt;@InciteJoe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I agree with &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;, the email frequency safeguard feature and the option to remove contacts from workflows are great tools for this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Personally, I would never want to receive two overlapping series of emails. From a marketer's standpoint it also doesn't make a lot of sense: You designed a series of emails specifically to work towards a specific goal, a next conversion, a meeting booked etc. If two or more nurturing workflows overlap, it's unlikely that this goal will be achieved, too much going on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my opinion it comes down to whether you want to allow the first conversion to continue its nurturing or the last. The first makes more sense in my opinion. For your workflow design that means that the workflow that delivers the content should never contain the follow up emails. It should only deliver the content and then 'nominate' the contact for a nurturing workflow where they enter if they are not being nurtured already. (This can of course be solved with if/then branches in the original workflow but I'm not a fan of it. Especially with a large number of content pieces this becomes unmanageable at some point.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lastly, you want to think about how to deal with scenarios when contacts have already downloaded a piece of content they're about to receive in a nurturing workflow. Here you'll have to work with if/then branches referring to those specific form submissions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2022 05:07:38 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/722523#M2809</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2022-11-24T05:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Overlapping workflow best practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/730744#M2960</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;&amp;nbsp;that is very helpful&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2022 11:38:28 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/730744#M2960</guid>
      <dc:creator>InciteJoe</dc:creator>
      <dc:date>2022-12-14T11:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: Overlapping workflow best practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/730745#M2961</link>
      <description>&lt;P&gt;Thanks &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2022 11:39:52 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Overlapping-workflow-best-practices/m-p/730745#M2961</guid>
      <dc:creator>InciteJoe</dc:creator>
      <dc:date>2022-12-14T11:39:52Z</dc:date>
    </item>
  </channel>
</rss>

