Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6160 Ideas

    darkknight
    darkknightExpert ⭐️

    CTAs and Success Plans - Prompt user with option to auto-close parent when all child entities are completed.Open

    Having the nested structure of SP, CTA, Task is useful - but it can also be very unwieldy for the end user. More often than not they forget that when they close out their last task in a CTA they have to also close the CTA (Yes, the “quick action” button is there, but only useful when the CTA should be “Closed Success”) and when they complete the last CTA in a Success Plan, they still have to go close the success plan.This results in a very cluttered set of cockpits and an administrative and an enablement nightmare, as well as users saying “Gainsight sure is a click-heavy tool.” (Direct quote) Let’s make this easier shall we?When a user completes the last objective in a Success Plan or the last Task in a CTA, the system should prompt the user giving them the option to auto-close the Success Plan or the CTA, respectively.And when it’s the last Task in the last CTA, carry that option upward to the SP level as well.Sure, having the ability to close CTAs and SPs via Rules Engine is nice, but admins should not have to shoulder the burden of creating and maintain rules to manage such a logical use case that should be programmatically possible within the platform. I’m getting pressure to consider a more admin- and user-friendly platform, and I really don’t want to go that route.  Lets please make this experience easier to manage for all concerned. 

    jenlpro
    jenlproHelper ⭐️

    AI Cheat Sheet for Gainsight Home/Portfolio SummaryNew Idea

    AI Cheat Sheet has proven beneficial for many customers in its current state where it lives on the C/R360. However, as teams are continuing to look for efficiency gains using AI, it seems like a missed opportunity for Gainsight to not roll Cheat Sheet up to a portfolio-level/book-of-business summary. My vision for this would be the following:Gainsight Home AI Cheat Sheet Widget - using the same filters applied to the user’s Home page, AI Cheat Sheet would refresh with a portfolio-level summary, surfacing the most critical, need-to-know information for a user daily right on their home page. As a CSM, I might want to know the top 5 biggest risks across my book, renewals upcoming this fiscal quarter, upsell opportunities in flight, calls I have upcoming, action items I have coming due, and any key contact changes from my book. This would be useful to ICs, as well as to leaders for an AI-powered summary of where they should focus their time. AI Cheat Sheet <> Copilot parity - if cheat sheet is able to use Copilot data sources & training data (key definitions) for additional context, portfolio summaries would be further improved. We could give more insight into what risk looks like for each account, how to prioritize results, etc. so that a portfolio-level cheat sheet wouldn’t be too big to be useful.I’d argue that much of what was recommended in the below idea post should be completed before or in tandem with a portfolio-level summary - for this feature to be truly valuable, we need more flexibility to train the AI to our specific business models. If you’re also interested in portfolio-level summaries on Gainsight Home, I recommend upvoting this post as well.  

    alizee
    alizeeVIP ⭐️⭐️⭐️⭐️⭐️

    Support ISO 8601 date format (and others) in JO emails embedded reports date fieldsNew Idea

    I’m working on a digital engagement journey (JO) which contains an embedded report in an email with a report that contains date fields.Everything’s fine when building. It displays per our locale preferences. And come email testing time. The date is displayed in US format in the email: mm/DD/yyyy. Needless to say that:The US format is NOT universal (it is used by a vast minority of countries) dd/MM/yyyy seems to be used across the majority of countries yyyy/MM/dd (and variants with hyphens) is the most universally understandable format, and happens to be, in its hyphenated format, the INTERNATIONAL STANDARD (ISO 8601) The US format is problematic whenever the day (dd) ranges from calendar day 1-12 (which can be confused with the month (mm)). How do you know what day and month the following date really is: 03/04/2026 ? Is it the 3rd of April or the 4th of March? So we have a product that forces the date format of a minority into reports that are embedded in JO emails. I am puzzled by the approach to default to a non-universal format.But more importantly, the product needs to be upgraded to support the majority of this planet.Allow us to choose date formatting in Reports that are embedded in emails. This is not a nice to have. It is a must have to communicate effectively with our customers, wherever they are, and without imposing a confusing date format onto them. If that cannot be done, the default MUST be the international standard. Not the minority format.