Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6266 Ideas

    darkknight
    darkknightExpert ⭐️

    CS AI Tools Management: Extend "Quick Insights" functionality to Copilot/MCP ServerNew Idea

    Report access through the Gainsight CS MCP server is all-or-nothing today. In Administration > AI Settings > AI Tool Management, report_search_tool and fetch_report_data can only be toggled Active or Inactive.The admin has no say in which reports are eligible. I’ve currently got both report tools disabled in my tenant. That’s not a preference — it’s the only option when you can’t scope them. And it costs users real capability, because the MCP tool instructions tell the model to prefer saved reports over dedicated tools, on the reasoning that reports encode the customer’s own business definitions. That’s a lot of trust to place in a library the admin can’t curate.As noted in this post, there are a number of reasons why broad report access could be problematic. Admins need a way to designate which reports are eligible for consideration by Copilot and the MCP ServerA marker already exists“Mark as Quick Insight” was built to designate which reports are fit for consumption through an AI surface. That is exactly the control we need.Today it only applies to Sally in Slack. Sally within Gainsight CS was retired in November 2025. Sally in Slack remains supported, but Gainsight AI Agent in Slack and Copilot are plainly where the product is heading.So Quick Insight is a working flag attached to a legacy surface. Rather than let it age out, repurpose it. Per-report gating already exists here — the report tools branch on a user_accessible flag today. This is a second flag on an existing gate, not new architecture.What I’m asking forRedefine Quick Insight as a general marker meaning “this report is approved for AI surfaces.”  Honor it across Copilot, Gainsight AI Agent in Slack, and Gainsight CS MCP — not just Sally. Add a toggle in Tool Management: “Restrict report tools to Quick Insight reports only.” allowing admins to choose whether or not to leverage this restriction When on, non-approved reports are excluded from both report metadata search and report fetch. When off, behavior is unchanged. Default the toggle off, so nothing changes for existing tenants on release.That gives admins a curated allowlist. We approve the reports that are accurate, stable, and safe. Everything else is invisible to the LLM — without touching report sharing and without disabling report tooling entirely.The restriction has to cover metadata, not just fetchToday’s user_accessible gate in the MCP server report tools stops a report from being run, not from being read. When a report is flagged inaccessible, the model appears to be instructed that its structure “still encodes genuine tenant conventions” — the objects it queries, the lookup chains it traverses, the filter logic it applies, the GSIDs it has resolved — and told to carry those forward.Row data stays permission-bound. Structural knowledge doesn’t. A toggle that only gates fetch would leave unapproved reports still shaping answers.Benefits Improved Accuracy - MCP picks reports by matching your question against report names and descriptions. With hundreds of reports, several will look like plausible matches. A curated set means it’s choosing from reports you’ve vouched for. Consistency - Today the report pool varies by user. Same question, different people, different answers. A shared approved set narrows that. Less prompt effort - Gainsight’s guidance is to spell out your business logic in the prompt. Good reports already encode that logic in their filters, so users write less to get the same result. Predictability - “It draws on this set of reports” is something users can understand and admins can explain. “It searches your entire report library” is not. Trust - This is the one that compounds. Users decide early whether the assistant is reliable. Curated sources make the early answers better, which is when it matters most. Better Admin QOL - Today when someone reports faulty results, you don’t know which of the hundreds of reports produced it. You have to reconstruct what the LLM probably matched on before you can even tell whether it’s a bug, a stale report, or the user misreading the answer. With a curated set, the suspect list is small and you own every report on it. Triage goes from “investigate the library” to “check these reports.”  It also cuts ticket volume at the source, since most of those tickets come from the LLM picking a report nobody maintains.Dependency: make the “Mark as Quick Insight” flag usable at scaleToday a report can only be marked as Quick Insight by opening the individual report itself, which makes curating an allowlist impractical when governing hundreds of reports.Please add Mark as Quick Insight to the row-level settings menu in the report list view. That menu already has Edit Report, Rename Report, Delete Report, Manage Permissions and Enable Add Record. The flag belongs beside them.Bulk select would be better still. The row menu alone makes this workable.One behavior to revisitMarking a report as Quick Insight currently exposes it to all Sally users. If the flag becomes a general AI-surface marker, that blanket exposure should be reconsidered — ideally the flag governs eligibility, with each user’s existing report permissions still applying on top.

    t.nelsonContributor ⭐️

    Make Group Send available throughout Gainsight workflowsNew Idea

    Group Send should be available directly from the places where CSMs identify and manage audiences - not only from a separate workflow. This includes Reports, Dashboards, C360/R360, Cockpit, and other person-based grids across Gainsight.CSMs often use Gainsight to identify a specific group that needs outreach: dormant users, contacts associated with open risk CTAs, stakeholders at accounts with a renewal approaching, or people meeting criteria in a report or dashboard. Once that audience is identified, they should be able to select the relevant people and initiate a Group Send without exporting the list, manually rebuilding it, or navigating away from the workflow.Integrating Group Send throughout the platform would:Turn insights into action at the point they are discovered. Reduce manual list-building and the risk of using an outdated or incorrect audience. Help CSMs maintain relevant, timely communication with contacts across their portfolio. Create a more connected workflow between reporting, customer context, Cockpit actions, and outreach. Improve adoption of Gainsight as the system where CSMs both understand and act on customer data.For example:From a report or dashboard, a CSM could select people who meet a risk or adoption criterion and send an approved, relevant template. From C360/R360, a CSM could email a filtered set of stakeholders without manually locating each person. From Cockpit, a CSM could send outreach to people associated with a set of related CTAs.Any expanded capability should continue to honor permissions, email preferences, recipient limits, and existing template/token requirements. A clear preview of recipients before sending would also be important.Making Group Send available across these workflows would make Gainsight more actionable and reduce the friction between identifying a customer need and communicating with the right people.

    Suiteify AcademyContributor ⭐️

    Feature Request: More Options for Customer Communication Based on Live Event Attendance and Recipient SegmentationNew Idea

    Hello Skilljar team,We would like to submit a second feature request, related to customer communication within Skilljar.Current limitationAt the moment, we can only use the completion state of a course as a trigger for communication, for example in a thank-you email. This is not sufficient for our use case. Not every course has a completion state that fits, and a completion-based trigger does not allow us to reach all relevant learners at the right moment.Our use caseAfter a live event has taken place, we want to:Make the event recording available as the next lesson in the relevant course. Communicate with learners in a way that depends on their participation: Learners who attended the live event should receive a different message than learners who did not attend. Learners who registered but neither attended nor completed the course must also be informed about the recording and should not be excluded. In both cases, every relevant learner needs to be notified about the recording, but the content and tone of the message should reflect whether they took part.What we would like to requestAttendance-based segmentation: The ability to distinguish between registered, attended, and not-attended learners for live events, and to use this as a condition for communication. Additional triggers: Communication triggers beyond course completion, such as a live event being completed, a lesson being published, or a registration status change. Targeting of registrants: The ability to send communication to users who are registered for a course or event but have neither attended nor completed it. Message variants per segment: The ability to create different email content for each segment within the same workflow or campaign.These options would allow us to automate recording distribution reliably, communicate in a more relevant way, and avoid manual follow-up work for each live event.Could you let us know whether any of these options are planned or already available in another form? If there is a workaround, or a related feature request we should follow, please point us to it.Thank you for considering this request.

    Bhanu prasadGainsight Employee ⭐️

    Request to Support Learner Profile Picture Sync Through API and Salesforce IntegrationNew Idea

    Description We would like to request the ability to retrieve learner profile pictures that have already been uploaded to the My Profile section in Skilljar through the Skilljar API and sync them with Salesforce using the existing Salesforce integration or Data Connector.The goal is to make learner profile pictures available to other connected systems without requiring learners or administrators to upload the same image more than once.Business use case We would like to use Skilljar as the central source for learner profile pictures and make this information available in Salesforce.Our intended use case is to generate course completion certificates directly through Salesforce. These certificates would include the learner's profile picture and would also be made available as Apple Wallet passes.Since learners have already uploaded their pictures to their Skilljar profiles, it would be helpful if we could retrieve and reuse those existing images in Salesforce.This would provide a consistent experience for learners and help us avoid asking them to upload their photos again in another system.Current limitations At present, we have identified the following limitations: The Skilljar API (V1 and V2) does not appear to provide a field or dedicated endpoint to retrieve a learner's profile picture. The Salesforce integration does not currently offer a supported field to sync learner profile pictures. The Data Connector does not provide an available field or mapping option for profile pictures. Other learner and course completion details, such as completion date, completion status, certificate code, certificate validation URL, and signup fields, can be synced to Salesforce. However, the learner's profile picture is not included. Because of this limitation, we are unable to use the profile picture already stored in Skilljar when generating certificates through Salesforce.Requested functionality We would appreciate it if the following capabilities could be considered: Make learner profile pictures available through the API: Provide the ability to retrieve a learner's profile picture through the existing student or user object, or through a dedicated API endpoint. Ideally, this could be made available as an image URL or downloadable image content. Support profile picture syncing with Salesforce: Introduce a profile picture field, such as a profile image URL, within the Salesforce integration and Data Connector field mappings. This would allow the image information to be synced to the appropriate Salesforce Contact or custom object field. Maintain the connection with the learner record: Ensure that the retrieved profile picture is associated with the correct learner so that Salesforce can use the image when generating certificates and Apple Wallet passes. Expected benefits Supporting this functionality would provide several benefits: Avoid duplicate uploads: Learners would not need to upload their profile pictures again in Salesforce, reducing the effort required from them. Maintain consistent learner information: Skilljar would remain the central source for profile pictures, helping ensure that the same image is used across connected systems. Support personalised certificates: Salesforce could use the learner's existing profile picture when creating course completion certificates and digital wallet passes. Improve the learner experience: Removing the need for repeated uploads would make the overall process easier and more convenient. Reduce manual work: Administrators would spend less time managing duplicate images and maintaining learner information across multiple platforms. Suggestions for implementation We understand that learner profile pictures are personal information and would like to suggest a few considerations for implementation: Provide secure or time-limited image URLs to ensure that profile pictures are accessible only through authorised access. Support a consistent image format and size, with an option to retrieve a resized version if needed. Return a clear empty or null value when a learner has not uploaded a profile picture. Ensure that profile picture updates in Skilljar can be reflected in Salesforce when the information is synced again. Current workaround Currently, the only available options are to ask learners to upload their profile pictures separately in Salesforce or collect a hosted image URL through a signup field.Both options require additional effort from learners and administrators. They also create duplicate records and make it harder to maintain a consistent profile picture across systems.Since the learner's profile picture is already available in Skilljar, being able to retrieve and sync it directly would be a much better approach.Closing note We would appreciate your team reviewing this request and considering the possibility of making learner profile pictures available through the Skilljar API and Salesforce integration or Data Connector.We believe this enhancement would be valuable for organisations that rely on Skilljar as their primary learning platform and use Salesforce for certificate generation, learner records, and digital credentials.Having this capability would help us make better use of the existing learner information in Skilljar, reduce unnecessary manual work, and provide a more convenient experience for our learners.Thank you for taking the time to review this request. We look forward to your feedback and would appreciate any guidance on whether this functionality could be considered for a future enhancement.

    jean.nairon
    jean.naironExpert ⭐️

    PX on my CSDevelopment

    PX on CS (also known as the Enablement Engine)I would like improved user analytics and product engagement to help drive user growth in my Nxt CS instance. We currently have 700 users in Gainsight CS and we are evolving our processes quickly. Enabling our teams on new process/system changes is critical to the success of our teams.As the PX website states, it enables you to deeply understand what users are doing in your product, collect feedback, and create in-app engagements like walkthroughs and guides to drive onboarding and adoption. That’s exactly what I want for my Gainsight CS and my users. Let me explain further.  Gainsight CS Analytics TodayToday, Gainsight provide the G360 feature to show admins some simple usage data. If you don’t have this in your instance, I recommend talking to your CSM to get access to it. The data in this feature is not very deep. You can see things like page views and how often users are logging into Gainsight. You can also top level feature usage like how often someone goes to the Cockpit, a 360, or the Rule Engine. This is somewhat helpful, but it isn’t deep enough information to be incredibly powerful.  User AdoptionFeature Usage Analytics AskWhat would be incredibly powerful is to see deeper insights on on our Gainsight users so that we can continue to identify areas to improve and build our end-users depth of their usage. For example, I would like the ability to be able to understand: Which users are not only going to the Home page but which dashboards do they use the most? Which dashboards do they not use? Which sections on the 360 are they leveraging the most? Do they spend all their time on the Summary and Cockpit or is it one of the related lists? When they go to the Cockpit, are they using Global Cockpit or the 360 Cockpit the most? And more importantly, which views are they using the most and which ones do they not use? How do user cohorts (brand new users vs seasoned users) compare? Do older users spend more time somewhere different than new users and is there something there that new users are not learning? We measure our user’s satisfaction through surveys and it would be great to be able to correlate usage details to better understand if certain functionality is attributing to better satisfaction.Those are a few of my asks but I think if we are able to marry usage data with end-user surveys and other key details about the users (ex: departments, manager, geo, etc), this information could be incredibly powerful for administrators to drive further adoption and stickiness of our configurations.  End User Enablement TodayToday, we enable our end-users through many of the common ways that other companies are using. Our change management and end-user enablement includes:Training sessions: global virtual meetings and sometimes in-person Knowledge Base: we use a knowledge base (salesforce and sharepoint pages) to store help articles which include GS how tos and CSM processes. This includes both articles, videos, and lots of pictures.  Monthly Email Newsletters: we send out regular emails with updates to Gainsight, processes, and other changes that impact our end-users. Online Chat Message: We further send out regular messages on multiple chat streams to follow-up on new changes and reinforce specific new configurations.  One-on-Ones: and when all the above doesn’t work, we further meet with people to ensure they fully understand the changes and how to apply them in their day. Our current change management efforts require a lot of energy and commitment to continue pushing the changes we are trying to accomplish in our teams. And we are always trying to better understand usage to see where our change management activities didn’t hit the mark. But it’s never enough and has zero automation. Enablement AskWhat would be incredibly power is to use the PX engine to drive user enablement at the point of action. Change management activities over meetings, email, and chat are somewhat effective but often get forgotten and it is very difficult to reinforce behavioural changes. It would be incredibly helpful if we could: Build in-app guides to walk new users through our 360s and other core features with combinations of dialogs, sliders, tooltips, and hotspots. Fully personalize the onboarding experience based on account and user level attributes. We also want welcome videos from our leadership to popup when a user first signs. This creates an amazing new employee onboarding experience within Gainsight. Leverage guides, tooltips, and hotspots to activate usage of new or lesser-known features, new features the moment they are released, and any workflow or business changes. Create highly personalized engagement experiences based on user characteristics such as role, geography, historical product behavior, and more Create Knowledge Center bots with customizable content like how-to articles, CSM checklists, and key business processes. We don’t want this to just be about Gainsight, we want it for all our how to content for our end-users (CSMs, TAMs, Renewals, etc).  Identify and segment out users who aren’t fully utilizing a core feature and target them with personalized tips and guides. Especially for our leaders to help guide them through their critical dashboards.  Survey our customers within the app to get feedback on new features we’ve enabled or key changes.  Integration with other SystemsWe use Nxt in Salesforce (Classic and Lightning) so it would need to work there properly. It is critical that if a user is in Classic and/or switches to Lightning, it has to work there. And possibly, if need be, we’d like to be able to know which user is using which SFDC version. We’re migrating from Classic to Lightning and it would be an amazing bonus if we know who’s logging in where to help enable and push this change as well.  ConclusionThe ability to use PX on our instance of CS is going to be incredibly powerful for us to drive the stickiness of our Gainsight. There is a tremendous amount of shared value here for us to drive our user growth. If we can do this easier and more successfully, our use cases and value will write itself. And most importantly, we need this functionality in the hands of our admins so that we can learn quickly and make adjustments to campaigns quickly. This feature will not scale if we always need a TAM to implement changes.