Reccuring/Real time CTAs
CS Cockpit & Playbooks
Today, we run CTAs 3 times for things we want our CSMs to be on top of more frequently (NPS detractor score, a health score dropping, etc.). However, sometimes this results in the same CTA being created over and over despite our "unique rules." This is happening when the CSM closes the first CTA before the next rule runs. What are the plans for real time recurring CTAs that are not 3 separate rules?
Additionally, I know you have a manual "set to recurring" button in Cockpit, but are their plans to add this to a rule? Example, I create a rule and I want it to run every 90 days after close (like a performance review). Today I get around this by creating that CTA + 90, + 180, + 360 but that doesn't scale past a couple years.
Additionally, I know you have a manual "set to recurring" button in Cockpit, but are their plans to add this to a rule? Example, I create a rule and I want it to run every 90 days after close (like a performance review). Today I get around this by creating that CTA + 90, + 180, + 360 but that doesn't scale past a couple years.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
As far as the recurring: I know a customer who's had success setting up a custom field on the Account (or Customer Info object) to indicate "month number that this customer started". Then you only need to build one Rule that generates the CTA for all customers who started in that month, regardless of what year they started. In fact, you don't even need a Rule for each month, since, if there's a 90-day recurring CTA, then customers who started in January, April, July, or October are all on the same cycle.
"Create CTA once in ___ " is perfect here.
And especially if you're running into a race condition where human interaction is happening before the next series of system updates.
https://support.gainsight.com/Product_Documentation/CTAS_Tasks_and_Playbooks/Admin_Configuration/Con...
The reason why the CTA once in x days does not work in this specific case is because the identifiers for the CTAs used for the verification are
1. Rule ID
2. Account ID
3. Action ID
Since there are 3 different rules the CTAs did not pass the identifier check so it creates a new CTA for each rule.