Using sub-workflows for assignments and notifications
SOLVE
Hi Everyone,
I've been working to optimize my workflows for scalability and encountering an issue that I should think is easy to solve, but can't figure it out..
(I have Enterprise)
Old System:
- I had numerous individual workflows for all our form submissions that would then assign new leads to team members based on Geography
- Each workflow would send internal marketing emails to team members for new leads, or would send a different internal email to team members for existing leads. (Existing leads would include more details/personalization tokens compared to New leads).
New System:
- I created a subworkflow (Child) that only focuses on lead assignments (so I no longer have to re-make or make changes to in the different form submission workflows)
Challenge I'm facing:
- With this change, how I can now determine if the form submitted is from a new or existing lead?
- Previously, it was simple to check if 'Contact is unknown', but that will no longer work.. and I can't send the internal marketing emails until they've gone through the 'child assignments' workflow
Using sub-workflows for assignments and notifications
SOLVE
@hwagner there is likely to be a better suggestion from the others mentioned, but one thing I have done when I run into similar situations and have to set up a new workflow to replace one that is existing and differentiate whether someone is new or not is to set an if/then that says "if create date is after [today, the day I create the workflow]" then the contact is new, otherwise, they are existing. Then I handle potential lead revisits from those new leads through re-enrollment criteria.
If my reply answered your question please mark it as a solution to make it easier for others to find.