The Visits list on a client’s record used to show one merged run of bookings.
It now separates what is coming up from what has already happened, and both
lists reach all the way back through imported history from your previous
system.

Staff can narrow the list to a date range, a single class type, one teacher,
one location or one brand, and to a single status such as attended, cancelled
or no-show. The first page also carries a small summary: how many visits in
total, how many attended, how many cancelled (with late cancellations broken
out), how many no-shows, and the attendance rate across the visits that could
have been attended. Those numbers count the whole filtered list, not just the
page on screen.

Each row now says how the booking was made — through the website, the client
app, the desk, the register, ClassPass, as a guest, or imported from the old
system — and whether a pass paid for it. Where there is no pass and no linked
payment, the row says so plainly rather than guessing at "unpaid".

Every row also carries exactly which actions apply to it, so the app only
offers what the server would actually accept: cancel a confirmed booking,
take someone off a waitlist, move a booking to a different pass, check them in
or mark a no-show on today's classes, and correct attendance on today or any
past day. Imported rows stay read-only and point back to the web page.

Correcting attendance can now tell the client. It starts on "Don't notify",
and staff choose Email, SMS or Push per correction; a channel the client
cannot receive is shown with the exact reason and cannot be selected. The old
behaviour, where a stored preference could send on its own, is gone.

One security fix rides along: when transferring a pass to another client, the
Business app now confirms the recipient belongs to your venue before it checks
anything about their contact details.