A member is not at risk because they skipped a class. They are at risk when their own pattern breaks: the regular Tuesday gone quiet, visits halving against their own norm, no-shows or late cancels climbing, bookings drying up. Xyzios reads that pattern for every member every night.
Signals, from each member's own rhythm
- Days since the last visit
- Attendance down against their own norm
- A usual class missed three times
- No-shows or late cancels climbing
- Back from a pause, not returning
- A move to a cheaper plan
- A new member with low engagement
- No future bookings
- A failed payment
Scored every night
0–11
weights learn from your own cancellations once there are enough of them
Where the score puts them
- 3 or moreon the list
- 6 or moreHigh, name and score in colour
Nothing here contacts a member. Saves are drafted into Approvals for High members only; anyone on the list can be called, given to a teammate as a task with Assign, and marked Handled.
What the score is for
It orders a list, it does not judge a person. The top of the list is who to call first; the signal beside each name says why, in plain words; the suggested move says what usually works.
What happens next
- Your AI team drafts a save into Approvals only for High members (a score of 6 or more), and of those only for the ones who slipped recently, whose payment failed, or who are brand new and never came in. Everyone else stays on the list for a personal call.
- A call made from the list counts once someone taps Handled. The row remains, marked with who and when, and a save that was waiting for that member counts on Recovered Revenue from the tap. No new save or payment recovery draft is proposed for seven days, so nobody hears from the studio twice.
- The default view hides people more than 30 days out, because on a studio’s first day the list is mostly people who left long before Xyzios saw them. Include long-lapsed, in the list’s Filter, shows them.
Handing a call on
Whoever reads the list does not have to make every call. Assign, beside Handled, gives a member’s call to a person, or leaves it open to a role or to the team for whoever takes it first, as a task on Tasks that reads “Call Jane Doe: at risk”, with the member’s top signal and the suggested move in its notes. It is set at the member’s own location, so a role or the team there has it. A member has one call open at a time, and you never give one to yourself: you tap Handled instead.
Ticking that task done is what records the call. The member is marked Handled on the authority of whoever gave it, even if the person who finished it cannot open Retention, and the record names them both. Everything a tap does follows from it: a save that was waiting for the member is withdrawn and counts on Recovered Revenue from then, and no new save is proposed for seven days. A call given more than two weeks before it is ticked is only a finished task: the member is not marked Handled, and the message after the tick says so.
Where you meet it
Retention is the list itself. Data counts the members at risk by location, and Your focus on the Overview often starts with them. A call someone was given is on Tasks.