We use cookies to make HubSpot's community a better place. Cookies help to provide a more personalized experience and relevant advertising for you, and web analytics for us. To learn more, and to see a full list of cookies we use, check out our Cookie Policy (baked goods not included).
Mar 30, 2022 6:07 AM
We have the ’Sync lifecycle stages’ enabled in our organization. However, there are scenarios, where we would like to use a custom automation instead of the standard setting.
In the early stages of the company lifecycle (subscriber, lead), the standard automation to update the contacts is usually just fine. It becomes more tricky when we talk about existing customers and bigger corporations especially. We would like to approach different decision makers and departments as new leads, so they shouldn’t be updated as customers. That’s the most common use case.
We have thought about turning off the standard lifecycle automation, but then it requires us to build a set of custom workflows, so that contact lifecycle gets updated in all kinds of scenarios. The lifecycle stage would be the most obvious trigger in these workflows, but I wonder if there are any additional triggers, filters etc. which should be noted. I’d be very happy to hear any ideas or references, which would help us to implement this!
Solved! Go to Solution.
Mar 30, 2022 6:26 AM - edited Mar 31, 2022 6:56 AM
Hi @EPirinen
The best advice I, or anyone, can probably give you is:
You probably will need to turn off the automatic lifecycle stage update. Then, I suggest you build individual, if/then branching workflows for each lifecycle stage - base the branching off really simple, explicit company properties for the best results.
Even when automatic updates are on, I build custom automation for the MQL/SQL stages following these basic principles.
Hope this helps.
Mar 30, 2022 6:26 AM - edited Mar 31, 2022 6:56 AM
Hi @EPirinen
The best advice I, or anyone, can probably give you is:
You probably will need to turn off the automatic lifecycle stage update. Then, I suggest you build individual, if/then branching workflows for each lifecycle stage - base the branching off really simple, explicit company properties for the best results.
Even when automatic updates are on, I build custom automation for the MQL/SQL stages following these basic principles.
Hope this helps.