Please make it so each Reasons is associated with a specific CTA Type
CS Cockpit & Playbooks
We have a list of 20+ reasons. Some of these reasons are only used when CTA type = opportunity, some reasons are oly used when CTA type = Risk.
When creating a CTA our SMs need to scroll through a long list when half the Reasons are not applicable.
When creating a CTA our SMs need to scroll through a long list when half the Reasons are not applicable.
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.
With the recent ability to customize CTA types, we are going more granular and specific on the cockpit management and reporting. I already have 15 reasons, but it will only expand. with 3-5 reasons designed specifically for each type.
I would very much share the frustration that Harris had, since it makes my team much less efficient every time they manually create a new CTA and leads to increased data fidelity issue, since they opt out and just pick what's on the top.
Search ability is one step forward, but really, it's the look-up relation btw CTA type and CTA reason that I would be advocating for. Thanks.
It would be great to have this feature!
What else would you say should be dependent on the CTA Type? Status perhaps?
While I can think of cases, where a certain type of definitions of Types/Reasons might make the same reason part of several types - I do think that adding a parameter that allows creating this dependency is good to have.
More so than having a search feature, there is a governance component here as we want to make sure our team is only selecting a reason when it is supposed to be used and does not skew our reporting.
Associating CTA reason, status and other attributes with a CTA Type will be available in Feb release.
Thanks,
Nitisha
This capability is available now.
Thanks,
Nitisha
'Categories' are meant to solve the problem of being able to report consistently across the organization. For example, three divisions using Gainsight might have three variants of the same CTA Type that make the most sense to them. But at the organization level, we ideally would want to club the three together under the same bucket or category.
To define Reasons specific to a CTA Type, you can pick the right option from this drop-down and then add the codes there:
Thanks,
Manu
Just like we can associate playbooks to CTA types we should be able to do the same for Reasons. That was the original request.