1 Accepted solution
Workflow delays
SOLVEHi @CateDuarte,
Yes, there is, especially if you're waiting for actions by contacts. Let's take this workflow:
Version 1
Contact is enrolled
Send marketing email
Delay 7 days
Check if email was clicked
Send a follow-up email if contact did not click first email
Version 2
Contact is enrolled
Send marketing email
Check if email was clicked
Delay 7 days
Send a follow-up email if contact did not click first email
In version 2, HubSpot would send the marketing email and, within split seconds, check immediately whether the email was clicked – which of course it can't have been. It's only been split seconds. The contact needs time to actually interact with the email before we then check, after 7 days. In version 2, all contacts would go down the branch of contacts who did not click. Not a single contact can click that fast.
This is of course a very specific example. Sometimes, it doesn't make a difference, adding a delay before a branch however means that you're workflow is leaner (one delay instead of multiple delays depending on the number of branches).
If you have a specific example, feel free to share a screenshot.
Best regards!
| Karsten Köhler |
 | Did my post help answer your query? Help the community by marking it as a solution. |
Workflow delays
SOLVEHi @CateDuarte,
Yes, there is, especially if you're waiting for actions by contacts. Let's take this workflow:
Version 1
Contact is enrolled
Send marketing email
Delay 7 days
Check if email was clicked
Send a follow-up email if contact did not click first email
Version 2
Contact is enrolled
Send marketing email
Check if email was clicked
Delay 7 days
Send a follow-up email if contact did not click first email
In version 2, HubSpot would send the marketing email and, within split seconds, check immediately whether the email was clicked – which of course it can't have been. It's only been split seconds. The contact needs time to actually interact with the email before we then check, after 7 days. In version 2, all contacts would go down the branch of contacts who did not click. Not a single contact can click that fast.
This is of course a very specific example. Sometimes, it doesn't make a difference, adding a delay before a branch however means that you're workflow is leaner (one delay instead of multiple delays depending on the number of branches).
If you have a specific example, feel free to share a screenshot.
Best regards!
| Karsten Köhler |
| Did my post help answer your query? Help the community by marking it as a solution. |
