I've noticed that when a contact is updated - say they move companies - they seem to inherit the "client" lifecycle stage from the previous company. So I want to build a workflow to address this:
Trigger Event: Contact's Company Changed
If Company =/= lifecycle stage "client" then change contact's lifecycle to "awareness"
This is probably oversimplified - the new company could be a prospect, I suppose.
I'd also like to surface a notification to my client service rep that a user from a client is at a new org, so they can initiate a conversation about a discount (or something) for advocating for our product at the new org.
Keep in mind that resetting the lifecycle stage will affect any reports that display when contacts entered certain lifecycle stages – another reason why I'd recommend creating a new contact for the person at the new company and not simply re-associating the existing one.
Let me know if you have any follow-up questions or need more details on anything above!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Keep in mind that resetting the lifecycle stage will affect any reports that display when contacts entered certain lifecycle stages – another reason why I'd recommend creating a new contact for the person at the new company and not simply re-associating the existing one.
Let me know if you have any follow-up questions or need more details on anything above!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Thanks Karsten - that's very helpful. Creating duplicate entries in the CRM is so contrary to how I'd typically think about this, it hadn't crossed my mind. I appreciate you taking the time to walk me through this. Thanks very much. I will have to think it over.