Follow-up recovery · a Bluerook workflow product
Finding the leads the CRM quietly forgot.
Deterministic checks, privacy-bounded context, a human digest. It finds the gap, prepares the review, and stops short of ever sending a message.
01 · The workflow itself
Rules you can read.
A refusal you can see.
-
Six records, none reviewed
Not because anyone is careless. Because no system was watching. The detector runs on a schedule against the CRM's own fields, and it starts from zero assumptions.
-
Deterministic checks, not a hunch
No owner. Overdue. No next action. Rules a founder can read and argue with, applied after validation so unusable input never reaches a verdict.
-
Context is bounded before review
Each flag becomes a digest entry a person can decide on. Phone numbers and email addresses are excluded from the analysis context by construction, not by policy.
-
Failure has a path, and Send stays cut
A missing column stops the scan, alerts the owner and changes nothing. And the outreach node is disabled on the canvas itself: detection never becomes a message.
02 · Now run the review
Scan. Inspect. Approve.
Never send.
The prepared dataset mirrors the package test fixture: six synthetic records, five gaps, one healthy record that must stay untouched. Prepare context for a flagged lead and approve the task — the sent counter is the point of the exercise.
Records
Selected record
Review package
Prepare a privacy-bounded context summary before drafting.
No outcome logged.
Break it
No failure active.
Verified state
Current export, current count.
Supporting detail comes from the current package and its passing synthetic harness, not from a headline.
No gap disappears, no healthy record is disturbed, and nothing leaves without human approval.