New Idea
Ability to limit CTA Reason & CTA Types
Would like the ability to "lock" CTA Reason types for triggered CTAs so that end users cannot change them. We have subsequent rules with logic that is dependent on reason codes.
Would also like the ability to hide certain CTA Types from CSMs when they go to create a manual CTA, but still make those CTA Types available for use by the rules engine.
In order to faciliate automated workflows, we are leveraging some special CTA Types with required fields associated with them...but we don't want CSMs creating manual CTAs using those Playbook/CTA Types.
Would also like the ability to hide certain CTA Types from CSMs when they go to create a manual CTA, but still make those CTA Types available for use by the rules engine.
In order to faciliate automated workflows, we are leveraging some special CTA Types with required fields associated with them...but we don't want CSMs creating manual CTAs using those Playbook/CTA Types.
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.