Attendance drop-off

Members whose visits fall off are noticed early.

A member who used to come three times a week and now comes once is easy to miss until they stop coming. This workflow notices when visits fall below a pattern you set and prepares a short, friendly check-in for the club to approve.

Three calendar cards hang from a brass rail with fewer gold squares from left to right, the last one empty with a small red tag hanging from its corner.
Visits that thin out week by week, and a prepared check-in for the club to approve.

Where this work slips today

A calendar card with an empty outlined square, then a dashed outline of a message bubble where no message has been written, then a second calendar card whose square is only a dashed outline.
Fewer visits, no check-in written, and a week with nothing booked.

Attendance data sits in the booking or door system, but nobody has time to read it member by member. A drop is noticed late, often only when the member asks to cancel, and no one has written to ask how things are going.

How this runs

Three calendars show falling attendance, then a prepared message, a rust checkpoint, the approved message and the closed green ledger. Dots under the stages count the five steps.
Fewer visits, a prepared check-in held at the checkpoint, the message sent and the record. The dots under each stage count the steps below.

On Ateles, each member whose visits fall below the pattern you set becomes a task that moves through a workflow we define with you before anything runs. Each step has a named owner, an agent or a person. The steps below are the intended design, not a record of work already running.

The five steps

  1. A drop in visits is noticed. Your booking or door system shows a member visiting less than the pattern you set, for example half as often over three weeks. That becomes a task in the shared record, with the recent visits.
  2. The agent prepares a check-in. A short, friendly message in the club’s tone that asks how things are going and mentions a class or time the member used to come to. It can do only what its permissions allow.
  3. The checkpoint. Like any message to a member, the check-in waits. A named team member approves, edits or stops it before it goes out.
  4. The check-in goes out. Once approved, it is sent to the member. A member who has asked not to be contacted is left out by the rule you set.
  5. The record keeps it. The visits, the message, the decision and any reply stay in the record, so the club can see who was contacted and when.

Who does what

The agents do the preparing and your team does the deciding. That line is drawn before anything runs, and nothing crosses it without an approval.

  • The agents prepare. Reading the visit pattern against your rule, drafting a short check-in in the tone you approved, and noting who was already contacted.
  • Your team decides. What counts as a drop, who gets a message and what it says. A reply about a personal reason, a complaint or anything unusual goes to a named person.

Example: a fitness club

A member of a fitness club who came to an early class three times a week has come once in the last three weeks. The club’s rule marks the drop, the member becomes a task, and an agent drafts a short message that asks how things are going and mentions the early class.

The message waits at the checkpoint. The club’s manager approves it, and then it goes out. If the member replies with a personal reason, the case goes to a named person at the club, who answers in person. Each step stays in the record.

What the record holds, in order:

  1. The recent visits and the rule that marked the drop
  2. The message the agent drafted
  3. The manager's approval
  4. The member's reply, and who answered it

See what you could delegate.

A free, no-commitment 30-minute conversation. You leave with a clearer picture, whether or not you work with us.

A calendar card with one gold square filled in, beside a small blue notebook with a pencil lying across it.