Takes the auditor's per-workflow scores, groups them by customer account, computes a composite technical health score, and routes each account: critical books an intervention and opens a task, at risk gets a nudge, healthy is left alone on purpose.
How it works
A customer success team cannot read every workflow its customers build. This gives them a number per account instead, and a play for each band, so the scarce thing, a human's time, goes where it moves a renewal.
Three ways in: a daily schedule, a POST handoff from the Workflow Health Auditor, and a GET that renders the book report in a browser. The audited workflows are grouped by account name, and each account gets three signals: average fragility, stability (the share of workflows that scored critical) and findings density.
Composite health is fragility at 60 percent, stability at 25 and density at 15, banded at 75 and 50. Every account also gets plain-language reasons and a play. Critical books a 30 minute technical intervention, leading with error handling and credential hygiene, with a re-audit in 14 days. At risk gets an invite to office hours and a template pack. Healthy stays in the automated nurture track.
The book of business here is seeded demo data. The fragility column is not: it comes from the auditor scanning a real instance.
Key features
- Three entry points converge on one scoring path
- Composite score with the weights visible in the code, not hidden in a prompt
- Every band has a named play, and the healthy band's play is to do nothing
- Critical accounts get a Slack alert and a task opened in the CS platform in one pass
- Browser report lists accounts weakest first with the three signals as bars
Step by step
- Signals inDaily Health Run, Audit Handoff (acked with 202), or Book Report Request.
- Load Book Of BusinessGroups audited workflows by account and aggregates scores, findings and the three worst workflows.
- Score AccountsComputes fragility, stability and density, the composite, the band, the reasons and the play.
- Requested As HTML?Browser request gets the report; scheduled and handoff runs go on to routing.
- Route By HealthThree outputs, one per band.
- ActCritical posts to Slack and opens an intervention task. At risk posts a nudge. Healthy is logged with no human touch.