Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    KromerSxContributor ⭐️⭐️

    Community Event Data in Gainsight ConnectorNew Idea

    The current Gainsight Community Connector is missing crucial event data. We cannot easily see event registrations or attendance in Gainsight CS, which are key indicators of customer engagement and health. This forces us to use manual, inefficient workarounds like CSV imports or custom API integrations, wasting valuable time and resources.This enhancement would provide out-of-the-box data objects for events, registrations, and attendance, allowing us to: Improve CSM Efficiency: Give CSMs a single, real-time view of customer event engagement. Drive Proactive Engagement: Trigger automated workflows (e.g., Journey Orchestrator programs) based on who registers or attends an event. Enable Deeper Insights: Easily build reports to measure event ROI and correlate event participation with customer health metrics. Proposed SolutionWe request that the Gainsight Community Connector be updated to include the following data objects and fields, all of which should be mapped to the Gainsight Person and Company objects: Events: Event Name, Type, Date, URL, Event Platform Event Registrations: Person ID, Company ID, Event ID, Registration Date. Event Attendance: Person ID, Company ID, Event ID, Attendance Status (Attended/No Show). This enhancement would streamline our processes, reduce operational overhead, and empower our teams to more effectively use event data to drive customer success.

    Molly.McQ
    Molly.McQHelper ⭐️

    OOTB AI Tool Utilization InsightsNew Idea

    As Gainsight continues to expand its suite of native AI tools, such as Write with AI, Cheat Sheet, CoPilot, and Staircase, it would be incredibly valuable to include OOTB analytics and insights into the internal adoption of these AI features.Today, admins are often left relying on anecdotal or qualitative feedback from users to understand how (or if) these AI features are being leveraged. However, this user reported data can be inconsistent and limited. Having clear, quantitative insights directly in Gainsight CS would help admins:Evaluate adoption trends of specific AI tools This, and the following point, become increasingly relevant as organizations seek to measure the value of AI tools Identify which AI features are driving engagement or saving time Understand where further training, enablement, or awareness might be needed Track usage over time and by user/team for deeper operational visibilityWhile any reliable OOTB reporting on AI feature-specific usage would be a significant improvement, it would be logical to expand the Gainsight 360 > Feature Usage dataset to include detailed tracking for native AI tool usage. Ideally, each AI capability (Write with AI, Cheat Sheet, CoPilot, etc.) would be broken out as its own enum so admins can view individual adoption rates and trends.It would also be helpful to have the ability to build reports and dashboards using this AI utilization data, and potentially tie it to outcomes like CTA closure rates, timeline activity, or overall productivity metrics.As AI becomes a bigger part of the Gainsight experience, it’s crucial for admins (and their organization) to be able to measure its actual impact and adoption internally. These insights would help teams better understand how their CS teams are engaging with AI, where there may be resistance or untapped value, and how Gainsight’s AI investments are translating into daily usage and efficiency (ROI).