Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6159 Ideas

    spencer_engel
    spencer_engelExpert ⭐️

    Allow SFDC Contacts to be the source of truth in Gainsight instead of Company Person/PersonNew Idea

    I find myself spending a lot of time architecting our Company Person model in such a way that will optimize how our Salesforce contact architecture is setup. The problem, though, is there has never really been a perfect - or even decent - blueprint as to how to do this, especially for customers like us (and my previous org) who use the Account Contact Relationship object. Plus, Gainsight’s arcane “Load to People” action makes updating/upserting to Company Person even harder than it already is, as I’ve already outlined below.  Here are just a few of the common issues I’m constantly playing whack-a-mole with: Duplicate and orphaned records: Contacts that exist in Salesforce but don't cleanly map to a Company Person, or Person records that linger in Gainsight long after they've been deactivated or deleted in Salesforce. Sync headaches: Field mapping mismatches, sync failures, and contacts that show up in one system but not the other. Admin overhead: Time spent building and maintaining rules, connector jobs, and data management plays just to keep contacts in a usable state. End-user confusion: CSMs logging Timeline activities to stale contacts because the Person model hasn't caught up with what Salesforce already knows. I presume the initial intent behind the Person object was to make Gainsight CRM-agnostic, which I understand. But let’s be realistic here - we know Salesforce still is the predominant CRM, which is reflected in the fact its related list functionality, connectors, etc. are all much more well-developed and high-functioning than other CRM competitors. So why not acknowledge this by allowing Salesforce contacts to be the source of truth for Timeline activities, JO Programs, and more if admins so choose? This would presumably have the added benefit for Gainsight of deflecting a lot of support tickets and cleaner customer data.  The bottom line is contact cleanliness is already a difficult issue for pretty much every business. Forcing customers to use the Person/Company Person model compounds the problem.

    gregory.williamsonContributor ⭐️

    Daily Job Execution Health Monitoring & Team AlertsNew Idea

    Category: CS Platform - Administration & OperationsProduct Area: Rule Engine, Connectors, Data ManagementPriority Level: MediumProblem StatementGainsight administrators currently lack a centralized, automated way to monitor the health of daily job executions (rules, connectors, job chains) and get alerted to failures or anomalies. This forces teams to manually check Gainsight logs or rely on external monitoring solutions to identify failed jobs, partial successes, and aborts.Use CaseOur CS team runs dozens of daily jobs (rules, connectors, job chains) that sync critical customer data and drive automated workflows. When jobs fail or partially succeed, we have no native way to:Get a daily summary of job execution status Identify which jobs failed or ran with errors Surface anomalies automatically (e.g., unexpected abort, sudden failure rate spike) Route findings to the admin team for remediationInstead, we either:Manually check Gainsight execution logs daily (time-consuming) Build custom integrations/scripts to monitor jobs (workaround) Wait for customers to report data discrepancies (reactive, too late)Proposed SolutionAdd a Daily Job Health Dashboard & Alert System to Gainsight CS that:Core Features:Health Score: Automated daily calculation of job execution health (SUCCESS %, with breakdown by PARTIAL_SUCCESS, FAILURE, ABORT) Daily Summary Report: Auto-generated report showing: Overall health score & trend vs. previous day Job status breakdown by type (connectors, rules, chains, data design, programs, etc.) All non-successful jobs (failures, partial successes, aborts) Anomalies (e.g., job that usually succeeds suddenly fails) Recommended remediation actions Team Notifications: Option to email or post reports to Slack/Teams for admin teams Flexible Scheduling: Run daily or on custom schedules Historical Trending: Track health scores over time to identify patterns Filterable by Job Type: Option to focus on specific connectors, rules, or job chainsAdmin Configuration:Define which jobs to monitor Set alert thresholds (e.g., alert if health score drops below 80%) Choose notification channels & recipients Customizable anomaly definitionsExpected BenefitsFaster Issue Detection: Proactive identification of job failures before they impact customers Operational Visibility: Admins can see system health at a glance without manual checking Reduced Troubleshooting Time: Clear identification of failed jobs + suggested next steps Data Quality Assurance: Catch sync failures early, preventing downstream data issues Team Collaboration: Shareable reports keep all stakeholders informedTechnical ConsiderationsCould leverage existing Rule Engine execution logs & connector audit trails Similar to application monitoring/APM patterns (health scoring, anomaly detection) Optional integration with existing Gainsight reporting/dashboardsCommunity QuestionsAre others manually monitoring job health or building custom solutions? What job execution visibility features would be most valuable to your team? Would you use this if it were available?