At the moment you can only schedule an Article for future publication. This is a big burden when we want to schedule something we would like an answer on (as you can only mark a solution to a question). Can you please add the functionality to schedule a Question and Discussion so community managers can communicate with their audience as they intend.
We have the Salesforce and inSided integration set up. However, the Idea post Status field is not included in the integration. After interviewing a half dozen of our CSMs to find out what is most important for them to see in salesforce (and Gainsight) with regard to their customers’ community engagement, the single most popular request is to see their customers’ Idea posts and status. I also see our CSMs asking our product team via Slack, all day everyday, for updates on product enhancement status. If we could provide this visibility in Salesforce/Gainsight, it would be a big win. Can you please, please, pretty please add this to the integration? Or let us know if you're working on another way to bring Idea status into the Gainsight app?
Would be super nice, if it would be possible to exclude some users from receiving automatic badges. E. g. moderators & admin, because they’ll be super active in supporting our customers and to answer their support questions, so it makes not really sense to award them with the same manual badges as those for our users.
Having the ability to create events is great, however not being able to send confirmation emails, reminder emails, or a calendar invite to attendee’s isn’t ideal. At least giving them the option to select iCal, Google Cal, etc. on the event attendee confirmation pop-up would be an improvement. Email confirmations and reminders are a must though. Follow up- being able to pull GET requests via the API for Event Attendee’s so we can take our own action when someone signs would be helpful.
Hi all, We have a Developer Forum inside our online community. Since developers mostly participate only in that forum, it would be fair to have a separate leaderboard for them. What do you think?
Our old community platform allowed us to see the count of members who were following each category as well as the list of users. This was useful to understand how many of our customers we were potentially reaching with our announcements/posts, and which customers still needed to be onboarded to community. For example, we launched a new category this year for a new product. We were tracking the number of subscribers on a monthly basis and working to drive that up as a measure of our community engagement success. I’d like to see this data available on our insided community at least for admins.
For inSided community users it is not possible to see (or edit) the email address they set up when they registered. If the email address of the user changes (or it has been years since registration and the user simply doesn’t remember anymore), a moderator needs to make that change or give that information → Usually a user needs to publicly ask to have the own email address changed (which doesn’t look very professional for a community), the conversation needs to move to private messages (in order to keep the information private), the moderator needs to make that change in the Control Panel and confirm it to the user. For both the user and the moderator this is much more hassle than necessary. That’s why we propose that the email address field will be shown in the frontend for users who view their own profile. In addition to that we propose that the email address can be changed in the frontend, just like it is possible for personal information or the password.
Now that MCP access is available in Gainsight CS It would be incredible if we had the ability to authorize this use via Permission Bundles.
It would be great if I could add a new contact from Timeline entries. The contact I am trying to add as an external attendee doesn't exist so now I need to go back to people, add them, then try again (less likely to do that). If I could be prompted to add the contact, fill in any fields required and hit save, then continue doing my timeline entry, it could help ensure proper record keeping
Similar to, but different from, this: Please allow admins to add the Summary section more than once on the same C360 layout (e.g., “Adoption Summary,” “Support Summary,” “Renewal Summary”), similar to sections like Reports that can be added multiple times.ProblemAs we add more data and teams request more 360 insights, we want to keep information organized into logical groups. Today, Summary is the best “at-a-glance” area, but we can only have it once. This leads to either: A single Summary that becomes overcrowded, or Creating additional tabs/sections primarily for layout organization rather than user experience. Impact Cluttered UI: one Summary gets packed, hard to scan More tabs than necessary: CSMs click around to find related insights Higher admin overhead: more layout maintenance as requirements grow Proposed EnhancementAllow admins to add multiple Summary sections to a C360 layout, with: Independent titles per Summary (e.g., “Adoption,” “Support,” “Renewal”) The same widget types supported today in Summary Example Use Case Summary #1: Adoption at-a-glance (usage KPIs, feature adoption, last activity) Summary #2: Support at-a-glance (open cases, escalations, SLA risk) Summary #3: Renewal at-a-glance (days to renewal, renewal stage, risks) Why this mattersThis would reduce “tab sprawl,” keep the C360 experience intuitive, and scale better as our data model grows.
With some of the recent AI tools created with Horizon AI, what are the plans to integrate with Microsoft CoPilot? There’s huge potential to integrate CoPilot into Timeline (similar to Gong integration) and automatically sync all notes, tasks, etc into Timeline, tasks and potentially Cockpit.
Currently, when a playbook is attached to a CTA using the Update CTA Rule Action, the task owners defined within the playbook are not retained. Instead, all tasks are assigned to the CTA owner.After raising a support case and engaging with Gainsight Support and Engineering, it was confirmed that this is the current expected behavior and not a defect. However, this limitation significantly reduces the usefulness of playbooks in automated workflows.Current BehaviorExample:Playbook contains:Task A → Assigned to User ATask B → Assigned to User BRule Action updates a CTA and attaches the playbook.Result:Task A → CTA OwnerTask B → CTA OwnerThe ownership configuration defined within the playbook is ignored.Expected BehaviorWhen a playbook is applied to a CTA through Rules Engine or External API, the tasks within the playbooks should honor the ownership settings and not default to CTA owner.
I learned today that the out-of-the-box Timeline sync requires “External Attendees” to be mapped to “Name” on the Task object in Salesforce. You can’t unmap this, which is unfortunate enough. To make matters worse, the mapping is hard-coded to look at “External Contact ID” on the Company Person and matches that to the SFDC Contact ID. You can’t change this. If we could, we would repoint this mapping to the “External ID” on the Person instead. Why is this so inflexible? Now I have to identify which activities have been failing (not that easy because the GS Error Logs object only goes back 30 days) and create a rule to supplement our Activity Sync when I should just be able to make a simple configuration change in the out-of-box sync. Please consider enhancing this feature.
Background:Prior to the implementation of the new Zendesk widget authentication changes, organizations were able to safely serve different C360 layouts depending on the location. Because the previous integration utilized a centralized connection rather than individual user logins, users could see a compact layout inside the Zendesk widget while maintaining a comprehensive, standard layout when logging into the Gainsight app directly.Following the security and authentication updates post-outage, this split-view capability was lost, forcing a single global layout across both access points. We are requesting a way to restore this flexibility under the new authentication model.What is the requested enhancement?We need the ability to assign and differentiate C360 layouts based on where a user is viewing the data: whether they are accessing Gainsight within the Zendesk sidebar widget or logging into the full Gainsight application.Currently, because the widget authenticates via individual user logins, a user is forced to see the exact same layout in both places. We are requesting that Gainsight introduce a context-aware parameter to the C360 Layout assignment rules: If accessed via Zendesk Widget → Show Widget-Optimized Layout If accessed via Gainsight App directly → Show Standard/Full Layout Why this is needed:An all-or-nothing approach to layout assignment forces a compromise between usability and deep insight: If optimized for Zendesk: The widget looks great and fits the small sidebar, but when those same users log into the main Gainsight platform, they are stuck with an ultra-trimmed "widget view" on a desktop screen, preventing them from doing deeper analysis. If optimized for the Gainsight App: The layout has the depth needed for full platform users, but it becomes completely cluttered and unusable when crammed into the tiny Zendesk sidebar. Business Impact: Support Workflow Efficiency: Support agents need a clean, compact view of high-level health metrics directly inside Zendesk to make rapid decisions on ticket management. However, specialized or higher-tier support agents also need to be able to log into the full Gainsight app to investigate deeper health trends. Data Governance & Licensing: Different tiers of support have different operational needs. A compact view in Zendesk is ideal for front-line agents who do not require full platform access or who have data privacy restrictions limiting what customer data they should see. Without context-aware layouts, we cannot balance a clean user experience in Zendesk with comprehensive data access in the main application. Turnaround time on support tickets is impacted when agents have to constantly fight a UI that isn't optimized for their active workspace.
I read a really good blog that pointed out how much better it can be for gamification metrics like points, reputations and ranks to erode slowly over time. Example: If a member earned a high reputation 24 months ago by posting lots, getting ‘likes’ and best answers, and then goes quiet, their score should start to drop over time. That way it’s clear to members that they’re no longer a voice of authority, a reliable source for help, and a valuable member, at least, not as much as they were 2 years before. It rewards the consistent member, and it helps newbies rise to the top, above the legacy members. Thoughts on this welcome!
Hi Team, Currently, if a call recording/transcript is “split” in the middle of the call, Staircase is only able to pull in the first recording, which can cause anything in the second call to be missed. It would be really helpful if subsequent call recordings would also be picked up, to allow for cases where the recording/transcript may have been stopped for various reasons, such as needing to answer the door, take a break, etc. Thanks in advance for your consideration!
Hi guys, a article is very important for Google but now when you upload a blog the first sentence is used for the meta-description. As far as I know you cannot add, better or change the meta-description which is very important for the performance on Google. I would like to add this, maybe a YOAST-module can be added to the control room? I would like to here if you agree with me of have other solutions.
Like it is possible to customize the layout of the main landing page and custom pages it would be great to be able to customize the user experience in each community section and category.
Today, Staircase AI alert notifications (email and Slack) display a fixed set of metadata fields — specifically Owner, Tier, and Renewal Date. There's no way to customize which fields appear in the notification display.Enhancement request: Allow admins to configure which account-level fields are displayed in Staircase AI alert notifications (email and Slack). Ideally this would be a simple selection from mapped account fields (e.g., Owner, Tier, Renewal Date, ARR/Revenue, CSM, Region, etc.) so each org can tailor the notification to what matters most to their users.Use case: Executive stakeholders who subscribe to churn risk or sentiment drop alerts need revenue context at a glance to prioritize which accounts warrant immediate attention vs. which can be addressed in the normal workflow.
Hi, It is really awesome feature - Quick links. But we can only place them on a main page of the community. Much more time a member spend inside a specific category he/she is interested in. Sadly the only Quick Links we can add there are links to subcategories of that category. We cannot place there links to outer content with tiles like on a main page. Why it could be useful. For instance, we have B2B and B2C customers. We have separated personal account services for two those segments. We also have separated knowledgebases and even stores for two those segments. It would be pretty nice if we could create a total space e.g. for B2B customer within a B2B category on the community. We could place there Quick links to the B2B company account, to the B2B knowledgebase, to the B2B store, to the B2B partners portal and even to place there quick links for B2B actions and promos. So B2B member could drop into a B2B category and then go to any other place of his B2B world right from the category. Too more possible scenario than he/she moves back to the main page to find a useful link. What do you think?
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.