Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    CHillTEContributor ⭐️⭐️

    Customer-facing "Enlarge" option for images in Slider Engagement DialogsNew Idea

    We publish a monthly Product Updates Slider Engagement to our customers, and we had a customer request the ability to enlarge the screenshot images in each slide, as they can be quite small images trying to show a sizeable section of an in-app screen. I've attached an example. We advised the customer to right click to open the image in a new tab, and we're aware that we can add a hyperlink to these images to show the screenshot in a separate window if desired.However, I think it would be nice if a customer viewing our Engagements had the option to hover and/or click and choose to show a larger version of the image, without leaving the Engagement and our app, perhaps in a pop-in modal on top of the engagement. This could be a setting to toggle on or off in the Engagements Editor, or just a standard feature of images in Engagements.This would be a nice value-add for our Product Updates Slider Engagements, where the images tend to be screenshots, and can be hard to see in the small Engagement dialog. (Note: we wouldn't want to make our Engagements dialogs much bigger, to accommodate larger images, as users on smaller screens would have a much worse experience. Screen-size-responsive dialog sizing would be a great feature add, too!)I did also reach out to Gainsight Support about this, and they suggested I post it here. They also let me know that we would already be able to do this with a Guide-type Engagement, by adding onclick JavaScript directly in the engagement HTML. Unfortunately we prefer Sliders over Guides for this type of update, as the Guide’s true “buttons” make it feel more like “work” for our users to get through, where a slider is more lightweight-looking and easier/more intuitive to click through using the arrows. I should note that if we had this same HTML editability for Sliders, that would also work for what we need to accomplish, but a toggle or setting might be more user-friendly.

    Ashton
    AshtonContributor ⭐️⭐️⭐️⭐️

    Funnel Report Support for Matching Field Logic Across Steps (e.g., Object ID)New Idea

    Subject: Enhancement Request: Funnel Report Support for Matching Field Logic Across Steps (e.g., Case ID)Description:We would like to request an enhancement to the Funnel Report in Gainsight PX that would allow steps in a funnel to be logically linked by a matching field, such as an Object ID, to better reflect user journeys tied to specific objects.Use Case:In our product, users can create and manage multiple objects (called cases) simultaneously. Each case progresses through a defined workflow (e.g., Step 1 → Step 2 → Step 3). However, users often work on multiple cases in parallel, switching between them as needed.Currently, the funnel report tracks user activity across steps without ensuring that those steps are tied to the same object instance. This leads to inaccurate funnel progression data, as a user may complete Step 1 on Case A, Step 2 on Case B, and Step 3 on Case C — which should not count as a valid funnel progression.Proposed Enhancement:Introduce a "Matching Field" configuration option for each funnel step that allows us to specify a field (e.g., Case_id) that must have the same value across all steps in a funnel instance. This would ensure that:Funnel progression is only counted when a user performs all steps on the same object (e.g., the same case). The report can track multiple funnel journeys per user, one per unique matching field value (e.g., one funnel per case).Benefits:Enables accurate tracking of object-specific workflows. Supports more granular analysis of user behavior across multiple concurrent journeys. Aligns funnel reporting with real-world usage patterns in products where users manage multiple entities.Example Configuration:Step 1: Custom Event case_created with attribute case_id Step 2: Custom Event case_updated with attribute case_id Step 3: Custom Event case_closed with attribute case_id Matching Field: case_id (must match across all steps)Thank you for considering this enhancement. We believe this would unlock powerful new use cases for funnel analysis in PX and better support products with object-based workflows.

    bradley
    bradleyExpert ⭐️

    Allow Attachment Tagging on UploadNew Idea

    Tagging is a handy element (though could use some work) of the new Attachments feature. However, the actual implementation of it seems very clunky from a user perspective for a couple of reasons.For one thing, you can’t manage them in bulk, or across customers. This isn’t really what this post is about but it’s only available on the 360s right now meaning it’s only visible one customer at a time. You can only add Tags *after* the file has been uploaded. This is the main issue here. The ask here is simple: Update the Tag workflow to allow file tagging during upload via whatever means the file/link is being added. Why is this important? Consider the function of tags: Reportability and organization. As a user, I might want to add a tag to something so that I can find this more easily. As a business, I might want my users to tag files in a certain way for reporting/KPI purposes. Let’s look at the timeline workflow as an example of this workflow: The great thing about timeline, is you *do not* have to be on the 360 to create one. You could be on a CTA, Success Plan, some non-Attachments tab 360 section, Home, etc.However, you can *only* add a Tag on the Attachments section of the 360s. This means, if you want/need to add a Tag, and you have created a timeline entry on Home, you have to:Create timeline Add Attachment Go back to that customer 360 Go to the attachments tab Find the file Add the Tag(s)Instead of:Create timeline​​​​​​​ Upload Attachment with tagsNot only would this change obviously reduce the steps a user would need to go through, but it would also maintain the usefulness of creating Timeline entries from everywhere or “meet you where you’re at”. This feature does *not* meet you where you’re at, and will be incredibly frustrating for users and probably hamper adoption.For us, adoption of Tags is a critical component of this attachments feature.

    Molly.McQ
    Molly.McQHelper ⭐️

    Add Dashboard Status Options in CSNew Idea

    Currently, any dashboard created in CS is immediately visible to admins or provisioned users. There is no option to mark a dashboard as “Draft” or “Inactive.” The only workaround is adding “WIP” or “DRAFT” in the dashboard title. This does not restrict access, is easy to miss in dropdown menus, and often confuses end users.The alternative is to adjust user permissions or bundles, which is not a good solution. This requires admins to repeatedly edit sharing logic, introduces risk of impacting unintended users or groups, and creates additional work to revert changes later. If forgotten, dashboards remain exposed or inaccessible to the wrong audiences.Other Gainsight objects (such as programs, activities, playbooks, templates, rules, etc.) already support draft, active, and inactive/published statuses. Dashboards are an exception. This inconsistency complicates governance overhead and forces admins into risky workarounds for what should be a simple task.As such, requesting to introduce dashboard statuses such as:Draft - visible only to the creator and admins, hidden from other users Active - (current behavior) visible to provisioned users Inactive - Retained, but hidden until reactivated or deleted This would effectively reduce admin effort and eliminate the need for risky permission/bundle manipulation. In addition, it would:Provide a more consistent lifecycle approach across CS features Prevent unfinished or outdated dashboards from undermining end user trust in reporting Reduces dropdown and search clutter for end users Support improved administration/governance and change management by allowing testing, iteration, and archiving without unintended exposureNOTE: I could have sworn this idea already existed, but our team has been unable to locate it in the community; please merge as appropriate if related idea exists.