Skip to main content
New Idea

Enable Global Configuration of Stakeholder Type (Staircase)

Related products:Staircase AI
  • August 14, 2025
  • 2 replies
  • 43 views

Molly.McQ
Forum|alt.badge.img+2

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 environments

In 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 level

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

2 replies

bradybluhm
Forum|alt.badge.img+8
  • Gainsight Employee ⭐️⭐️
  • August 15, 2025

Hey ​@Molly.McQ ! Thanks for this, and I have scanned the entire support ticket thread about this as well.

 

Staircase functionality is never meant to ingest your other AI tools summaries and notes. The fact that Gemini was being added as a customer contact is a bug that I am calling out to engineering to catch and squash. You should not need to manually update these automated stakeholder types across each account because they should never get added in the first place as a stakeholder. I am also asking that we remove gemini@google.com as a contact from all of your customer accounts where it may have appeared. We will do out due diligence for the other meeting capture tools as well (zoom as you call out).

 

We have never and do not plan to ingest other AI tools summaries and notes. Staircase ingests only the transcript and metadata from your meeting/call service provider and then we run our own AI processing, analysis and AI summarization that is tuned for post-sales use cases and best practices. From my pov, ingesting the AI summarization from other tools would only create redundancy as we have all the data we need from the transcript itself and tune our summary process and prompt engineering regularly.

 

We do have the feature request and understand the partner use case that you pointed to with this post: Staircase - Domains Associated to Multiple Accounts. This is something that we would like to solve and that will hit our roadmap in the future.

Is there anything I am missing around the gemini situation and issue you have been having? Or is what I have shared above enough to understand the context and know that we will fix this bug?

@danny_hallgren 


Molly.McQ
Forum|alt.badge.img+2
  • Author
  • Helper ⭐️
  • August 19, 2025

Thanks so much for clarifying this and for reviewing the support thread, ​@bradybluhm! That helps a lot.

It’s good to finally know that Gemini showing up as a Stakeholder was indeed a bug and not intended behavior. I wish that had been identified earlier in the support process, but I appreciate you confirming it here and escalating it to engineering. Glad to hear gemini@google.com will be removed where it appeared and that other tools like Zoom are being double-checked too.

Your explanation about Staircase working directly off transcripts and metadata (rather than other AI summaries) makes sense and clears up the confusion. My main concern was making sure insights weren’t misattributed, so I’m glad to know this will be fixed. Also happy to hear the “domains associated with multiple accounts” request is on the roadmap, as that’s going to be a big help.

Appreciate you closing the loop on this.