Build an auditable customer health score while keeping observed signals, judgement, and missing data separate.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this to define or apply an account health model.
For every signal record its meaning, source, date range, refresh rate, good and bad thresholds, weight, and missing-data rule. Keep adoption, outcome, support, relationship, and commercial measures visible as separate parts.
For each account show the raw value, baseline or target, trend period, component score, and source. Label manual judgement and explain it. Do not convert a missing value to zero or healthy. Do not use logins as proof of value when the customer's outcome calls for another measure.
Give the component view, overall result, confidence, missing data, material change since the last period, and next check. Include the formula or rules so a person can reproduce the result.
Never invent usage, sentiment, support history, goals, or contract facts. A health score directs review; it does not prove renewal or churn.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.