+at least 2
The use cases that come immediately to mind include:
- All child Objectives are completed, so the Success Plan can be Closed.
- Data cleanup (we’ve all discovered a trove of abandoned Success Plans somewhere, sometime)
- Change in company or customer, whereby if a customer moves to a new segment, or churns, that we want to close the Success Plan.
Having this in the Rules Engine, akin to CTA Closure functionality, would increase automation options.
Now that I’ve campaigned for a UI-centric solution, @sagan_sherlin , you can likely accomplish this with the Success Plan API, if you’re adventrous.
https://support.gainsight.com/Gainsight_NXT/API_and_Developer_Docs/Success_Plan_APIs/Success_Plan_APIs
Updating success plan via rules engine is in our short term roadmap. Admins can setup a rules action to update the status, owner, or any attribute of the success plan.
Excellent @Anil Raj Pujari . With so many Gainsight customers utilizing Success Plans, and because Success Plans tend to be “around” longer than individual CTAs, productizing more update capabilities into the Rules Engine will be of significant value.
Hi @Anil Raj Pujari - is there any idea of when updating success plans via rules engine?
Great question I’m subscribing. It's something we can't wait to hear updates on!
Wondering if the Beta participants for Horizonized Rules engine @andreammelde, @tonyaclemons, @Elana Cipin, @jrich might have any news for us on this?
@anirbandutta I believe it allows you to create or update, but not close.
There is an issue with the action in Beta where it does not work if you do any steps to transform or merge data so frankly it is pretty useless in the current state of Beta. I’m hoping they get it fixed by release.
I have a different solution that we are using to update certain fields using an external API that comes back into GS to update. So I can run the rule and determine what needs to be changed and use the API to update, but it is definitely more complicated than just using a rule action. This includes updating the status
Definitely having a rule is always easier than mass edit. I also periodically go to mass edit to close out rules, and use the same conditions. But then I have to set up the same conditions every time, which could easily run in the background with a rule instead.
Just to stir the pot a bit: I’m still very much behind more admin automation to close Success Plans, though there’s an interesting Process question underneath this functionality request:
Why do we need this feature in the first place? Put another way, what part of closing a Success Plan isn’t valuable enough or isn’t impactful enough for CSMs, such that we need to automate the closure of the Success Plan?
^ 100% agree @matthew_lind! Biggest use case for my business right now is that we were impacted by tech layoffs. The responsibilities of the CSM totally shifted, and so did books of business to entirely new owners. So with testing out what does work within Success Plans for the new group, having the ability to automate closing would save time!
Has there been any update specifically on closing CTA tasks through rules engine? I know you can close entire success plans and call to action types, but not child tasks.