Guide

How to build a customer health score in Salesforce

A customer health score in Salesforce is a formula field that turns a few fields on the Account object into a 0–100 number and a Red, Yellow or Green band. This guide builds one with 7 custom fields, 5 formula fields and a report, using the same rule as our health score template, and then covers what a score built only from CRM data will miss.

1. Add the fields to the Account object

Score each area by its worst open problem, using the rubric from the template: 80 for Good, 60 for Concerning, 35 for Poor. You probably have ARR and a renewal date on the account already; if not, add those too.

FieldTypeWhat goes in it
Product_Score__cNumber (3, 0)Bugs, urgent tickets and incidents in the last 60 days
Adoption_Score__cNumber (3, 0)Seat and product usage in the last 60 days
Relationship_Score__cNumber (3, 0)Champions and sponsors in the last 90 days
Commercial_Score__cNumber (3, 0)Budget, competitors and renewal terms in the last 120 days
Last_Conversation__cDate/TimeThe last real conversation (a call or meeting), set by hand or by a flow from logged activities
Health_Event__cPicklistNone, Cancellation notice, Champion or sponsor left
Event_Date__cDateWhen that event happened

2. The formula fields

Create these five in order, because each one refers to the one before. When Salesforce asks about blank field handling, choose "Treat blank fields as blanks", or ISBLANK will never be true on a number field.

Days_Since_Conversation__c (Number, 0 decimals)

DATEVALUE turns the date/time into a date, and subtracting dates gives days. An account with no conversation on record gets 999, so it reads as silent rather than fine.

IF(ISBLANK(Last_Conversation__c), 999, TODAY() - DATEVALUE(Last_Conversation__c))

Relationship_Adj__c (Number, 0 decimals)

Silence caps the relationship score: 45 days without a conversation holds it at Concerning (60), 90 days at Poor (35), whatever the owner typed.

MIN(
  BLANKVALUE(Relationship_Score__c, 0),
  IF(Days_Since_Conversation__c > 90, 35, IF(Days_Since_Conversation__c > 45, 60, 100))
)

Event_Cap__c (Number, 0 decimals)

A cancellation notice caps the whole score at 30, and a lost champion or sponsor caps it at 50 for 60 days. With no event the cap is 100, which changes nothing.

IF(ISPICKVAL(Health_Event__c, "Cancellation notice"), 30,
  IF(AND(ISPICKVAL(Health_Event__c, "Champion or sponsor left"),
         NOT(ISBLANK(Event_Date__c)),
         TODAY() - Event_Date__c <= 60), 50,
  100))

Health_Score__c (Number, 0 decimals)

The smallest of three numbers: the average of the four areas, the weakest area plus 25, and the event cap. Salesforce's MIN takes as many arguments as you need.

ROUND(MIN(
  (BLANKVALUE(Product_Score__c, 0) + BLANKVALUE(Adoption_Score__c, 0)
   + Relationship_Adj__c + BLANKVALUE(Commercial_Score__c, 0)) / 4,
  MIN(BLANKVALUE(Product_Score__c, 0), BLANKVALUE(Adoption_Score__c, 0),
      Relationship_Adj__c, BLANKVALUE(Commercial_Score__c, 0)) + 25,
  Event_Cap__c
), 0)

Health_Band__c (Text)

Red under 40, Yellow from 40 to 79, Green at 80 and above, and "Insufficient data" when any area is blank. Put this field on the page layout and in list views; it's the one people will read.

IF(OR(ISBLANK(Product_Score__c), ISBLANK(Adoption_Score__c),
      ISBLANK(Relationship_Score__c), ISBLANK(Commercial_Score__c)),
  "Insufficient data",
  IF(Health_Score__c < 40, "Red", IF(Health_Score__c < 80, "Yellow", "Green")))

Check it with the template's examples. An account scoring 80, 80, 35 and 80 with a call last week and no event averages 69, but the weakest area caps it at 60: Yellow. Scores of 35, 35, 60 and 35 with a cancellation notice would be 41, and the cap makes it 30: Red. Four 80s with a call last week give 80: Green. The same four 80s with no conversation for 50 days give 75: Yellow, which is the silence rule doing its job.

Salesforce limits how large a formula can be once it's compiled, and a formula that refers to another formula field counts that field too. These five fit. If you keep adding to them and hit the limit, move the intermediate steps into a scheduled flow that writes plain number fields.

3. A report and a dashboard

  1. Create an Accounts report. Filter on Type equals Customer and Renewal Date in the next 90 days. Group rows by Health_Band__c. Add Account Name, Account Owner, ARR, Health_Score__c, Days_Since_Conversation__c and Renewal Date as columns, sum ARR, and sort by ARR descending.
  2. Save a second version without the renewal filter for the whole book.
  3. On a dashboard, add a stacked bar of ARR by band for the next 90 days, a metric for ARR in Red, and a table of Red accounts by ARR. Subscribe account owners to it weekly.

4. What a CRM-only score can't see

Keep the score anyway. It gives forecasts and reports one shared number, and the fields above are where that number should live.

5. What Horizon adds

Horizon starts from the same Salesforce accounts: ARR, renewal dates, owners and opportunities refreshed daily, with email and calls logged to Salesforce read hourly as evidence. Your field names stay as they are; you map the ones Horizon should read. It then reads what the CRM can't: Gong and Google Meet calls, support tickets, Jira issues, incidents, inbound email and usage, and raises a risk signal with a citation to the call, ticket or email it came from. The health score uses the same four areas and the same rule as above, no more than 25 points above the weakest area and the same event caps, with no AI in the arithmetic. Every account is rescored nightly and whenever a signal is raised or closed, and an account shows "Insufficient data" when less than 60% of the score's weight has evidence behind it. See the Salesforce integration and how the score works.

Updated November 3, 2026

See which of your renewals are at risk.

A 30-minute call on a demo book, or on your own top 25 accounts.

Book a call