RSM Consulting
Get in touch

Customer Health in HubSpot: Five Checks Before You Trust a Weekly Summary

By Ricardo Martinez Nov 19, 2026, 12:30:00 PM

Customer Health in HubSpot: Five Checks Before You Trust a Weekly Summary

Quick answer: Customer health in HubSpot is only useful when the underlying CRM tells a coherent story. Before relying on HubSpot’s new Customer Health Assessment, verify who counts as a current customer, whether account evidence is complete, who owns the data, how risks become actions, and how the team corrects bad signals.

A customer-health process can look sophisticated and still be useless.

HubSpot’s new Customer Health Assessment private beta is a good reason to tighten that up. Here are five checks to run before you let a weekly summary drive customer-success attention.

1. Can you define a current customer without opening a spreadsheet?

The initial beta assesses the customers currently defined in CS Workspace settings. That makes customer eligibility the first operational test.

Write the definition as one sentence. For example: “An active customer is a company with an active contract after go-live, excluding churned accounts and pre-implementation deals.” Your own definition will be different. The point is that it must be explicit.

Then test it against real edge cases:

  • a customer in implementation;
  • a company with an open expansion deal;
  • an account that churned and later returned;
  • a parent company with several customer entities; and
  • a deal marked closed-won before the customer is actually live.

If the answer changes depending on who you ask, the weekly summary will inherit the confusion. Start by aligning lifecycle, customer-status, deal, and association logic around the definition your team approves.

2. Can you identify the evidence behind a risk?

A health summary should help the team understand why an account needs attention. If the available data is incomplete or disconnected, the summary may be technically correct and still operationally thin.

Review the data sources your team already uses when judging a customer. Depending on your model, that may include renewal activity, onboarding milestones, support interactions, product usage from an integrated system, meeting outcomes, or CSM notes. Do not assume every field is useful just because it exists.

For each source, ask three questions:

  1. Is it reliably connected to the correct customer record?
  2. Is someone accountable for keeping it current?
  3. Would a CSM trust it when deciding whether to escalate an account?

If the answer is “no” to any of those, the issue is not the weekly summary. It is the data contract underneath it. RSM’s HubSpot product-update tracker is useful for monitoring the beta, but a feature announcement is not a substitute for validating your own portal.

3. Does each critical customer fact have an owner?

“Sales owns the CRM” is not an ownership model for customer health.

CS may own meeting context. RevOps may own the data model and automation. Finance may own billing or contract facts. Support may own ticket categorization. Product may own usage data. That can work well—but only if the handoffs are intentional.

Make ownership visible for the information your health process needs:

  • who creates or updates it;
  • what triggers the update;
  • how quickly it should be current; and
  • who resolves conflicts when two sources disagree.

This is less glamorous than a health score. It is also the difference between a signal your team acts on and a signal they dismiss.

4. What happens in the next 24 hours when a risk appears?

A risk without a response path is just more information for already-busy people to ignore.

Decide in advance what the team does when a weekly health summary highlights a concern. You do not need a workflow for every possible scenario. You do need a basic operating rule.

For example:

  • a CSM reviews the context and confirms or dismisses the concern;
  • confirmed risks receive a named owner and a next action;
  • material commercial risks are escalated to the appropriate account, renewal, or leadership process; and
  • the CRM captures the action taken and the current status.

This is where CRM process and automation work earns its keep. The goal is not to automate judgment. The goal is to make sure good judgment does not vanish into a Slack thread.

5. Can your team tell the system when it is wrong?

The weekly review should get better because the team is learning—not because people quietly stop trusting it.

Build a lightweight feedback loop. When a risk is irrelevant, ask why. Was the customer definition wrong? Was a record stale? Was an association missing? Did the process fail to capture the context a CSM already knew?

Those answers reveal the actual work. They also keep the team from responding to every signal by adding more fields, more scoring points, and more exceptions until the health process becomes unmanageable.

A targeted CRM audit can help distinguish data-quality problems from workflow, ownership, and reporting problems before the team invests in a larger rebuild.

HubSpot’s next step will make this more important

HubSpot says future updates will allow teams to define customer segments and customize how health is assessed and summarized for them.

That should be valuable. A strategic enterprise customer, a low-touch customer, and a new customer should not automatically receive the same review. But segments only work when their membership is clean and their playbooks are real.

Use the private beta as a readiness exercise. If your team cannot explain who belongs in each review group, what evidence matters, and what happens after a concern appears, do that work before expecting software to solve it for you.

The practical takeaway

HubSpot is making it easier to bring weekly customer-health context into CS Workspace. That is progress.

The teams that benefit most will not be the ones with the busiest dashboards. They will be the ones with a clear customer definition, trusted account evidence, explicit ownership, and a consistent response when a risk appears.

Want to see whether your CRM can support that kind of customer-health operating rhythm? Start a conversation with RSM Consulting.

FAQ

What is a customer-health summary in HubSpot?

In HubSpot’s Customer Health Assessment private beta, it is a weekly summary of risks and opportunities for each current customer, based on available HubSpot data and displayed in a Customer Health card in CS Workspace.

Should every customer use the same health criteria?

Not necessarily. HubSpot says customization by customer segment is planned for a future update. Even before that arrives, teams should decide whether their customer types have different expectations, risks, and response playbooks.

Is a customer-health score enough to prevent churn?

No. A score or summary can surface context, but preventing churn depends on the quality of customer data, the team’s judgment, and the actions taken after a risk is identified.

Keep reading

More from the field

Get in touch

Tell us what your CRM is doing wrong

Book a time directly, or send us a note and we will come back to you — usually the same day. Either way you get a real answer about your portal, not a pitch deck.

Book a meeting

Pick a time that suits you. Thirty minutes, no obligation, and we will look at your portal together.

Open the calendar
✓ Free 30-minute discovery call
✓ No obligation, no strings attached
✓ A real answer, not a pitch deck
Scheduling runs on HubSpot Meetings.

Or send an inquiry

Tell us what is going wrong and we will come back with a first read on it.

Send inquiry
Submissions land in our HubSpot CRM — the same portal we would be auditing for you. support@crmbyrsm.com