Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    5961 Ideas

    dcassidy
    dcassidyHelper ⭐️

    Churn Save Event DetectionNew Idea

    I've raised this during Office Hours and wanted to formalize it as an official idea.Staircase already does excellent work surfacing Churn Risk signals, Churn Notifications, Extremely Negative Messages, and Highly Positive Messages - all high-value events that drive action across CS, Sales, and Leadership. I'd like to extend that framework with a discrete "Churn Save" event.The ask: When Staircase detects a customer who was previously flagged at elevated churn risk (or even churn notification) and subsequently shows recovery or renewal signals, surface that as a named, trackable event in the platform.Why it matters:CSM-level: Gives individual contributors concrete, timestamped evidence of impact to bring into performance conversations and 1:1s — no manual documentation required. CS Org-level: Enables CS leadership to aggregate and report Churn Saves as a measurable outcome alongside ARR retained, rather than relying on anecdotal accounts. Executive-level: Provides ELT and C-Suite a defensible, data-backed metric for CS ROI — particularly relevant given current pressure on every org to demonstrate clear business value.This builds naturally on existing Staircase detection logic and would give the platform a closed-loop view of the churn lifecycle: risk identified → intervention triggered → save confirmed.Interested to hear whether others are tracking Churn Saves manually today and what signals you'd want Staircase to use to confirm a save event. 

    darkknight
    darkknightExpert ⭐️

    CS - Allow Summary section multiple times on a single C360 layoutNew Idea

    Similar to, but different from, this:  Please allow admins to add the Summary section more than once on the same C360 layout (e.g., “Adoption Summary,” “Support Summary,” “Renewal Summary”), similar to sections like Reports that can be added multiple times.ProblemAs we add more data and teams request more 360 insights, we want to keep information organized into logical groups. Today, Summary is the best “at-a-glance” area, but we can only have it once. This leads to either: A single Summary that becomes overcrowded, or Creating additional tabs/sections primarily for layout organization rather than user experience. Impact Cluttered UI: one Summary gets packed, hard to scan More tabs than necessary: CSMs click around to find related insights Higher admin overhead: more layout maintenance as requirements grow Proposed EnhancementAllow admins to add multiple Summary sections to a C360 layout, with: Independent titles per Summary (e.g., “Adoption,” “Support,” “Renewal”) The same widget types supported today in Summary Example Use Case Summary #1: Adoption at-a-glance (usage KPIs, feature adoption, last activity) Summary #2: Support at-a-glance (open cases, escalations, SLA risk) Summary #3: Renewal at-a-glance (days to renewal, renewal stage, risks) Why this mattersThis would reduce “tab sprawl,” keep the C360 experience intuitive, and scale better as our data model grows.

    kstim
    kstimHelper ⭐️⭐️

    Feature Request: Differentiate C360 Layouts Based on Access Context (Zendesk Widget Context vs. Gainsight App Login)New Idea

    Background:Prior to the implementation of the new Zendesk widget authentication changes, organizations were able to safely serve different C360 layouts depending on the location. Because the previous integration utilized a centralized connection rather than individual user logins, users could see a compact layout inside the Zendesk widget while maintaining a comprehensive, standard layout when logging into the Gainsight app directly.Following the security and authentication updates post-outage, this split-view capability was lost, forcing a single global layout across both access points. We are requesting a way to restore this flexibility under the new authentication model.What is the requested enhancement?We need the ability to assign and differentiate C360 layouts based on where a user is viewing the data: whether they are accessing Gainsight within the Zendesk sidebar widget or logging into the full Gainsight application.Currently, because the widget authenticates via individual user logins, a user is forced to see the exact same layout in both places. We are requesting that Gainsight introduce a context-aware parameter to the C360 Layout assignment rules: If accessed via Zendesk Widget  → Show Widget-Optimized Layout If accessed via Gainsight App directly → Show Standard/Full Layout Why this is needed:An all-or-nothing approach to layout assignment forces a compromise between usability and deep insight: If optimized for Zendesk: The widget looks great and fits the small sidebar, but when those same users log into the main Gainsight platform, they are stuck with an ultra-trimmed "widget view" on a desktop screen, preventing them from doing deeper analysis. If optimized for the Gainsight App: The layout has the depth needed for full platform users, but it becomes completely cluttered and unusable when crammed into the tiny Zendesk sidebar. Business Impact: Support Workflow Efficiency: Support agents need a clean, compact view of high-level health metrics directly inside Zendesk to make rapid decisions on ticket management. However, specialized or higher-tier support agents also need to be able to log into the full Gainsight app to investigate deeper health trends. Data Governance & Licensing: Different tiers of support have different operational needs. A compact view in Zendesk is ideal for front-line agents who do not require full platform access or who have data privacy restrictions limiting what customer data they should see. Without context-aware layouts, we cannot balance a clean user experience in Zendesk with comprehensive data access in the main application. Turnaround time on support tickets is impacted when agents have to constantly fight a UI that isn't optimized for their active workspace.