Somewhat related to this idea, but I need to use different CTA Statuses for one CTA Type. However, for all other CTA Types I need to keep the same core set of Statuses.
In the current implementation, I can create additional statuses under a specific CTA Type, but I cannot hide the other cross-type statuses from visibility within the specific CTA Type.
I need the ability to configure a CTA Type so that it will not inherit one or all of the “All” Type statuses.
Allow ability to disable "all" Statuses for specific CTA types
CS Cockpit & Playbooks
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 E-mail address. We'll send you an e-mail with instructions to reset your password.
Same should go for Reason, Priority, Snooze Reason.
Hi@darkknight ,
We are simplifying the creating and editing process for all CTA Attributes with the Admin Redesign project that is about to be finished soon.
The inheritance concept has been simplified so I think your ask will be possible after that. I am changing the status of this idea to in development. We can revisit if this is solved or not after the release.
Thanks,
Monica
Thanks for the update@mpatra - you’ve referred to this “Admin Redesign Project” in several posts now. Question for you: have any admins been directly involved in giving feedback on the planned designs? Since this is specifically targeting admins, I for one would like to see what these redesign plans are and give feedback on them before they make it to beta, where often very little design feedback is accepted.
@bradley @heather_hansen @gunjanm @spencer_engel @zach_davis @TMaier @matthew_lind @sarahmiracle @ddezuniga ?
Thoughts
Thanks for the update@mpatra - you’ve referred to this “Admin Redesign Project” in several posts now. Question for you: have any admins been directly involved in giving feedback on the planned designs? Since this is specifically targeting admins, I for one would like to see what these redesign plans are and give feedback on them before they make it to beta, where often very little design feedback is accepted.
@bradley @heather_hansen @gunjanm @spencer_engel @zach_davis @TMaier @matthew_lind @sarahmiracle @ddezuniga ?
Thoughts
I know I’ve given plenty of feedback to Gainsight about any number of things, but I know nothing of this, though possibly have contributed unbeknownst to me. Seems like something admin feedback early and often would have been useful.
I get why admin redesign/revamp might be too high level. We’ll be more specific about what’s coming. Happy to connect directly as well.
The other issue is timing. We started doing research for these improvements last year. There were VCAMs in June and Dec 2022, and a combined Ops Council session in April this year.
I don’t like the idea of waiting for the beta because GS betas rarely seem to take actionable design feedback; they are more focused on fixing bugs (which is why I personally don’t participate in them anymore).