Please make it so each Reasons is associated with a specific CTA Type

Thanks for the feedback Harris. I also believe that the option to have reasons by type is valuable. 

Thanks for posting, Harris!  And thanks for responding, Sidhu!  For all of these drop-down options, even having a 'search' would be helpful.  Once a CSM has used Gainsight for a while, we know what reasons we need so to be able to type "Training" (for example) & have it come right up would be great.  

Even within the "Event" type; having some ability to search, sort, and otherwise filter CTA reasons would be very helpful.

I was about to post a new idea to the Community and noticed this post so I figured I would add my comments here.  I would LOVE (!!!) to have the ability to set up unique sets of reason codes for each CTA type to ensure that the reason codes are relevant for that CTA type.  That way we could tailor the reasons to fit the nature of each CTA type.

Same with Kimberly here - was searching for similar feature request before posting a new one. 

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. 
 

I'm posting too! I noticed this thread is older, and we launched Gainsight in April, but we're already finding this to be an issue, even with only 8-10 reasons. Users are selecting the wrong reasons based on types and it's making our reporting muddy.

It would be great to have this feature!

I'd like to add my support to this as well. It seems like this should be pretty basic functionality given how Salesforce is built. Being able to have a restricted list of reasons codes depending on the CTA type created will be insanely valuable for granular reporting.

We are considering this for next quarter; will share an ETA once the project is picked up. 

What else would you say should be dependent on the CTA Type? Status perhaps?

I'd like to add my support to this request.
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.

I'm adding my vote as well.  We're rolling out Gainsight starting with manual CTA creations just to get a couple CSMs and one account manager familiar with the system.  The multitude of reasons across all CTA types leads to input / reporting errors and time lost sorting through reasons to find the correct one.