Skip to content
Open Source Apache 2.0

A coach on every Salesforce record

Record Health Check turns business rules into clear, actionable guidance on Salesforce record pages without changing record data or save behavior.

ConfirmWhat looks good
FocusWhat needs attention
ActWhat to do next
Record Health Check showing passed, failed, warning, informational, and skipped checks on an Account

Guided path

The fastest path to a working Check

Follow one focused sequence from understanding the card to configuring your first production-ready experience.

Examples

See it solve real Salesforce problems

Compare four ways to answer a business question about an Account. Each example shows why the method fits, what a user sees, and what to do next.

01Keep branch billing aligned with headquartersFor branches billed through headquarters, confirm the complete billing address matches the parent Account.Runs on: AccountVerify with a formula

Why this method?

Both addresses are available from the Account and its parent, so a formula can compare them directly. No related-record query or custom Apex class is needed.

A difference in any billing-address field needs attention. An Account without a parent is skipped. Display formulas show the two addresses but do not determine Pass or Fail.

Example result

Found
Branch: 100 Congress Ave, Austin, TX 78701
Display formula on the branch Account
Expected
Parent: 500 Elm St, Dallas, TX 75202
Display formula on the parent Account
Result
Needs attention · Info
Next step
Confirm the legal bill-to location with Finance before correcting either Account.

Key configuration

Pass Condition
AND(BillingStreet = Parent.BillingStreet, BillingCity = Parent.BillingCity, BillingState = Parent.BillingState, BillingPostalCode = Parent.BillingPostalCode, BillingCountry = Parent.BillingCountry)
Display: Found Formula
Complete branch billing address
Display: Expected Formula
Complete parent billing address
Open full setup and testing
02Keep the high-priority support backlog within capacityCount open, high-priority Cases for an Account without blocking Case updates.Runs on: AccountVerify with a query

Why this method?

The information is on Cases related to this Account. A query counts the open Cases marked High priority, and the Check compares that count with the service team’s limit.

No matching Cases returns a count of zero, so this Check passes. Hidden records are excluded; missing required permissions may produce Unable to Check.

Example result

Found
4 open high-priority Cases
COUNT() of matching visible Cases
Expected
3 or fewer
Fixed value configured by the service team
Result
Needs attention · Warning
Next step
Review Case ownership and the response plan.

Key configuration

Source Query
SELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND Priority = 'High'
Comparison Operator
Less than or equal
Expected Value
Fixed value: 3
Open full setup and testing
03Protect product continuity across open pipelineCheck whether this Account’s open Opportunities include a product recorded on its previously won Opportunities.Runs on: AccountCompare two queries

Why this method?

One query finds products on open Opportunities. Another finds products on won Opportunities. The Check passes when the two Product ID lists share at least one value.

Product names are illustrative; the Check compares Product IDs. In this example, no open-pipeline or purchase-history rows produce Skipped because that outcome is configured.

Example result

Found
Open pipeline: Product A, Product B
Source query → Product2Id
Expected
Won Opportunities: Product B, Product C
Comparison query → Product2Id
Result
Pass — Product B appears in both lists
Next step
If the lists do not overlap, confirm the intended sale before changing product selection.

Key configuration

Source Query Field
Product2Id
Comparison Query Field
Product2Id
Comparison Operator
Lists overlap
If Either Query Finds No Records
Skip
Open full setup and testing
04Score strategic-account readiness before executive reviewUse developer-created Apex to combine relationship, pipeline, activity, and billing evidence into one readiness score.Runs on: AccountVerify with Apex

Why this method?

The decision combines several objects, a configurable activity window, and weighted scoring. A developer implements that logic in an Apex class; an administrator can then configure its threshold and parameters.

The class awards 25 points for each criterion, so possible scores are 0, 25, 50, 75, and 100. With an 80-point threshold, all four criteria must pass. Strategic Accounts that do not meet the applicability rule are skipped.

Example result

Found
75 points — three of four criteria met
Score returned by AccountStrategicReadinessCheck
Expected
80-point minimum
Administrator-configured minScore
Result
Needs attention · Critical
Next step
Review the missing readiness criterion before the executive review.

Key configuration

Apex Class
AccountStrategicReadinessCheck
Apex Parameters (JSON)
{"minScore": 80, "activityDaysBack": 60}
Applies When
ISPICKVAL(Type, "Strategic")
Open full setup and testing

Documentation

Choose what you want to do

Find focused guidance for learning the basics, building Checks, operating in production, or extending the framework.

Resources

Explore the ecosystem

Go beyond the core package with optional extensions, reusable configuration patterns, presentations, and product demonstrations.

Extensions repositoryExplore optional packages for logs, scheduled runs, guided building, alerts, reports, and integrations.Open repository
View SlidesUse presentation-ready material to introduce the product to your team.Coming soon
View DemoWatch it explain findings directly on a Salesforce record.Coming soon