Skip to main content
Question

Churn Signal Reporting in Staircase

  • June 22, 2026
  • 1 reply
  • 0 views

bradley
Forum|alt.badge.img+10

Is there a way in Staircase to do more historical reporting? My use case is understanding the time between signal detection and resolution, as well as understanding if that resulted in a deflection/save (shout out to ​@dcassidy’s post here: 

).

This is less for CSMs day to day and more for business reporting, but it might still be useful for CSMs to know. 

In theory, you could write the events to Gainsight CS if you also have that tool, but it’s sort of unclear how that would work. It looks like you just write to a field, which implies you just overwrite a field constantly, rather than creating event records. So then you write THAT value to some time series data...but that seems to get messy.

1 reply

bradybluhm
Forum|alt.badge.img+11
  • Gainsight Employee ⭐️⭐️
  • June 23, 2026

Agree, that does get messy. I do agree that Gainsight CS is the ideal space for the historical tracking to happen, but the field writing today is limited. One thing that should make this a lot easier is when we bring the full Event table into Gainsight instead of just the last event date. 

Until then, the event table in Staircase is a pretty solid place to start today. I definitely love the idea of tracking a Save and am going to take that to the team. Today, it would be manual to check your renewals for previous churn risk or churn notifications to see which came in.  The MCP or Ask Staircase could analyze the story today. But yes, tracking over time is really important and is definitely on my mind.