I’m building out a deal workflow for a client. They have annual subscriptions. The subscriptions are automatically renewed on the Next Billing Date. I’m creating a Deal about 60 days prior to the Next Billing Date so they can reach out and make sure nothing needs to change and the company wants to renew still.
I also want to include an automatic way for the Deal to move to Closed Won if there are no changes and the subscription renews on it’s on. But I’m not sure what property to use. I tried branching from the Next Billing Date but I have to put in a specific date not just if it has changed. Any ideas?
Hey @KEastman15,
Thanks for posting in the Community!
Just to clarify for my own sake, what would you expect to be updated in any particular deal if there is a change? I think identifying this would help narrow down which property(ies) to use as a trigger for this workflow.
Additionally, I’d like to tag in some workflow experts to see what suggestions they may have. @Josh , @trevordjones, and @RomyFuchs1 - any thoughts for @KEastman15 ?
Shane, Senior Community Moderator
Hi @KEastman15,
Maybe this could be an option for your logic, if you already have a 60-day delay before the branch.
I created the workflow using a subscription as the enrollment criteria so that I could create the deal. When I try to add actions from the deal later in the workflow it wants to associated all deals and this subscription would be attached to two deals. Maybe I need to rethink the whole thing.
@KEastman15 Yes, in that workflow setup you won’t be able to reliably close the deal later.
I’d probably handle that with a separate deal-based workflow instead.
Then you could use associated subscription criteria there, and also make the deal filters more specific, for example:
- the deal is still open (not Closed Won/Lost)
- and it’s either in a renewal pipeline or marked with a custom renewal property
That way you’d have a better chance of targeting only the renewal deal you actually want to close.