Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6160 Ideas

    bradybluhm
    bradybluhmGainsight Employee ⭐️⭐️

    Simple Journeys access at CSM LevelReleased

     As a CSM / CS Leader, I want access to the new Simple Journeys feature for my book of business so that I can more easily communicate with my entire book of Customers. RequirementsAccess would need to be limited to only the Companies and Contacts to which a user is associated as their [(CSM) - (CS Leader) - (AM - Sales) - (PM - Product)] Tokenized email capabilities (JO Simple Programs, essentially) Reporting interface accessible at a user level Opens  Click throughs Bounces Check box field at a Contact level that designates a contact as Do Not Contact using mass communications. GS Admin ability to enable or disable the feature in the instance, by segment, by user type. Potential use case of only CS Leaders having access to the tool in an organization. 2.0:  Ability to schedule recurring templates as a user for my customers. Use case: Usage reporting based on customer’s needs and priorities; better usage report = better visibility and better usage over time. ContextCurrently, Simple Journeys is only available for certain admin level roles within Gainsight. A CSM has to be an effective communicator. Currently, I have to manage all of my customer communication at a 1:1 level using Gmail/Outlook I can use GS templates but it is still incredibly manual and tedious and all done outside of Gainsight. The goal of this feature is to truly make Gainsight the software users live out of to empower their customers. Use Cases CSM Send content and communication out to my customers en masse; allowing me to share product insights, best practice content, and other important information to established personas and contacts efficiently across my customer base. Greatly improve both CSM efficiency and efficacy as they increase their ability to communicate and connect with customers. Include reporting capability into the body of the templates and CSMs could easily create a custom usage dashboard for  CS Leader Regional communications about key initiatives, product updates, important/urgent company level comms. Particularly useful if CS Directors play a largely customer facing role (attending EBRs and other meetings, managing escalated risks, etc.) as it can keep them as a more regular face in the relationship. Thought Leadership communication with any customers of a certain type chosen with filterable fields. Renewal Sales Send reports / tables that house usage or renewal information to my customers with a renewal within xx amount of days; more easily automate this process Filter existing customers and contacts to a particular Product, use case, persona type, willingness for advocacy, etc. to find a connection for a potential prospect. Product Manager ​​​​​​​Filter existing customers and contacts to a particular Product, use case, persona type, willingness for advocacy, etc. to reach out to as a potential beta tester of a feature, and do so en masse. Problems Improved/SolvedImprove CSM efficacy by allowing them to think of and execute on how to to better help their customers at scale. Encourage frontline team members to create effective content that can be templatized and used at scale.  Gather campaign data to determine which templates are working most effectively, allowing continued iteration on journeys and workflows to improve the customer experience. Contact cleanliness and management will happen naturally as a result of teammates communication efforts. The proper gathering of personas and needed contacts at a customer will be prioritized because it will be in view regularly.  Possible PX integration to insert a pop-up for my customers into the product as a CSM.

    Drew C.
    Drew C.Helper ⭐️

    Exports and Date Formatting Problems with ExcelReleased

    Excel doesn’t like dates in analytics exports because they are in DD-MM-YYYY format (because, Europe 😎 ). This breaks Excel’s automatic date format recognition for US region customers (and others who use MM-DD-YYYY). Day numbers greater than 12 are displayed as text/general and aren’t properly sortable. This is massively frustrating! For example, there's no way to distinguish between January 8th or August 1st (01-08-2018 vs 08-01-2018). Fortunately, there is an ISO standard for this, https://en.wikipedia.org/wiki/ISO_8601. Unfortunately, Excel doesn’t really like it when using the letter T for concatenating the Date and Time. From what I can find, the generally accepted universal format to use for CSV exports is noted in this stack overflow thread: https://stackoverflow.com/questions/804118/best-timestamp-format-for-csv-excel YYYY-MM-DD hh🇲🇲ss 👈🏻 Edit: Please fix the emojification problem Relevant XKCD: https://xkcd.com/1179/ Ideally, making this change won't have much impact on current users because leading with a four-digit year is what most date parsing tools expect to see anyway. I’ve attached a CSV I used for testing. The date used is October 25, 2018. The “Europe2” example uses October 3, 2018. Here’s what Excel displays for me (US Region Settings): In the interim, I can swap text around using Numbers on my Mac and re-export the CSV. This is in US format. =CONCATENATE(MID(P2,4,2),"-",LEFT(P2,2),RIGHT(P2,14)) This matches the recommended format above and doesn't add text to blank cells: =IF(L2="","",CONCATENATE(MID(L2,7,4),"-",MID(L2,4,2),"-",LEFT(L2,2),RIGHT(L2,9))) I'm going to have to write a script to do it for me.

    sydney.bennett
    sydney.bennettContributor ⭐️⭐️

    Error Notices - Admin Self-HelpNew Idea

    Over the past months, we have run into a few separate issues that required us to create a ticket over topics that I feel should’ve been fixable by us as the admins. My request/improvement is to increase the error notices or the context provided to Admins regarding errors. The first example is regarding uploading an email to Timeline, the subject was the same as another post in the same account’s timeline, giving the very vague error message of “Unknown Error”. Requiring support to have to come in and tell us what that Unknown Error was. The second example, when wanting to set up the Connector for Zendesk to get ticket info into GS. We received multiple jobs failing notices stating "error occurred while fetching object," we had multiple tickets open on the topic, just to find out that Zendesk only allows 50 records per API call. Something that is a clear answer but not communicated to the Admins at all. Lastly, we ran into a major data discrepancy issue with PX data in CS, using the Daily Aggregated data. It is NOT clearly communicated that the data in that record is only stored for 90 days. There should be some sort of clear messaging when using those Daily objects and a date field. The support team, although very kind and responsive, were unable to tell us that this was the issue (a predetermined Gainsight setting that should be easily communicated) for OVER a month. Meaning, we thought that all of our usage data from PX was unreliable for all that time.  And this is just a few examples, there are more that I can come up with if necessary. Even if this means Error Codes that GS Admins have to find and investigate, it would be a huge improvement, saving both that GS admin’s time AND the GS Support team.

    Samuel Brown
    Samuel BrownContributor ⭐️⭐️

    Segment-based component visibility changes should take effect immediatelyNew Idea

    When a component's visibility is configured to target specific segments, changes to a user's segment membership can take over an hour to reflect in what they actually see. This delay makes it impractical to build real-time, segment-driven user journeys.For example, we attempted to build an onboarding flow where verified customers are shown a modal on first visit. Upon completion, we update a profile field via the API, which moves the user into a different segment — at which point the modal should no longer appear. However, because visibility changes aren't applied promptly, the user continues to see the modal long after their segment has changed, effectively trapping them in a loop.This is impractical for us for serveral reasons such as:User experience degradation - Users who should be seeing onboarding content, upsell prompts, or role-specific guidance will instead see stale or irrelevant components. This undermines any personalisation effort and creates a confusing experience. Operational reliability - If we cannot trust segment targeting to update within a reasonable timeframe, it limits the value of segmentation as a feature entirely. We cannot build automated workflows or time-sensitive processes on top of a mechanism with an unpredictable multi-hour delay. Compliance and access control - Depending on the content being served, prolonged access to the wrong segment's components could have implications for data handling obligations, particularly if customer-specific documentation, pricing, or account information is exposed to non-customers.Reducing this propagation time — ideally to near-instant — would unlock segment-based visibility as a tool for building responsive, self-resolving user experiences such as onboarding flows, first-run wizards, and conditional prompts.