New Idea
Questions on Federated Admin (CTA Statuses)
I'm running into an issue with Federated Admin for relationship CTA configuration and want to make sure I am understanding this correctly.
I am working on one relationship type, CAM, for HPE. They have 6 of their own CTA Types. By default, there is are the 7 CTA statuses (New, WIP, and a bunch of closed ones). If any of my CTA types need to have their own customized statuses, you have to turn off all of the global statuses so they don't show on that one type and then create the new statuses there. However, if my other CTA types need to have all of those same global statuses, I have to recreate them on each type. It seems to me that there should be a way to turn off global statuses by each type so you don't have to duplicate everything.
This also impacts reporting because I will have 5 'New' statuses that are on the other CTA Types that I don't need custom statuses on.
It may be a bit of a bold statement, but for multiple reasons, I don't think we should ship the product with a bunch of default types/statuses/reasons/etc. It can either complicate things like I have explained above, or customers (or services team) doesn't clean them up and remove not applicable ones and it actually confuses things for end users. If I'm a new CSM and see a bunch of items in the picklist that I don't understand, I would get discouraged from using the tool. It would also force the Gainsight admin to think through what statuses/reasons/etc actually apply to each type to refine the processes.
I am working on one relationship type, CAM, for HPE. They have 6 of their own CTA Types. By default, there is are the 7 CTA statuses (New, WIP, and a bunch of closed ones). If any of my CTA types need to have their own customized statuses, you have to turn off all of the global statuses so they don't show on that one type and then create the new statuses there. However, if my other CTA types need to have all of those same global statuses, I have to recreate them on each type. It seems to me that there should be a way to turn off global statuses by each type so you don't have to duplicate everything.
This also impacts reporting because I will have 5 'New' statuses that are on the other CTA Types that I don't need custom statuses on.
It may be a bit of a bold statement, but for multiple reasons, I don't think we should ship the product with a bunch of default types/statuses/reasons/etc. It can either complicate things like I have explained above, or customers (or services team) doesn't clean them up and remove not applicable ones and it actually confuses things for end users. If I'm a new CSM and see a bunch of items in the picklist that I don't understand, I would get discouraged from using the tool. It would also force the Gainsight admin to think through what statuses/reasons/etc actually apply to each type to refine the processes.
Reply
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.