I have built what is to date a pretty effective ATS system within my HubSpot. Only issue I am having is auto updtaes of Lifecycle for contacts that are applicants.
See below, I have built a workflow that looks for changes and then automatically changes it to null, but I’d like to find a way of classifying/marking an ATS contact as not to update lifecycle.
Any ideas?
It looks like you are trying to keep Lifecycle Stage blank, without seeing the rest of the workflow, I have two ideas:
1. Create a separate property that flags these contacts, even if it is simple like:
Applicant: Yes (or No)
Then add a rule to your criteria that excludes Applicant Yes from your updates.
2. We also use persona for exclusion - if Persona = applicant, could you make Lifecycle = Other so it isn’t constantly changing?
Other is at the top of the Lifecycle stages, so it can’t be reset to subscriber without blanking it out first.
For example, we work with Realtors, so we set their Persona to Realtor and have a workflow that sets their lifecycle stage to Other - we use this to exclude them from customer workflows, but also if they subscribe to our blog or submit a lead form (known to happen), it won’t change them to a subscriber or a lead (desired result, since usually they are trying to fill the form out for their clients, not themselves).
Hi @Anonymous , thanks for your feedback. I hadn’t considered using that method and persona. I’ll go away and work on that, I think that wil lbe more reliable than what I have.
Hi @SWilsonA4u,
How are these applicants getting into your CRM? There are some auto-updates to the Lifecycle stage property which can’t be turned off, e.g. when a contact converts on a blog subscription form, is created through a conversation, or is manually created in the contacts index page. In your screenshot, you can see that the oldest update was through conversations. There’s nothing you can do about this, see here, unfortunately (except asking for a change in the HubSpot Ideas section of the community).
For any other assets that update the Lifecycle stage (website forms, workflows etc.), you’d have to make sure that you exclude these contacts from those updates – although it seems like you’re on top of that already.
Your workflow that clears the value of Lifecycle stage is a pretty good, low effort solution. As long as there isn’t any other automation based on the value “Subscriber”, I wouldn’t worry about it. If there is, I’d recommend labeling applicants with a custom property or use the Persona property to exclude them from any communication that you don’t want them to receive.
Hope this helps!
Thanks @karstenkoehler
applicants are coming in through conversatiosn or webforms on a form embedded on a page on our website. My workflow RMT1 contains the perameters t oensure that thsi only acts on the two specific sources.
The Persona option is definitely a good suggestion and I’ll give it a try
Appreciate your help.
regards
Stuart
