Why you would use it
You have more customers than anyone can give proper attention to, and the ones in trouble are not always the ones making noise. An account with no meetings booked, a contact who has left and an open complaint is in a worse position than one that phones every week, but nothing on the record says so.
Relationship Health puts a number on it. It runs a set of plain pass or fail checks over each customer, scores them out of 100, and shows you which ones failed and why. Instead of a feeling about an account you get a list of things to do.
If you read nothing else: the score is just checks passed out of checks scored. Open a customer, look at the red and amber checks, and work down the list.
How the score works
Score = checks passed, divided by checks scored, times 100. Every check weighs the same.
Bands: Healthy is 80 and above, Moderate is 40 to 79, Needs Attention is below 40.
21 checks exist, and your company can switch any of them off. A switched-off check leaves the score and the panel completely, so you are scored out of 21 minus whatever is off.
A check nobody has answered counts as a fail. The panel shows those separately, so "not filled in yet" is easy to tell apart from "genuinely bad".
Some checks pass on No. Anything phrased as an absence, such as no complaints or no billing disputes, passes when the answer is No.
Where the checks get their answers
Wherever The Layer already holds the information, the check answers itself.
Kind of check | Where the answer comes from |
Automatic | Data already on the record: appointments and their outcomes, emails and calls logged, contact flags, live services and contracts, cease activity, case feedback. |
Mapped | Cases, once an administrator has said which case categories mean a complaint, a billing dispute or a service credit request. Until that mapping exists the check falls back to a manual field. |
Manual | Judgement only a person can make, recorded on Yes or No fields on the customer: do we understand their objectives, would they give a reference. |
Where you see it
On the customer record. A panel with the score, the band, how many checks are passing, and every check with its reason.
In grids, exports and automations. Six fields are written back to the customer on every recalculation, so the score behaves like any other field. See Reporting on Relationship Health.
As history. One snapshot per customer per day, which is what the trend arrow compares against.
How often it recalculates
Three ways, so the number is current whenever someone actually looks at it:
A batch run does every scored customer, typically overnight.
Opening a customer recalculates the score if it is older than your company's freshness window. The default is 24 hours.
The Refresh action on the panel recalculates immediately.
What it is not
Not a churn prediction. You can record a churn risk you have spotted, but nothing guesses one for you.
Not an account plan. It only asks whether the plan has been kept current.
Not per user or per site. One score per customer account.
Turning it on
Relationship Health is off until an administrator enables it in Settings then Record Scoring. Enabling it creates the fields it needs, so there is no separate setup task. See Setting up Relationship Health.
It is one metric in Record Scoring, the same engine behind Lead Score and Customer Health. Each one is enabled and tuned separately.
Related articles
Reading the Relationship Health panel
The Relationship Health checks in detail
Answering the Relationship Health questions on a customer
Recording a churn risk
Setting up Relationship Health
Tuning the checks: mappings, windows and thresholds
Contact responsibilities and the coverage check
Overrides, exclusions and parent accounts
Keeping scores up to date
Reporting on Relationship Health
Relationship Health troubleshooting and FAQ
Support
Support page: thelayer.com/support
Email: [email protected]
Telephone: 03333 222 000

