Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    Molly.McQ
    Molly.McQHelper ⭐️

    Enable Global Configuration of Stakeholder Type (Staircase)New Idea

    Currently in Staircase, Stakeholder Type must be configured on a per-account basis, even for automated stakeholders like Google Meet/Gemini, Zoom, or Teams meeting summaries. This creates a lot of unnecessary manual work and increases the risk of inconsistent setup, particularly in environments where account data is not perfectly clean by Staircase standards due to partners, resellers, or indirect customer relationships. The process becomes especially tedious for major automated stakeholders like Gemini and Zoom, where automated notes and summaries provide valuable insights that Staircase can and should analyze. This is further compacted by the fact that there are no notifications to alert us when a new stakeholder is added to an account, so this is something we would have to manually identify and track. It’s worth noting that Staircase does not appear to offer an OOTB way to be notified specifically when a new stakeholder is added, particularly for automated sources like Gemini, Zoom, or Teams. If this is possible, it isn’t documented anywhere, nor is it obvious from current configurations. This  would require manual discovery, which is not a scalable or intuitive process in fast moving environmentsIn real world operations, perfect 1:1 contact hygiene is rarely possible. Automated stakeholders often appear across multiple accounts, and while Staircase is not currently designed to efficiently handle cases where valid contacts exist on more than one account (for example, in partner or reseller models- see related Community Idea: Staircase - Domains Associated to Multiple Accounts with multiple upvotes), there's a clear need for a way to define and apply Stakeholder Type globally for recurring automated stakeholders. The Stakeholder Type should be preserved wherever that stakeholder appears, reducing the need for repetitive manual updates at each account levelThis enhancement would allow admins to set Stakeholder Type at a global or system level for specific stakeholders, such as Gemini being classified as “Automated,” with that setting automatically applied wherever the stakeholder appears. Any updates to the global Stakeholder Type should carry over to all applicable accounts, with an optional override at the account level if needed.The value of this would be significant for teams using Gong, Google Meet/Gemini, Teams, Zoom, or other automated meeting transcription and notes tools. It would reduce administrative workload, improve the consistency and accuracy of Stakeholder classifications, and increase the reliability of insights, particularly in complex account models involving partners and resellers.It is clear from the related community idea linked above re: domains associated with multiple accounts that many Staircase customers face similar challenges when handling contacts who exist across multiple accounts. Considering how widely automated tools like Zoom and Gemini are used, and considering the continued rise in these products and tools, there’s a strong case for enabling global stakeholder configuration- for automated stakeholders in particular. This would ensure insights from these sources are applied consistently across all eligible accounts, benefiting both standard and partner/reseller account structures.

    jordan_cook
    jordan_cookContributor ⭐️⭐️⭐️⭐️⭐️

    Allow for free-form JavaScript in formula fieldsNew Idea

    I would love it if Gainsight would allow for the creation of JavaScript (or similar) functions within a formula. This could exist across Horizon Rules Engine, Data Designer, and even in GDM.For example, I would love to be able to count the number of options selected in a multi-select picklist. Right now, it’s nearly impossible to accomplish this within Gainsight if there are a large number of possibilities. But I could accomplish this with one line of code.StringField.split(';').length;No complicated pivots, no crazy case statements that eventually run out of options. Just one simple line of code and we are done.This of course could expand to many, many additional use cases. We could convert dates/times. We could manipulate text fields easily. We could count things, do math on things, and even utilize RegEx. The possibilities are essentially endless. And I suspect that you are already executing code like this with the formulas that are available, but there are heavy guardrails in place by only allowing us to use specific functions.I would also envision a quick formula validator. It wouldn’t have to be complicated - it would simply execute the formula on the fly within the UI. If it results in a syntax error, don’t allow the user to save the formula. Otherwise, just about anything is fair game.This would expand the capabilities of the rules engine by leaps and bounds!