Customer health is easy to oversimplify. Product usage can look strong while a critical issue remains unresolved. A quiet champion may signal risk, or they may simply be busy. A score is only useful when the team agrees on what it means and can inspect the evidence behind it.

Strawberry can bring goals, product use, support history, meetings, account records, communication, and open commitments into one review. Your companion can show where the signals agree, where they conflict, and what is missing instead of turning incomplete data into a confident churn label.

Define health from the customer outcome

Start with the account, lifecycle stage, goals, success measures, stakeholders, review period, and next decision. Use the team's agreed health model when one exists. Keep company-wide signals separate from promises and conditions that apply only to this account.

Want to try it?

Ask your Strawberry companion: “Review this customer account against its accepted goals and health definitions, reconcile the current signals, and show the risks, opportunities, evidence gaps, and next actions.”

Skill

Review customer health

Review whether the customer is reaching value, what has changed, and what deserves attention.

Build the view from several kinds of evidence

SignalWhat to examine
Outcome progressThe customer's stated goals, success measures, and evidence of value.
AdoptionMeaningful product use and the workflows or users that matter, not activity volume alone.
ExperienceSupport impact, onboarding progress, unresolved issues, and delivery commitments.
RelationshipsChampion strength, stakeholder engagement, decision-makers, and relationship gaps.
Commercial contextRenewal, expansion, contraction, or billing context that the team is allowed to use and that changes the next decision.

Keep source dates, definitions, and coverage visible. A stale usage report or incomplete support history should weaken the conclusion rather than disappear inside the score.

Reconcile the signals

Compare the signals instead of averaging them into false precision. Separate observed facts, customer statements, team judgment, AI inference, stale data, and unknowns. If the team uses a score, apply its agreed definitions and show the support for each component rather than inventing weights.

  • What outcome has the customer achieved, and what remains unproven?
  • Which material signal changed since the last agreed review?
  • Where do usage, relationship, support, and commitment signals disagree?
  • What action or conversation could most improve the customer's outcome now?

Turn the review into the next right action

Lead with outcome progress, material changes, supported strengths and risks, open commitments, missing information, and a prioritized next-action plan. If the next step is a QBR, EBR, check-in, renewal, or escalation conversation, carry the current account picture into meeting preparation.

Skill

Prepare for a customer conversation

Prepare the customer conversation from the current goals, health, history, and open decisions.

Skill

Escalate a customer issue

Package unresolved customer impact for the internal owner who needs to act.

Save the health-review method as a team skill when account owners should use the same sources, definitions, and review shape. Once it is trusted, a Routine can prepare the next view and stop when the goals, model, coverage, audience, or sensitive context changes.

How to onboard customers with AITurn accepted goals and commitments into a clear path to first value. How to prepare for any meeting with AICarry the current account picture into a customer check-in, QBR, renewal, or escalation. How to escalate customer issues with AIGive the right internal owner a grounded brief when unresolved impact needs action.
Official Strawberry skill
Copy skill file Download skill file
name
review-customer-health
description
Review a customer account against its accepted goals, success measures, product use, support experience, relationships, commitments, renewal context, and risk definitions. Use for Customer Success account reviews, risk and opportunity assessment, portfolio prioritization, or preparation for a customer conversation without inventing an automatic health or churn score.

Review Customer Health

Build an evidence-backed view of whether a customer is reaching the outcomes they bought for, what has changed, and what deserves attention. Use the team's real health model when one exists; do not turn incomplete product signals into a definitive churn label.

1. Define health for this account

Establish the account, products and scope, lifecycle stage, business goals, success measures, stakeholders, review period, upcoming decisions, and accepted risk or opportunity definitions. Identify whether the result is for the account owner, a team review, leadership, or an upcoming customer conversation.

Use the customer's success plan and prior accepted review when available. Keep company-wide health rules separate from account-specific commitments.

2. Build the current picture

Use approved CRM or account records, product usage, support history, onboarding progress, meetings, email, team messages, billing or renewal context, and open commitments. Preserve source links, dates, definitions, coverage, and ownership for material signals.

Consider the signals that matter for this account:

  • progress toward the customer's stated outcomes;
  • adoption and meaningful product use, not activity volume alone;
  • support experience and unresolved impact;
  • stakeholder engagement, champion strength, and relationship gaps;
  • delivery, onboarding, or product commitments;
  • renewal, expansion, or contraction context when approved; and
  • external or organizational changes that could affect success.

3. Reconcile signals and uncertainty

Compare the signals instead of averaging them into false precision. Strong usage may coexist with an unresolved critical issue; a quiet champion may reflect timing rather than risk. Distinguish observed facts, customer statements, team judgment, companion inference, stale data, and unknowns.

If the team uses a score, apply its accepted definitions and show the evidence behind each component. Do not invent weights or infer protected or sensitive traits.

4. Deliver the account review

Lead with the current outcome, material changes, and next decision. Include as useful:

  • goal and value progress;
  • supported strengths, risks, and opportunities;
  • important relationship and adoption changes;
  • open commitments, blockers, owners, and dates;
  • missing or conflicting evidence; and
  • a prioritized next-action plan.

Use strawberry/operations/prepare-for-meetings when the next job is a QBR, EBR, check-in, renewal, or other customer conversation. Use strawberry/customer-support-success/escalate-a-customer-issue when unresolved impact needs a cross-functional escalation.

5. Keep the view current and controlled

Drafting an account plan, contacting the customer, changing CRM fields, changing a health score, offering commercial terms, and committing product or delivery work are separate actions. Follow active scoped permission and verify completed changes.

After the team accepts the sources, definitions, and review behavior, preserve them for the next cycle. A health Routine may prepare a review from named sources and surface material changes, but it should stop when the account, goals, model, data coverage, audience, or sensitive context changes.