We communicate specific messaging based on several personas. We are new to workflows, in instances like this do you create a workflow per persona or do you use branching to include all personas in one workflow with branching?
This comes down to personal preference, the benefits of each option are very subtle. Once you've built out a sequence of actions for one persona, you can either clone the whole workflow or you can clone the branch including all actions. It's virtualy the same.
Multiple workflows would allow you to choose different settings for each persona (for example goals). That would be the key difference.
Sometimes, multiple workflows are needed to cover specific conditions for re-enrollment. However, it's unlikely that you would encounter these situations with your persona messaging workflow.
I prefer the modularity, lower degree of complexity (and hence risk) I get from multiple workflows but I know many HubSpot technical specialists who are a fan of branching logic.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
If you're using the same registration prcoess each month (same form) and it's a "rolling" registration, you might not have to clone anything. You would just update the date and host references on the landing page and in the automated emails. Automated emails can be edited at any time, so right after the February event, you could change the date to the March date, change the host mentioned in the email and just save it – without having to touch or pause the workflow.
If the registration process involves different assets each month (different form, different emails), you could either switch off the workflow and adjust it or, as you suggested, clone it.
Hope this helps!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Thank you for the response. We have these events on a monthly basis, would you clone each email or re-use the same email and simply tweak the details? the details change in the email (dates, host, etc) but the language is pretty similar. My hope would be to change the email content and clone the workflow or maybe just update the contact property based on the action from the original email (no open, open no click, click no submission).
This comes down to personal preference, the benefits of each option are very subtle. Once you've built out a sequence of actions for one persona, you can either clone the whole workflow or you can clone the branch including all actions. It's virtualy the same.
Multiple workflows would allow you to choose different settings for each persona (for example goals). That would be the key difference.
Sometimes, multiple workflows are needed to cover specific conditions for re-enrollment. However, it's unlikely that you would encounter these situations with your persona messaging workflow.
I prefer the modularity, lower degree of complexity (and hence risk) I get from multiple workflows but I know many HubSpot technical specialists who are a fan of branching logic.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
In my point of view, it depends. If your workflow will be so simple, maybe you can use branching to evaluate the persona field first of all. But, in general, I think that "one workflow - one persona" is better in order to optimize and put everything in its place.
Regards,
Rafael López
[ Si esta publicación te ha ayudado con tu problema ayuda a la comunidad marcándola como solución ]
[ If this response helped you, please mark it as a solution ]
Rafael López Head of Marketing Odontonet by Glintt