Skip to main content
New Idea

Questions on Federated Admin (CTA Statuses)

Related products:None
  • September 28, 2017
  • 1 reply
  • 4 views
lisa.mirth
  • lisa.mirth
    lisa.mirth

joseph_siudzinski
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.

1 reply

nadav_shemtov
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • 96 replies
  • September 28, 2017
Joe - this is a huge pain. And something we have to get right - I've seen clients struggling with this (along with the fact that we have global setting we can't turn off - e.g. risk type CTAs - which may not make sense given our new focus and approach on other use cases) 

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings