customer-health

name	customer-health
description	Assess configurable customer health; avoid universal scores.
metadata	{"short-description":"Assess customer health with explainable evidence"}

Customer Health

Outcome

An explainable health assessment with trends, evidence gaps, and recommended interventions.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Account goals, adoption or usage, outcomes, stakeholder coverage, activities, sentiment, service records, renewal data, commercial status, and configured health model.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Use the organization's health definition and thresholds when available; otherwise show dimensions without forcing a composite score.
2. Evaluate current state, trend, freshness, and evidence coverage for each dimension.
3. Prevent one missing or noisy signal from dominating and distinguish operational incidents from persistent health risk.
4. Explain every score or label and show how stale or inaccessible data limits confidence.

Required output

• Health headline
• Dimension scorecard
• Trend and evidence
• Risks and positive signals
• Recommended interventions
• Data gaps

Actions and boundaries

Propose health-field or task updates for review; confirm before writing.