Review customer account health across systems
Combine account usage, support history and renewal context into a current review packet. Explain changes with dated evidence and give account owners a focused list of questions and next actions.
How this works
Combine account usage, service issues, feedback and commercial milestones. Explain observable changes with evidence rather than an opaque model judgment.
Quiet activity may reflect seasonality, completed work or missing telemetry. Preserve uncertainty and apply an approved rubric before the owner chooses an intervention.
Before you start
Account identity map
Choose the cohort and verified CRM, workspace and help-desk mappings, including parent and subsidiary handling.
Comparable measures
Define usage, denominators, windows and freshness limits; agree relevant service, survey and renewal signals.
Review rubric and owner
Use documented watch conditions and account owners. Without a rubric, provide facts without health labels.
Prepare the inputs
- account_roster
- Required
Account ID, connected-system IDs, owner, lifecycle stage and commercial milestones.
Resolve duplicate names, multiple workspaces and missing owners before joins.
- usage_windows
- Required
Dated current and comparison measures with definitions and denominators.
Require equal periods or approved normalization; missing data is not zero.
- service_and_feedback
- Required
Ticket states, SLA flags, issue themes and available survey results.
Retain dates, unique counts and survey samples; distinguish updates from new issues.
- relationship_context
- Required
Renewal date, approved contact history and relevant account notes.
Verify business contacts and current terms; flag uncertain stakeholder changes.
- health_rubric
- Optional / conditional
Versioned conditions, data freshness limits and owner-review priorities.
Required for labels; a factual review can proceed without labels.
Implementation, step by step
Resolve the cohort and account mappings
- Freeze the roster and cutoff. Reconcile CRM accounts with product and support identifiers, preserving parent-child relationships.
- Set aside ambiguous mappings. Similar names do not justify combining workspaces or counting merged organizations twice.
Checkpoint: Each included account has a verified join map and an explicit source-coverage state.
Build comparable observation windows
- Collect current and comparison usage with matching definitions and denominators. Record boundaries, timezone and extraction times.
- Calculate changes deterministically. Report changed subscription size, tracking rules or period length before claiming comparable trends.
Checkpoint: Every trend has a stated measurement basis or is marked non-comparable.
Summarize service and relationship evidence
- Summarize open tickets and unresolved commitments with references. Keep ticket volume distinct from severity.
- Add renewal timing, business contact history and survey sample sizes. Missing surveys or quiet contacts do not establish dissatisfaction.
Checkpoint: The packet shows usage, service and relationship facts without conflating their meanings.
Apply the agreed review rubric
- Apply each documented condition with its evidence. Positive measures cannot conceal missing data required by the rubric.
- Compare with the last comparable review: newly flagged, unchanged, improved or unassessable. These states are not churn probabilities.
Checkpoint: Every label is reproducible from a named rule and dated account evidence.
Prepare owner-specific review questions
- Order the queue by agreed urgency and renewal timing. State what changed, the investigation question and accountable owner.
- Draft check-ins only when requested. Keep causal explanations hypothetical until verified; offer no unauthorized concession or failure claim.
Checkpoint: The owner can choose a next action while seeing both the evidence and its limits.
Publish the review artifact within its scope
- Recheck freshness and mark needed refreshes. Save the comparison basis and rubric version for the next cycle.
- Return the packet to the authorized destination. Separate owner-confirmed findings from automated flags and record identity corrections.
Checkpoint: The handoff separates current evidence, proposed interpretation and the owner’s accepted action.
Decisions along the way
No approved health rubric exists
Return the measured facts and open questions without inventing weighted scores or red/green thresholds.
Usage drops while the number of contracted seats also changes
Report both changes and use the agreed normalized measure before calling the account less engaged.
Survey feedback comes from one respondent
Preserve that sample size and avoid presenting it as the view of the whole account.
A required system is stale or unavailable
Label the missing coverage and hold conclusions that depend on it; retain supported facts from other sources.
What you will produce
account-health-review.csv
CSVA comparable, dated account snapshot with a source-completeness state.
Include: account_id · owner · cutoff · periods · measure_definitions · usage_change · open_service_needs · renewal_date · rubric_version · review_state · source_freshness
account-review-queue.md
MarkdownOwner questions and proposed next actions, separated from accepted decisions.
Include: account_id · changed_evidence · rule_triggered · alternative_explanation · owner_question · next_action · decision_state
account-source-map.csv
CSVReproducible joins and references for refresh.
Include: account_id · system · system_id · record_reference · observed_at · coverage_status
Check the result
- Verify a sample of account joins against each source system, including subsidiaries.
- Recalculate changes and inspect denominator or measurement changes.
- Check that positive evidence cannot turn missing required data into a healthy result.
- Confirm that summaries preserve resolved issues, survey sample sizes and source timestamps.
When something goes wrong
Tracking stopped during the comparison window
Mark the usage trend unassessable and ask the analytics owner to restore or explain coverage.
A renewal date conflicts across systems
Show both records and request commercial confirmation before prioritizing by that date.
The owner disputes an automated flag
Record the explanation and evidence; revise the rule only through the agreed rubric-maintenance process.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Review the selected account using the approved monthly rubric.
Inputs
Synthetic: account C8 has 50 contracted seats in both 30-day periods. Active seats fall from 40 to 30, two unresolved tickets are past their verified SLA, and renewal is six weeks away. The rubric flags a usage fall above 20%. C9 has no current usage export.
Expected result
C8 decreased 25% and meets the watch rule. Attach ticket and renewal evidence; ask what changed without assigning churn probability. C9 remains usage-unknown.
Run a small pilot
Start small
Review a small cohort twice, including renewal, seasonal and missing-data cases.
Record the baseline
Measure preparation time, identity corrections and usefulness of manual flags.
Agree success criteria
Require correct joins and calculations; agree the desired share of owner-confirmed actionable flags.
Stop or revise
Pause automated labeling if a system’s measurement definition changes or missing telemetry repeatedly produces false deterioration.
Keep the scope clear
- Analyze customer-account operations, not employee productivity or inferred personal traits.
- Do not promise commercial concessions, alter contracts or contact customers unless that action is authorized.
- These operational labels do not constitute a tested prediction model or establish why a customer might leave.
Check before using
The account owner checks context and decides the response; health labels are operational review categories, not validated churn probabilities.
Business activities
- Deliver recurring client work
- Resolve customer questions
- Review business performance
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Account identity map and usage measures · Support history and survey evidence · Renewal dates, contacts and health-review rubric
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow