Currently with MCP Integration with Microsoft Copilot studio, we see below limitations -"Fetch recent timeline entry for xxxx company" query does not return recent entries. In the timelines details returned, the fields which are not present in the corresponding activity type are also returned with Null values. The agent should return the fields as per the activity layout. These should be implemented in product so that the users get value out of the integration.@rakesh
Right now in Staircase, a standard team member is only able to see the bodies of communications where they are in the to/cc of the given comm. I want to be able to expose all of the communications for the accounts that they are assigned to as owners, but not ones where they are not.The only option today appears to expose communications on ALL accounts.
I would like to be able to add more ways users can earn points. For example, a daily log in point would be a great way to show consistent dedication to the community platform.
I don’t think this idea has been posted before. Truth is these days a like-only button doesn’t seem enough, and internet users tend to prefer having more options when it comes to reacting to a topic or comment. Perhaps Slack-style is too much for a community forum, but I think LinkedIn has offered a good balance. These are the reactions I see can be quite useful: like, love, support, useful, funny, sad, insightful.
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.
Many times in a query, the number of items in use extends beyond criteria “J”, however, when a dynamic program is live, we cannot see any advanced criteria to the right of “J”. Example below (I needed to check this was N and (O OR P) but needed to take the very risky action of editing and republishing.)Please correct this.
If I understand it correctly, subscribing to a category only sends an email notification for a new topic, but to receive notifications for a reply on that category you need to subscribe to that specific conversation. Our members would like to receive notifications for replies for category subscriptions and have more granular control of that in their settings. Especially our superusers who heavily rely on subscriptions.
Global filters are normally appended to the report's Advanced Logic with an AND, but when they land on a field the report already filters on, they replace that condition rather than add to it — which does not make sense as Global filters are expected to override report filters. This results to data inaccuracy.This isn't ideal for our case, particularly where we need the report filter to stay in effect alongside the global filter.
Request:Expose API usage data as a reportable object in Report Builder, with at minimum:Object queried Call source (connector name, MCP server, custom integration, etc.) User/service account attribution Timestamp and daily/rolling countGainsight's daily REST API limit (50,000 calls) is shared across all consumers — connectors, custom integrations, and now the Gainsight MCP Server. MCP usage is driven by natural-language prompts from end users, so call volume is no longer fully predictable or admin-controlled the way scheduled connector jobs are.In tenants with a large (and growing) user base and existing heavy API consumption from other automations, MCP-driven traffic can push aggregate usage toward the limit with no early warning — and no way to see which source is responsible when it happens.There's no way to see API consumption broken down by object, source, or user inside Gainsight. Admins have no proactive way to monitor, attribute, or forecast usage before hitting the ceiling.Why Report Builder specifically:This lets admins build their own monitoring dashboards and alerts using existing tools, rather than requiring a new dedicated UI — consistent with how other operational data (rule run history, connector job logs) is already surfaced.
We’re looking to leverage Spaces to collaborate with customers on Success Plans. We use the Customer Goals object to track and manage Value (Proposed, Planned, and Deliver) with customers. At the moment, we’re being blocked because we have internal fields on the Customer Goal object that we need to keep hidden. We’d like the ability to collaborate on Customer Goals with customers via Spaces - without exposing fields that should be internal only.
Hi Team,I would like to submit a feature request based on a limitation that has been reported by multiple customers and is impacting their ability to use Health Score effectively within Gainsight PX.BackgroundThe Health Score (also referred to as Product Score) is available under Administration > Attributes and can also be viewed in Account Explorer. However, this attribute is not available as a filter or targeting option in several important areas of the product.Current LimitationAt present, customers cannot use Health Score or Product Score in the following areas: Audience Explorer for creating user or account segments Engagement Audience Rules at the account level Analytics dashboards and reports Email engagement triggers or automation rules Although the score is available in the platform, customers are unable to use it to build audiences, target engagements, or automate workflows.Business ImpactHealth Score is one of the most important indicators customers use to identify accounts that may need attention. Since it cannot be used as a filter or targeting attribute, customers are forced to perform manual work instead of creating automated workflows.One common use case that is currently not possible is: Automatically show an in-app guide when an account's Health Score falls below a defined value. Automatically send an email when an account's Health Score drops below a specified threshold. Build audiences based on different Health Score ranges for proactive customer engagement. Filter analytics to understand the behavior of low-health or high-health accounts. These are common customer success and retention workflows, but they cannot be achieved today because Health Score is not available in audience rules or engagement conditions.Current WorkaroundThe only available workaround is to: Open Account Explorer. Filter accounts using Product Score. Export the results as a CSV file. Upload the CSV as a CSV Segment. Use that segment for engagements. While this works, it requires manual effort every time the data changes. It is not scalable, is not real-time, and prevents customers from creating dynamic audiences and automated engagement journeys.Requested EnhancementPlease make Health Score or Product Score available as a standard filter and targeting attribute in the following areas: Audience Explorer filters Engagement Audience Rules at the account level Analytics filters and dashboards Engagement trigger conditions for both in-app and email engagements Why This Should Be PrioritizedThis request has been raised by multiple customers who want to automate engagement based on account health. Since the Health Score already exists within the PX data model and is visible in Account Explorer, making it available across filtering and targeting experiences would greatly improve its usability and help customers automate important customer success workflows.This enhancement would reduce manual effort, improve customer adoption, and enable proactive engagement based on account health.Please let me know if any additional customer examples or business use cases would be helpful. Thank you for considering this request.Thanks,Bhanu
We are having our team do onboarding via success plans, and we keep finding that there is a lot of information that we would like to exist on the success plan. Some of which is stored in tables and not just one field. We would love it if there was a way to add a tab and add reports associated with the company onto the success plan.
It looks like the “schedule publishing” option doesn’t exist when you create a post in “product updates.” Can this be an added functionality like when you create a new “article”?
Hi there - I see that in this next release, there will be more ability to customize Cheat Sheet sections. That’s all well and good, but what we need is to filter the actual data that’s going into Cheat Sheet. I agree with this idea about adding more data sources into Cheat Sheet, but this idea is strictly related to Timeline entries.Right now, we’re stuck with every Cheat Sheet looking at exactly the last 6 months of all Timeline entries. Our issue is that we automate quite a few milestones (CSM change, Status change, Stage change, etc.), which are helpful in other areas of the product, but are more or less useless when it comes to Cheat Sheet. I’d like to be able to filter out Milestones for Cheat Sheet, but this is not possible. While we’re at it, I’d like to be able to filter on the following: Type (as mentioned above) Milestone Type (just in case we do want to include some milestones Activity Date Custom fields Thanks for considering.
Right now, there is no direct way for Spaces to share content that was sent to a company via Dynamic Programs. I’m sure there are ways you could configure it (Download the email template, store on an internal platform with a public link, add that link to the Space via a note widget) but it’s clunky & doesn’t include any tokenized content that might be specific to a customer.Given the emphasis of Spaces for scaled/digital customers, where most of the communications will often come in a 1:many format, it would be great if Gainsight found a way to include recent Dynamic Program communications that were sent to the company. This could be a toggle at the program level (much like Log to Timeline is) and would let the customer view the email content (much like you can in Timeline with formatted/tokenized info) directly in the Space.Not only does this amp up Spaces as a single source of digital content for the customer, but it also reduces the burden on a Digital CSM. These customers are already receiving the bulk of communications via digital methods & allowing them to view a list of what they were sent & retrieve them as needed would reduce the need on a Digital CSM to answer common questions of “I didn’t get the product email, can you resend?”
It would be great if Gainsight Assist and Playbooks supported multi-version email templates. We are rolling out Gainsight to our Client Success Managers that manage International accounts/clients that speak different languages where this is needed. As a work around, we set up a JO but there are some touch points where this would be helpful. Rather than having multiple individual email templates for each language, or a playbook for each language, we would like to group them.
I’m absolutely loving the new feature where we can log Automated Program activities to our C/R360 so that our CSMs are able to view any automated emails sent out by JO! This has really increased awareness of the programs we have sent, and ensures CSMs aren’t manually sending emails at touch points that are automated for them.One enhancement that would make this feature even more useful is being able to use the Global Timeline to filter to Automated Program and view all Automated Program activities logged across a CSM’s portfolio. For example: we have emails sending to Company Person(s) and being logged at the C360 level each time a new user accesses the product for the first time. Our CSMs would like to see at a glance all messages sent out on some cadence (daily, weekly, whatever), which having a timeline filter for Automated Program across companies & relationships would help with.I do recognize that creating a report that surfaces Timeline Activities where Type = Automated Program and adding it to a dashboard is a workaround, but wanted to raise the idea anyway, as I think it would create a more intuitive user experience for this particular use case & others!
Many community managers need a way to proactively highlight important content without relying solely on homepage banners or featured topics.I'd like to see a native Promotional Pop-up (or Announcement Campaign) feature that allows administrators to display a customizable modal dialog to visitors when they enter the community or specific pages.Examples include:Promoting annual customer conferences (such as Ignite) Announcing product launches or major releases Highlighting webinars and live events Driving awareness of new documentation or training Sharing important service announcements Welcoming first-time visitorsDesired functionalityAdministrators should be able to configure:Rich text editor with images and branding Primary and secondary call-to-action buttons Display delay (for example, after 2–5 seconds) Frequency controls Once per session Once per day Once per week Until dismissed Page targeting Homepage only Specific product pages Knowledge Base Forums Entire community Audience targeting using Segments Start and end dates Mobile-responsive layout Optional analytics showing: Impressions Dismissals Click-through rate Conversions Today, many communities have to build this functionality using custom HTML/CSS/JavaScript widgets, which requires development effort and ongoing maintenance. A native solution would make it much easier for community managers to launch professional announcement campaigns without writing code.This would complement existing Topic Banners and Featured Topics by providing a more attention-grabbing way to communicate high-priority announcements while giving administrators fine-grained control over when and where they appear.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.