Weekly classes, occasional workshops and a student's break can look similar in an attendance list. Mako keeps the visit history visible while your studio chooses whether a follow-up would help.
The gap after a weekly class looks different from the gap after a workshop. Look at the recorded dates and any booking your team already knows about.
A quiet stretch after a workshop may be normal for that student. Use the recorded class dates and what the team knows before choosing a follow-up.
Class, teacher and workshop comparisons need those fields in the source. Confirm the available group views before using them for student follow-ups.
A student may be away, attending workshops or choosing a different class. The studio decides whether to make contact and keeps any task with the person who knows the student.
Help the team keep class attendance and student follow-ups together, with the booking system and contact decisions staying in the studio's hands.
Explore retention, rebooking, cohorts, client segments, historical revenue context, and privacy-safe benchmarks at no cost.
Create a free Pulse account →Need to confirm a source or workflow? Talk with the Mako team.
Contact usMako uses recorded visits to show changes in attendance. Your team checks the class history and available membership context before choosing a follow-up.
Class, teacher and format comparisons need those fields in your source. We can confirm the available groups and small-group rules during setup.
Pulse keeps follow-ups as internal tasks. The studio decides whether a student needs contact and handles it through the tools it already uses.
No. Mako uses observed return patterns and historical context rather than predictive cancellation scoring.
Keep the current booking platform while we check its attendance export and the fields available for the student review.
Explore the visit history and student follow-up list, then check which fields your studio can bring across.