Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    5994 Ideas

    pfpsimoesContributor ⭐️

    Timeline - Bulk Update of Associated RecordsNew Idea

    Problem StatementCurrently, updating associated records (such as Contacts/Attendees or related records like CTAs) on Gainsight Timeline activities must be done individually. When a CSM needs to clean up data, link multiple historical meetings or emails to a newly created CTA, or update associations after an account transition, they have to manually open each Timeline entry. This process is highly tedious, time-consuming, and acts as a barrier to maintaining clean data hygiene. Proposed SolutionIntroduce a multi-select checkbox capability directly in the Timeline list view, accompanied by a bulk action toolbar. Multi-Select Functionality: Allow users to check multiple Timeline entries simultaneously from the main view. Bulk Action Menu: Provide a "Manage Associations" or "Bulk Update" button once multiple entries are selected. Association Modal: Open a modal that allows users to: Add a specific record e.g., link a single CTA or Contact/Attendee to all selected activities. Remove an existing association across the selected entries. Replace a current association with a new one Business Value & Impact Massive Time Savings: Reduces administrative overhead for front-line CSMs, freeing up hours previously spent on manual data entry. Improved Data Hygiene: Encourages accurate data tracking by making it frictionless to link Timeline activities to relevant Gainsight objects. Enhanced Reporting Accuracy: Ensures that CTAs, Success Plans, and Opportunities reflect a complete, accurate history of customer interactions, leading to more reliable executive reporting and healthier customer health scores.

    darkknight
    darkknightExpert ⭐️

    CS: Give Admins Explicit Control Over Gainsight CS MCP Data Scope and ContextNew Idea

    ​I attempted to post this to the comments thread on this post, but I feel it warrants its own idea post.After reviewing the June 2026 on-demand release notes for both MCP enhancements, I want to respectfully share some honest concerns because, based on what I’m reading, I think both designs seem to share the same structural problem.THE CORE ISSUEThe release notes describe this directly:"Existing reports now serve as a knowledge layer for Gainsight CS MCP" because "reports encode your organization's terminology."There's an important distinction here: a knowledge layer describes what exists. A semantic layer — what's actually needed to ground an LLM — governs what data means, and who can see it. Reports provide the former. This design, however, assumes to provide the latter. FEATURE 1: QUERY USING EXISTING REPORTSWhat the docs appear confirmMCP searches reports you have access to, matching on names, descriptions, and filter logic Once a report is identified, MCP can dynamically: incorporate fields not in the report, add/modify/remove unlocked filters Only MDA-connection reports are included (SFDC and external connections excluded) Only reports run in the last 90 days qualify Reports without meaningful names or descriptions may not surface at allWhy this creates a potential governance riskThe report isn't a boundary — it's a discovery hint. Because MCP can add fields and strip unlocked filters at query time, a deliberately narrow report becomes an unscoped query template. Locked filters are honored (a real control worth acknowledging), but locked/unlocked filter status was designed for usability, not as a security perimeter. Few orgs have audited this with "an LLM can remove unlocked filters" in mind. Data and metadata hygiene becomes a functional dependency. Report naming, descriptions, field selections and filter quality now directly determine AI accuracy. In environments with reporting sprawl — inconsistent naming, legacy artifacts, overlapping definitions or (heaven forbid) self-service reporting access — the matching surface becomes both unpredictable and high-maintenance. The 90-day heuristic is a poor proxy for curation quality. Frequently run doesn't mean accurate.  QBR and annual planning reports — often the most carefully curated assets — can fall out of scope. What counts as a "run" is also undefined in the docs (dashboard render? scheduled export? any user?), making the effective discovery surface hard to predict. Cross-team report access is additive, not clarifying. Different teams may hold reports built with different filter logic, field selections, and naming conventions. MCP matching across that surface doesn't neutralize those differences — it inherits them.FEATURE 2: QUERY YOUR PORTFOLIO DATAWhat the docs appear to confirmPortfolio scope is determined exclusively from Gainsight Home filters No other Gainsight surface or configuration is read At least one Home filter must be configured — or the feature doesn't workWhy this creates a potential governance riskFilter state is invisible in the query interface. Results change silently when Home filters change, with no documented indication to the user that a filter is shaping the response False negatives are a design outcome, not a bug. Relevant accounts outside the current filter simply don't appear. Not every team uses Gainsight Home. For those that don't, the feature is inert. A UI personalization preference is not a book-of-business definition. Using Home filter state as the ownership model is a fragile abstraction for anything downstream that matters.BOTH FEATURES CAN FAIL IN OPPOSITE WAYS — FOR THE SAME REASON  In both cases, admins have no surface to adjust the behavior to their environment. ADDITIONAL POTENTIAL GAPS WORTH FLAGGINGDerived field behavior under dynamic modification is undocumented. In-report formula fields exist only at render time. What happens when MCP modifies the report's logic first is unclear. Data Designer outputs that overlap with base fields have no documented precedence model. Associated record resolution is an open question. Associated Record WHOID/WHATID lookup relationships aren't consistently resolved even across core Gainsight features today. How MCP would handle this when those objects become relevant is undefined.  Absence of inclusion on a Gainsight report is not evidence of unimportance.It's often evidence of the opposite — the analysis mattered enough to do properly (or with broader visibility) which meant doing it outside Gainsight. GS data is exported and surfaced in a BI tool because Gainsight's reporting layer couldn't handle the logic required. Those are often the highest-stakes analyses: compliance rates, portfolio-level KPIs, multi-source metrics. No Gainsight report exists precisely because the answer required something more capable. The MCP's discovery model inverts this. It treats a Gainsight report as the signal of relevance. So the analyses your org trusts most — the ones sophisticated enough to require a BI tool — are systematically invisible to it, while simpler, natively-built reports qualify.No audit trail. Neither the release notes nor the admin guide indicates who to know which report was matched, or what filter/field modifications MCP applied to produce a given answer. The tool surfaces changes outside admin change management. This release alone requires users to disconnect/reconnect (Claude) or an admin app refresh (ChatGPT). MCP capabilities shift between releases, outside any change process the admin controls.And these are just the things that came to mind for me. WHAT'S ACTUALLY NEEDEDThe release notes describe, at a high level, what each feature does — reports are matched on names, descriptions, and filter logic; locked filters are honored; only MDA-sourced reports run in the last 90 days qualify. However, it falls short on important details like how matches are ranked when multiple reports qualify, what counts as a "run," and how filter modification decisions are made at query time.Admins are being asked to govern a surface they can observe but neither directly affect nor predict.What's needed is a purpose-built MCP configuration layer where admins can:→ Explicitly define which objects and fields are exposed→ Attach business meaning to fields — definitions, context, caveats→ Designate authoritative sources (Data Designer or otherwise) rather than inheriting whatever reportsexist→ Declare ownership logic directly, rather than inheriting Home filter state→ Decouple AI context from UI state and report library condition entirelyThe MCP Server has real potential; however until admins can explicitly define context and tune it to our own unique business requirements — rather than inherit it from artifacts that require  that business context to understand and interpret — the orgs with the most mature and customized environments are the ones who will trust it the least.​

    darkknight
    darkknightExpert ⭐️

    CS: X-ORG 2.0 - Admins need ability to deselect dependenciesNew Idea

    I don’t know if there is an idea out here for this already or not, but admins need the ability to deselect dependencies when creating an X-Org 2.0 migration bundle because the scope of the default dependency generator is too broad. As an example, I created two Playbooks associated with a single CTA Type and two Success Plan templates associated with a single Success Plan template. Nothing wild, no custom fields, or anything.The Migration tool identifies 128 dependencies including CTA Types and Success Plan Types that are unrelated to any of these that I am attempting to migrate (including ones that are INACTIVE in my sandbox), in addition to other fields under Company, Call to Action, Task, etc. that did not require/have any changes made to them as part of the generation of these assets. I understand Gainsight is trying to ensure that any dependent assets that may be different/have been adjusted as part of the process are carried over, but this control needs to be given to the admin to determine which dependencies are relevant and which aren’t.For many of us, our Sandboxes are not necessarily 1:1 matches to Production.  We often use them as “scratch pads” for testing new features, processes, etc so some of the dependencies the migration tool automatically selects could contain values/components that are not intended for promotion to production.We need more granular control over it. --------Success Plan Template I’m trying to migrate, under the “Extend Product Onboarding” Success Plan type: Migration dependencies include irrelevant SP Types: Including ones that are deactivated:Which it does attempt to insert, since it does not exist in my Production environment:  And then attempted updates/insertions to DA Picklists which the logs don’t even define to which picklist they are related to forcing me to try and deduce it but also are either not different between Sandbox and Production and is unclear why they are attempting to update OR are, again, values related to deactivated assets:  

    t.nelsonContributor ⭐️

    Enhance the Home Page Calendar Widget: Expanded History & Configurable Company AssignmentNew Idea

    I'd like to suggest two enhancements to the Home Page Calendar widget that would improve usability and data consistency for administrators.1. Extend Calendar History Beyond the Rolling One-Month WindowCurrently, the calendar only allows users to navigate back approximately one month. It would be helpful to allow users to access older meetings directly from the calendar widget without relying on other navigation methods. This would make it much easier to review historical customer interactions, update meeting records, and perform administrative tasks for meetings that occurred more than a month ago.2. Allow Administrators to Configure the Default Company AssignmentToday, the calendar assigns the Company on a meeting based on its current default logic. We'd like administrators to have the ability to configure this behavior so the default Company is the Company associated with the Person on the meeting.This is especially important for organizations using the Gong connector. Gong meeting synchronization depends on the Company assignment being consistent across both platforms. When the Calendar widget assigns a different Company than Gong, it can create inconsistencies that require manual correction and complicate reporting and meeting management.Giving administrators control over the default Company assignment would: Reduce manual cleanup after meetings are logged. Improve consistency between Gainsight and Gong. Increase confidence in meeting-related reporting and customer activity data. Better support organizations with complex account hierarchies or multiple Company records associated with the same contacts. These enhancements would improve both the end-user experience and administrative efficiency for teams that rely heavily on the Home Page Calendar and Gong integration.

    LizzieContributor ⭐️⭐️

    Watchparty / live chat functionality in eventsNew Idea

    Hello everyone, We have several key product events that happen throughout the year. These are great ways to bring our community together to watch the live event and enable members to provide instant commentary, as well as speak more casually to other members.  Currently this is very hard to do, we share the live stream (usually a Youtube embedded video) in the community post or in the event page. But, without refreshing the page each time there is comment and scrolling to re-find your place, it is hard to keep the conversation alive.  It would be fantastic to have more capabilities within Events (and possibly other boards), enabling the ability to build something that can then encourage more conversation after the event (as well as before).  I’d like to see the live stream video, and the comments on the side (open to other ideas), but this prevents having to keep scrolling to the top of the thread list to watch the video.  In addition, the option to add polls (with the ability to make them anonymous or only who has responded visible to admins), surveys or highlight questions throughout the event would be also be helpful (especially if you are trying to gauge how well the announcements are going or alternative if a question is popular).  If you are also looking for something similar or have any current workarounds please do share, I’d love to hear any idea. Thanks so much. 

    lyndarContributor ⭐️

    Granular & bulk subscription management (Resources, sub-boards, and tags)Open

    The ProblemManaging content subscriptions is currently high-friction and restrictive. Limited scope: Users cannot subscribe directly to the Resources Board or its specific sub-boards, only to discussions and events. Click fatigue: Users must navigate to every individual page to hit "Subscribe," making onboarding or updating preferences tedious. No topical subscriptions: There is no way to follow specific Tags across the community. Proposed Solution Expand subscription scope: Enable full subscription capabilities for the Resources Board, including all nested sub-boards and resource categories. Bulk subscription preference center: Create a centralized "one-click" subscription overlay or page. When a user clicks subscribe, present them with a clean table of checkboxes so they can opt into multiple categories, boards, and sub-boards en masse. Subscribe to tags: Allow users to follow specific tags (e.g., #ProductUpdates or #BestPractices) to receive notifications whenever that tag is used community-wide. Value & Impact Higher content adoption: Users can easily follow high-value Resource documentation, driving self-service success. Improved retention: A bulk-subscription center reduces setup friction, ensuring users opt into the content they care about immediately. Personalization: Tag subscriptions allow users to curate a hyper-relevant notification feed based on topics rather than rigid folder structures.