<?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: Sending cap for a specific workflow - I don't have enterprise in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769682#M3319</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/479252"&gt;@Louisegbennett7&lt;/a&gt;! This is a great question and example of how it works in a different system. Unfortunately, I don't know of a way to do so the way you described in Marketo. Especially without being Enterprise. But even then, I don't think it works as granularly as you described.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes if you have a suppression with that criteria, it will mean the contacts in that list will not be enrolled - it doesn't mean that if they hit tht list in the middle of the workflow they would pause.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However that has me wondering if you can use the "delay until event happens" functionality if you re-engineered how you're thinking about the communications. It kinda messes up the whole idea though. You want the emails to go out unless something changes, not go out after something changes. But that's the only thought that comes to mind for your specific question.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 16 Mar 2023 13:03:33 GMT</pubDate>
    <dc:creator>danmoyle</dc:creator>
    <dc:date>2023-03-16T13:03:33Z</dc:date>
    <item>
      <title>Sending cap for a specific workflow - I don't have enterprise</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769066#M3310</link>
      <description>&lt;P&gt;Hi, we don't have enterprise so the email frequency safeguard doesn't apply to me. I am in the process of setting up a workflow to promote our latest content, sending an email every two weeks. This is in addition to other campaign-specific workflows and sales engagement.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm looking for a way to ensure contacts don't receive the next email in this workflow if they have been contacted by sales or received another marketing email in the last 3 days. I have set up a list of contacts who meet this criteria. However, if I add this to the suppression list for the workflow, does this mean people will be un-enrolled if they meet the criteria and then presumably, once they are no longer on the suppression list, they wouldn't be re-enrolled into the workflow?&lt;/P&gt;&lt;P&gt;I've previously used Marketo and I know this 'pauses' the workflow send until the next available date when someone can be contacted in-line with sending limits. I'm really hoping there is a HubSpot workaround for this. Please help!&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 13:51:31 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769066#M3310</guid>
      <dc:creator>Louisegbennett7</dc:creator>
      <dc:date>2023-03-15T13:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: Sending cap for a specific workflow - I don't have enterprise</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769366#M3316</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/479252"&gt;@Louisegbennett7&lt;/a&gt;,&amp;nbsp;thank you for posting in our Community and providing details about it.&lt;/P&gt;
&lt;P&gt;I want to invite our top experts to this conversation&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/87451"&gt;@Ben_M&lt;/a&gt;&amp;nbsp;any recommendations to&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/479252"&gt;@Louisegbennett7&lt;/a&gt;&amp;nbsp;matter?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Pam&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 21:45:28 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769366#M3316</guid>
      <dc:creator>PamCotton</dc:creator>
      <dc:date>2023-03-15T21:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Sending cap for a specific workflow - I don't have enterprise</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769682#M3319</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/479252"&gt;@Louisegbennett7&lt;/a&gt;! This is a great question and example of how it works in a different system. Unfortunately, I don't know of a way to do so the way you described in Marketo. Especially without being Enterprise. But even then, I don't think it works as granularly as you described.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes if you have a suppression with that criteria, it will mean the contacts in that list will not be enrolled - it doesn't mean that if they hit tht list in the middle of the workflow they would pause.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However that has me wondering if you can use the "delay until event happens" functionality if you re-engineered how you're thinking about the communications. It kinda messes up the whole idea though. You want the emails to go out unless something changes, not go out after something changes. But that's the only thought that comes to mind for your specific question.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 13:03:33 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769682#M3319</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2023-03-16T13:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: Sending cap for a specific workflow - I don't have enterprise</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769687#M3320</link>
      <description>&lt;P&gt;I don't think the frequency cap is what you are looking for. In most cases, I usually recommend leaving that off as the cap will force a not sent to that user and they will skip the step in question. You are also correct not to use suppression as that will remove the contact entirely from the workflow.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The closest you can come to in hubspot is to do an if/then branch and look for membership to that list before each send and hold them for a day or two before sending. A more complex solution would involve a workflow tied to your list that sets a property on/off upon entry/exit from that list. Then use the Delay Until Event Happens action in your email workflows to look for that property to update before each send.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will say that having used many automation platforms moving off Marketo for those who have used it excusively, can be challenging. The other big players like Hubspot, Pardot/MC, and Eloqua all tend to be closer in alignment with this style of workflow. What I would recommend is if you have your Marketo workflows mapped out that you sit down with someone from the Hubspot side to try and figure out ways to rebuild in this type of architecture to your Hubspot plan capabilities.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 13:09:00 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769687#M3320</guid>
      <dc:creator>Ben_M</dc:creator>
      <dc:date>2023-03-16T13:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: Sending cap for a specific workflow - I don't have enterprise</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769703#M3321</link>
      <description>&lt;P&gt;That's great advice to take the Marketo map and work with a HubSpot expert, &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/87451"&gt;@Ben_M&lt;/a&gt;. Since it's not 1:1 between systems, it will definietly take some strategic thinking.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 13:17:15 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Sending-cap-for-a-specific-workflow-I-don-t-have-enterprise/m-p/769703#M3321</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2023-03-16T13:17:15Z</dc:date>
    </item>
  </channel>
</rss>

