Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6159 Ideas

    andybuchanan
    andybuchananContributor ⭐️⭐️⭐️⭐️

    Allow Non-Owners to Edit Specific Fields on Timeline Activities (e.g., Associate to CTA)New Idea

    Currently, permissions for editing a Timeline activity is restricted to the record's owner or you can provide a permission that allows a given user to update all timeline entries (or admin-level overrides), even for fields that are purely organizational/associative rather than content-related such as linking the activity to a Call to Action, Success Plan, or other related record.This creates friction in common cross-functional scenarios where activities are auto-captured via email integration (e.g., Gmail/Outlook sync, Salesforce activity sync) from team members outside the CS org such as Sales, Support, Services, etc. who don't have Gainsight licenses or don't actively use the platform.Example use case:A Sales or Support rep emails a customer, and that email is auto-captured as a Timeline activity via CRM/email sync. As the CSM managing the account, I identify that this interaction is relevant to an active Risk CTA I'm tracking. Today, I have no way to associate that activity to my CTA because I don't own the record even though I'm not attempting to edit the content of the note, just add a relational link.Requested Enhancement:Introduce field-level edit permissions on Timeline activities, separate from full record ownership. Specifically, allow non-owners (with appropriate role/permission) to edit associative fields like "Related CTA," "Related Success Plan," or similar linking fields without requiring ownership or edit rights over the activity's core content (subject, notes, type, etc.).Business Impact:Improves cross-functional visibility by allowing CSMs to build a complete picture of customer engagement across teams, even when those teams don't use Gainsight directly. Reduces manual workarounds (e.g., creating duplicate manual Timeline entries just to attach context to a CTA). Strengthens the reliability of CTA history/audit trails by linking to the original source activity rather than a re-created one. Supports broader adoption of auto-capture integrations, since the value of captured activities increases when CS teams can actually act on them.

    bradley
    bradleyExpert ⭐️

    Improved Action Setup for Horizon RulesOpen

    Hopefully not a repost, though I’m sure I’ve seen similar, and probably made similar. The Setup Action page isn’t great if you have more than three actions:I’m sure I’ve commented already on the criteria getting clipped and the action not having any useful information on it. Here, you can see that the number of additional criteria is barely even visible. The main issue is the workflow. If I ever want to work on one of these 25 other actions, I have to click show more criteria. When I work on the action, save and close it, I’m not even snapped back to the design. I’m just in empty space. See gif below to embark on a delightful journey with me: I’d really like to have more show by default or at the very least when I expand the list, have it stay expanded while I’m on the Actions Page unless I collapse it myself. Part of the reason for this is I’d also really like to see which actions are active, which are not, AND have the ability to toggle actions off without having to go into each action individually.If the actions are all on the same criteria branch, it’s pretty easy to see what is/isn’t active and do the toggling. But for the most part, my actions all have different criteria and, as you can see above, going into each action to toggle it on or off is a nightmare:You have to go through this expand, click, scroll, expand, click, scroll nightmare 25 times. Because of that, and the fact you can’t see if the action you just toggled off is off or not, it’s hard to keep track.Toggling actions on and off is great for testing, but really hard to manage for larger rules. When I wanted to test this rule, I ended up cloning it, and just deleting everything because it was easier :(, and even that was a pain.

    nsimon
    nsimonContributor ⭐️⭐️⭐️⭐️

    Salesforce Activity Sync — Test Run should indicate when related-object filters aren't reflected in the countNew Idea

    Problem:When setting up a Salesforce Activity Sync job (Administration > Timeline > Integrations) that uses a related-object filter (e.g., a lookup object with its own filter condition), the Test Run count can be wildly inflated compared to what actually syncs on the real run — with zero indication in the UI as to why.Example we hit:Job filters: Task Filter (Type = Email, Created Date >= 1/1/2026) + Related Object filter (a custom object's status field IN 5 specific values) Test Run: ~30,000 matching records Real run: only 910 synced Activity log showed 910 successes, 0 failures — no skip reasons for the other ~29,000, since those records were excluded before processing even beganRoot cause (confirmed by Gainsight Support):Test Run only evaluates the base Task Filter layer. It does not apply related-object joins or any filter conditions on those related objects. The real run applies both layers (Task Filter, then join + related-object filter), so only records passing both actually sync. This is expected/by-design behavior today, not a bug — but the gap is invisible until after the real run completes.Feature request:Test Run should either:Apply related-object filters so the count is a true preview of what will sync, or If that's not feasible, surface a clear UI indicator/warning when a job has related-object filters that aren't factored into the Test Run count, so admins aren't caught off guard by a large discrepancy between test and real run volumes.Why it matters:Without this, admins have no reliable way to validate sync scope before running a job live, especially on large orgs where a 30x+ discrepancy can go unnoticed until data is already in Timeline (or conspicuously absent from it).

    Anthati RameshContributor ⭐️

    Increase Character Limit Beyond 256 for String Functions (To String, To Lower, Concat String) in Rules Engine Formula FieldsNew Idea

    Problem StatementIn the Rules Engine, when using formula fields with string manipulation functions such as Concat String, To String, and To Lower, the current character limit is capped at 256 characters. This creates a significant functional limitation when working with rich-text fields (e.g., Comments) that commonly exceed this threshold.Specifically, the following issues arise:Concat String function fails when the concatenated output exceeds 256 characters To String and To Lower functions fail when the source field (e.g., a rich-text Comments field) contains more than 256 characters String formula fields cannot be directly compared with rich-text field types, adding an additional layer of incompatibility There is no viable workaround currently available to handle this use case when field values exceed the 256-character limit  Expected / Desired BehaviorIncrease the character limit for formula field string functions (Concat String, To String, To Lower) to support a minimum of 2,000+ characters or align with standard rich-text field capacity Enable native comparison between formula-generated string fields and rich-text field types within Rules Engine criteria Optionally, provide a dedicated rich-text formula function that handles large text fields without truncation or failure

    darkknight
    darkknightExpert ⭐️

    CS: Allow Journey Analytics Dashboard to be cloned/modified and made privateNew Idea

    While it’s great that this 7-year old request was finally addressed in the latest release, and that OOTB metrics are now available, there are a few things that make the experience less than ideal.For starters, the dashboard was made public by default. No dashboard should ever be made public by default–especially without notice. Admins should control how and when dashboards are rolled out/assigned.  (Side note: This dashboards went live for many customers without notice a few days before the recent update.)   The dashboard may contain irrelevant elements. There are aspects of the pre-built dashboard that may not be applicable to every customer’s environment. For example, we don’t send emails against relationships, therefore the Relationship filter is irrelevant. there are additional dashboard filters that would be relevant to our environment, yet I’m not able to add them.   we don’t use Gainsight for surveys, so those widgets are irrelevant. It would be fine to simply clone the dashboard and make our own customizations to it except….   The Journey Analytics Dashboard cannot be cloned or made private.  I get why you wouldn’t want a system dashboard to be deleted, however as noted in item #2 above, it may not fit every customer’s scenario, so we should be able to Clone the existing dashboard and make our own customizations to it AND... Make the system dashboard Private or assigned to techops@gainsight.com only (like the CSQL system dashboard is).  The workaround for this is to “Give access to specific people” and assign to myself.  This at least hides it from everyone else, but leaves a redundant, unnecessary dashboard in the admin view.