Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    Molly.McQ
    Molly.McQHelper ⭐️

    Expanded Filtering Options for Targeted Slack InsightsNew Idea

    Our team is in need of the ability to filter insights delivered via Slack by data that is not available via the existing OOTB filters within theStaircase AI notification settings (i.e.,Team or Manager).While Staircase currently supports pushing events, insights, and AI summaries to a dedicated Slack channel, it is not currently possible to filter by CS Team or Manager- fields that, in our org, exist as subfields of the Company-based CSM data. Filters are available for User, Account, tier, etc., but these options are not sustainable for us long term- account ownership can change frequently (within and across teams), new users and accounts are regularly added, and most of our teams support customers across multiple tiers.Our primary use case is to surface team-specific insights in their respective Slack channels, rather than funneling all insights into a single centralized channel that team leads must manually sift through. This approach significantly reduces visibility and undermines the value of real-time alerts.While Staircase does offer a default filter for Owner, this only captures a portion of our team structure and does not reflect how our CS org is organized. In our instance, Team and Manager are subfields within the Company > CSM data object. These fields provide a more accurate representation of our internal setup and would serve as a much better foundation for targeted insight configuration/delivery.Ideally, we’d like the ability to filter Slack notifications using these existing Team or Manager fields, rather than relying on the OOTB filters, which don’t meet our specific use case. Essentially, having greater control of these OOTB filters would be key to improving our ability to filter notifications as desired. This would reduce noise, improve clarity, and eliminate the need for ongoing manual filter updates as team structures evolve (or whatever other filters an admin would like to utilize beyond those currently offered OOTB).While I’ve referenced the Team and Manager fields as ideal examples based on our setup and use case, the broader need is for greater flexibility and control over which fields can be used to filter Staircase based Slack notifications- particularly fields that are not currently available OOTB. This enhancement would allow us to operationalize insights more effectively (in a way that is aligned with our internal team hierarchy), improving both visibility and efficiency across the board.

    Molly.McQ
    Molly.McQHelper ⭐️

    Filter Team Effort Criteria by Customer TierNew Idea

    We're requesting Staircase functionality that enables admin users to filter and analyze Team Effort metrics (e.g., email effort in minutes, chat effort in minutes, ticket effort in minutes, etc.) by customer tier or segment.As we know, not all customers are the same. Different tiers of customers can have varying needs, expectations, and engagement models. For example, a digital or tech-touch customer may require more (or less) time and effort per interaction due to limited historical context, lack of a dedicated CSM, or simply differing expectations. In contrast, strategic, high-touch accounts typically have dedicated CSMs who are deeply familiar with the account and are, therefore, generally able to work more efficiently and strategically.A uniform approach to measuring effort can lead to misinterpretation of resource utilization and team performance. In comparison, filtering by tier allows for more accurate benchmarking, smarter resourcing decisions, and clearer operational insights. Ultimately, customer needs and expectations can vary greatly and our evaluation tools should reflect that reality.This variability in customer needs and CSM familiarity/expectations creates meaningful differences in how we internally define and measure “effort.” A single benchmark across all customers fails to account for the nuance in how different types of accounts should be served.To address this, we recommend enabling filtering and segmentation of team effort data, broken out by interaction type (e.g., email, chat, tickets), based on customer tier, segment, or other relevant classifications/filters. This functionality would allow Staircase users to evaluate effort in context and ensure teams are assessed accurately based on the customer profiles they support.Here are some key benefits that come to mind, but I am sure there are more to consider:Improved clarity on how effort varies across customer types more equitable and informed performance evaluation of CSMs and pooled support teams Better identification of where additional enablement or automation may be needed (especially for digital or low/tech-touch segments) Reinforces a “customer first” approach by aligning effort metrics with actual customer needs.