How automated playbooks work
When an org's health score crosses a threshold, the platform fires an automated "playbook" — a record + admin queue entry that triggers downstream action. This is invisible to the org; it's a platform-side workflow.
Three playbook types in v1:
**save_motion** — fires when an org's Operations score drops below 50 from a previously healthy state. The record captures the top 5 action items (across Trust + Operations + Growth) ranked by point gap. Triggers the save-motion outreach: review the top actions, decide whether to email the owner, offer a coaching call, or extend the grace period if their score crashed because of a deploy or migration disruption.
**upsell_ready** — fires when an org's Trust AND Operations both cross above 80. Mature, low-risk, well-run orgs are the right audience for cross-sell of paid modules, lending products (when ready), or partner program promotion. The record sits in the queue for the sales/CS team to action.
**recovered** — fires when an org with active save_motion crosses back above 60 (hysteresis gap of 10 points to prevent flapping). Auto-resolves the save_motion record + logs the win. Informational, not actionable.
Where to see them: Admin → Save Motion tab. Pending counts roll up in the admin badge. Each row shows org, trigger reason, when it fired, and (for save_motion) the top action items so an admin can quickly assess what's broken before reaching out.
Admin actions per row:
• **Mark resolved** — you've completed the outreach and consider the playbook closed
• **Dismiss** — the trigger was a false alarm (e.g. an org running an internal stress test that crashed metrics; you can dismiss without action)
Hysteresis prevents flapping — orgs that bounce between 49 and 51 don't generate noise. Recovery requires score >= 60, not >= 50. Same pattern for upsell_ready (drop below 70 to clear).
Stable IDs by date — if the same org's score crashes twice in one day, only one save_motion record exists for that day. The playbook captures the worst-state action items and leaves the resolved record alone.