I'm looking for tips/advice on moving deals associated to a singe contact, indpendently from eachother.
For context, a contact has potential to have more than one deal that are not related to eachother. Currently, form submissions & property changes at the contact-level are required for a deal to progress through the pipeline but this leads to all assciated deals then being updated in the next step of our proces.
As soon as you have a data point that makes it possible to identify the deal that should be updated to trigger the next steps, this should be rather straightforward. You can use branches in a contact-based workflow to filter the deal that should be updated (for example by deal name or the claim sub-type). You could also look at it from a different direction and start with a deal-based workflow that triggers based on associated contacts. But in the end, you would always need a data point that shows you which deal should move to the next step and which deal(s) should stay untouched. How would you do this, if it would be done manually? In that case, you would also need some kind of data point to decide which deal out of multiple ones to move forward, right?
To manage deals independently, consider using deal-level properties and automation instead of contact-level properties. This way, form submissions and property changes will only affect the specific deal in the pipeline without impacting other deals associated with the same contact.
do the Deals have any sort of differentiator to check if they are the ones that should be edited? So, what would be the data point to identify the correct deal out of multiple ones (even if you were to do it manually)?
So currently, we use Deal Name which isn't ideal. We also have Claim Sub-type which is specifc to the claim the deal is a part (being a law firm).
The main issue we are finding is the change at the Contact-level property will trigger all deals associated to that contact. It would therefore be useful to know any best tricks around updating Deal-level properties to replace this & how this then triggers the next step. Hope this makes sense!
As soon as you have a data point that makes it possible to identify the deal that should be updated to trigger the next steps, this should be rather straightforward. You can use branches in a contact-based workflow to filter the deal that should be updated (for example by deal name or the claim sub-type). You could also look at it from a different direction and start with a deal-based workflow that triggers based on associated contacts. But in the end, you would always need a data point that shows you which deal should move to the next step and which deal(s) should stay untouched. How would you do this, if it would be done manually? In that case, you would also need some kind of data point to decide which deal out of multiple ones to move forward, right?