What's the right way to share customer health data with reps without overwhelming them with dashboards?

The governing principle is rep-time budget: an AE will spend at most 30 seconds per account per week on health data. Design every surface to that budget. If your dashboard takes 45 seconds to load you have already lost; if your alert needs a click to reveal the reason you have already lost.

The job is to push one number, one reason, one action into the tools the rep already opens, and to make the system falsifiable enough that reps choose to trust it.

Surfaces, in order of attention captured.

CRM field on the Account record. Salesforce: Customer_Health__c picklist (Green/Yellow/Red), Health_Reason__c short text, Health_AsOf__c timestamp. HubSpot: three calculated properties with the same names.

Field mechanics: https://help.salesforce.com/s/articleView?id=sf.formula_overview.htm and https://knowledge.hubspot.com/properties/use-calculated-properties.

Slack delta alert on state transitions only, never on recalculation. Use Slack's workflow builder (https://slack.com/help/articles/360035692513-Guide-to-Workflow-Builder) to route to the AE pod's private channel. Canonical format: '[Acme] Yellow->Red. Logins down 41% in 14 days. Action: book a 30-min usage review with their admin this week.'

Monday 7am per-rep digest, ranked by expected revenue at risk this quarter, top five red and top five expansion-ready, no more. The CTA pattern is Gainsight's (https://support.gainsight.com/Gainsight_NXT/Cockpit_and_CTAs) but you do not need Gainsight to ship it - a Snowflake query plus a Customer.io email will suffice for the first 18 months.

QBR rollup. One 2x2 slide (health x ARR) pre-populated by RevOps the Friday before each QBR. Reps do not build it; they review it.

Bear Case - four failure modes with detectable pre-mortem signals.

(1) Score gaming. CSMs nudge inputs to keep accounts yellow because red triggers manager escalation. Trigger: >15% of yellow accounts have manually edited usage fields in a 30-day window.

Mitigation: derive every input from system-of-record telemetry via Snowflake (https://docs.snowflake.com/en/user-guide/data-time-travel) or Segment (https://segment.com/docs/connections/sources/) and lock the input fields.

(2) Data lag breaks trust. Stale telemetry produces a 'red' alert minutes after a great call and every future alert is discounted. Trigger: median Health_AsOf__c freshness >36h for two consecutive weeks. Mitigation: suppress surfaces when telemetry is older than 48h and publish the freshness SLO to the rep dashboard.

(3) Alert fatigue. Firing on recalculation buries signal. Trigger: >12 alerts per AE per week in the pod channel. Mitigation: state-transition firing only, 4-hour debounce on rapid flips.

(4) Role confusion. AEs assume the CSM owns the play and do nothing; CSMs assume the AE will follow up and do nothing. Trigger: <30% of red alerts have a logged activity within 5 business days. Mitigation: every alert names a single DRI in the message body and the QBR rollup shows alert-to-action latency by rep.

Counter-Bear. The strongest objection to this entire design is that reps will still ignore the surfaces because their compensation does not reward retention. They are right.

The only mitigation that actually works is to put net revenue retention into AE variable comp - usually 10-20% of OTE tied to NRR on the rep's named-account book - so the rep has skin in the red-account game. Without that change, every other piece of this system is vanity.

Implementation sequence. Days 1-30 (RevOps owns): build the three CRM fields, wire telemetry into Snowflake or Segment, ship the calculation as a daily batch. Days 31-60 (CS Ops owns): enable Slack delta alerts for two pilot pods, instrument the freshness and volume metrics.

Days 61-90 (CRO owns): expand to all pods, ship the Monday digest, gate the QBR rollup behind RevOps signoff, and propose the NRR comp change to finance.

Cross-links: /knowledge/q01 (RevOps charter), /knowledge/q07 (lead-to-account matching), /knowledge/q08 (territory carve mechanics), /knowledge/q102 (CSM-to-AE handoff), /knowledge/q198 (renewal ownership), /knowledge/q231 (QBR mechanics), /knowledge/q244 (forecasting expansion ARR).

FAQ

What is the rep-time budget that should govern every customer-health surface? An AE will spend at most 30 seconds per account per week on health data, so every surface must be designed to that budget. If a dashboard takes 45 seconds to load you have already lost, and if an alert needs a click to reveal its reason you have already lost.

The job is to push one number, one reason, and one action into the tools the rep already opens.

What three CRM fields anchor the health system, and what does the canonical Slack alert look like? On the Account record, use Customer_Health__c (Green/Yellow/Red picklist), Health_Reason__c (short text), and Health_AsOf__c (timestamp), with HubSpot using three calculated properties of the same names.

Slack delta alerts fire only on state transitions, never on recalculation, routed to the AE pod's private channel. The canonical format is: "[Acme] Yellow->Red. Logins down 41% in 14 days.

Action: book a 30-min usage review with their admin this week."

What are the detectable triggers for score gaming and alert fatigue? Score gaming is flagged when more than 15% of yellow accounts have manually edited usage fields in a 30-day window; the mitigation is to derive every input from system-of-record telemetry via Snowflake or Segment and lock the input fields.

Alert fatigue is flagged when more than 12 alerts fire per AE per week in the pod channel; the mitigation is state-transition firing only with a 4-hour debounce on rapid flips.

When should health surfaces be suppressed because of data lag? Suppress the surfaces when telemetry is older than 48 hours, and publish the freshness SLO to the rep dashboard. The trigger that signals a problem is a median Health_AsOf__c freshness above 36 hours for two consecutive weeks.

Stale telemetry that fires a "red" alert minutes after a great call gets every future alert discounted by the rep.

Why does the "Counter-Bear" argue that comp must change for any of this to work? The strongest objection is that reps will ignore the surfaces because their compensation does not reward retention, and the article concedes this is correct. The only mitigation that actually works is putting net revenue retention into AE variable comp, usually 10-20% of OTE tied to NRR on the rep's named-account book.

Without that change, every other piece of the system is vanity.