
Open the customer health score conversation with: “I want to check whether our service is working for your business. Where are we making your work harder?” Build your spreadsheet around five signals, record the evidence behind each, and use changes to choose a useful follow-up. A color without a conversation gives you very little.
My view is that the sheet should help you prepare for that call. It should never let an account manager diagnose a departing client from a quiet ticket queue. Use a monthly review as a proposed working rhythm, with urgent problems handled when you learn about them.
Choose Signals You Can Explain to the Client
Start with information your team can check against the service record. Give each signal a plain status: stable, concern or unknown. Compare it with the previous review, keeping the underlying observation so another account manager can understand the change.
I’d use the following five signals. These are suggested worksheet categories, not a validated retention model. Agree what evidence earns each status before the team starts scoring, and record exceptions rather than quietly changing the rule for a favored account.
| Signal | Evidence to Record | Question That Leads to Action |
|---|---|---|
| Service Friction | Repeated unresolved issues, disputed fixes or a project problem, with the relevant ticket or project record. | “Which part of this problem is still getting in your way?” |
| Client Feedback | What the client actually said, who said it and whether an agreed response was completed. | “You raised this concern at our last review. Did our response address it?” |
| Agreed Decisions | A business decision awaiting a named approver, including its consequence and the date you agreed to revisit it. | “Does this decision still need to happen, and who should own it now?” |
| Payment Changes | A change from the agreed payment terms, checked with finance for billing errors or an active dispute. | “Is there an invoice issue we need to resolve before this can be paid?” |
| Business and Contact Changes | A confirmed change in the business or its responsible contact, plus what remains unknown about its effect on service. | “Has this changed who we should work with or what you need from us?” |
Ticket volume alone can’t tell you whether a client is healthy. Fewer requests might mean fewer problems, but users might also be going elsewhere for help. More requests might follow a planned rollout. Read the work and ask about the experience before assigning a concern.
A missed meeting needs the same restraint. If an accounting client is in its filing period, attendance may tell you more about the calendar than about your relationship. Paul Green suggests shaping account contact around that sector’s busy periods. That is a useful planning suggestion, not evidence that every unanswered invitation is harmless.
Build a Sheet That Keeps the Evidence
Use a row for each client at each review, with a separate status and evidence cell for every signal. Keep the account owner visible. Preserve the previous review so the current color can’t overwrite the reason the account needed attention.
Beside those cells, record the next action and its owner. Add the agreed follow-up date and the result when it arrives. A client contact belongs in that action only after they have accepted the task; entering their name in your sheet doesn’t create an agreement.
Keep “unknown” available. A missing service review is missing evidence, not permission to call the account stable. Ask the account owner to close the information gap, without treating the absence of a reply as proof of dissatisfaction.
Dan Mallard describes using a form or spreadsheet that deducts points for problems, including repeated escalations. In his account, account managers use the resulting color alongside renewal information, with serious concerns reaching leadership. That describes a practitioner’s working approach. It doesn’t establish weights that predict whether your client will renew.
I’d begin with visible signal statuses rather than a weighted total. If you later add an overall status, document how the evidence produces it. Keep a serious unresolved service issue visible even when the other cells look reassuring, and let a person explain the decision.
Turn a Concern Into Words You Can Use
For a recurring service problem, say: “I can see we’ve returned to this issue. I’ve asked our service lead to review the previous work. What is still failing for your team?” Check the answer with the service lead, then agree what evidence would show the problem is resolved.
If the client says, “We’ve already explained this,” reply: “You shouldn’t have to rebuild the history for me. I’ll read the notes with our service lead and come back with the gap.” Make that internal handoff before you ask for another meeting.
For a stalled decision, say: “We were waiting for approval on the proposed change. Has its importance changed, or do we need a different person involved?” If it has lost priority, document the revised plan and any service consequence with the appropriate owner. Don’t label the client disengaged because they declined your proposal.
What do you say when the client is simply busy? Try: “Understood. Which decision needs your attention before our next agreed review, and what can we prepare so that discussion is useful?” Give them the relevant service context instead of another generic request to catch up.
I don’t buy the generic advice to treat every quiet account as an upsell opportunity. In an MSP, the silence may concern unresolved delivery work you already owe the client. Bringing a sales pitch to that conversation can leave the service problem unanswered. Establish what is happening before proposing more scope.
Choose the Accounts That Need Follow-Through
At the monthly review, compare each account with its previous evidence. For a manageable starting agenda, select three accounts whose status worsened and agree an action for each. That is a suggested meeting choice, not a ceiling on urgent work or a threshold supported by a benchmark.
Let the seriousness of the confirmed issue govern its route. A concern that needs service leadership should reach that owner immediately. A disputed invoice needs finance involved before the account manager frames it as a relationship problem.
Keep this review distinct from the model’s quarterly client assessment on margin and fit. Relationship concerns can inform that discussion, but a friendly contact can’t establish a profitable agreement. Equally, a margin problem doesn’t prove that the client is unhappy.
Start your next account review with the evidence behind a changed status. Choose the opening line that fits the issue, name the person who will act, and record what the client agrees would count as progress. At the follow-up, check that result before you change the color.
mspoutpost.com/articles/a-customer-health-score-that-starts-a-useful-client-call
Written by Natalie Brandt
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.
