Skip to main content

It would be awesome if we had a a checkbox or picklist on the "Call to Action" action in the rules engine where we could say "Don't create this CTA if one was created in last (X) days".  This would be similar to how the JO email feature works, with the 30/60/90/Lifetime selector.



I have a few customers who see the CTA come in, but there is nothing they can do to action on it and want to close it.  But closing it doesn't change the underlying data, so the CTA comes back the next day.  They'd like to reevaluate the next potential CTA after X days.



I can do this by adding a date field or something to Salesforce, but we'd have to do that for every CTA type, which isn't really manageable.

I would love this.  We have many scenarios where a CTA can be resolved without the underlying data changing; we want to have our reps check in periodically on these accounts, but don't want them to have to keep the CTA open or to have to close it every time we run the rule.  We're going with data triggers but as the # of CTAs we run grows, this will become unwieldy at best.
Totally agree, especially when the CTA has to do with adoption/usage data that may not be urgent, and could take some time for the underlying data to be resolved, for example the processing of a renewal order form.
Hi,



This is already in our short term roadmap. I will keep you updated about exact ETA.



Thanks,

Nitisha
Fantastic to hear.  Thanks, Nitisha!
Sean - I feel your pain.  We use the Snooze function so the CSM can dismiss a CTA for X amount of time without closing it.  



A nice thing about this is you have control over Snooze reasons so you can capture and bucket what situations arise.  My only grip with Snooze is they don't time stamp when that CTA is moved to a snoozed status.
Similar posted previously: https://community.gainsight.com/gainsight/topics/rules-engine-do-not-trigger-cta-if-it-has-already-b...
We ended up solving this by creating fields that track the last date a CTA with a specific playbook was created, and then data triggers that update this field every time a CTA is created.  We then use this date as a filter in the rules engine.  We don't have too many CTAs that require this so it is manageable right now.
Awesome to hear, this is a big one for us too.. Is there an estimate of what "short term roadmap" means? 
Hi Osha,



Most likely, this enhancement will be a part of Winter release.



Thanks,

Nitisha
With 5.5 release, you can prevent the creation of repetitive CTAs. Read more about it here. 

Reply


Terms & ConditionsCookie settings