Read decline before it becomes cancellation
The fitness lane treats retention as an operating loop, not a renewal event. This page orients operators to the moving parts: the signal, the record it lands on, and the workflow that acts on it.
The signal
Check-ins and class history compile into engagement telemetry per member, per location. The comparison that matters is the member against their own pattern — a regular who stops appearing is signal even when the location's overall traffic looks fine. Declines surface as flags with a named owner, not as a line in a report nobody opens.
The record
Visits, billing, and engagement share one member record across every location in the brand. Gate check-ins compile into verifiable visit records — designed to support health-account receipts and insurer reimbursement syncs where a member's plan allows them. Trainer certifications are checked programmatically before class assignment; expired credentials never reach the schedule.
The workflow
A retention flag opens a bounded sequence: review the member's context, propose outreach, and send inside policy. Messages that leave the building pass the same consent, quiet-hours, and send-authority gates as every automated communication on the platform — see approval gates for autonomous agents. Aria drafts; operators decide; the record keeps both. The companion field note, retention starts before the cancellation call, tells the same loop as a narrative.
What this page does not cover
Retention-lift figures are not published here — they are measured in your operation, inside the authenticated console. Live member records, flags, and outreach state are console surfaces; this page is orientation.