Booking events
What happened to a booking — in plain words
Salons fill in Altegio in different ways: some delete the booking, others mark it “no-show”. The platform looks not at the current status but at the change log: what changed and when — before the visit started or after. So the same events are counted the same way in any salon.
before the startLive
Cancellation
The booking was deleted or marked “no-show” before the visit started — in any way: by the client in the bot, by the administrator or by an integration. Who cancelled is recorded in the event.
Why it matters: The administrator has time to save the visit or fill the slot.
less than N hours beforeLive
Late cancellation
The same cancellation, but late: less than N hours before the visit (48 by default, changeable in settings).
Why it matters: The owner sees the specialist’s lost hours, the administrator sees which slots to fill urgently.
after the startLive
No-show
“No-show” or deletion after the visit has started, if it wasn’t marked “arrived” before.
Why it matters: Shows how many visits are lost without warning.
after the visitPlanned
Not marked
The visit time has passed, but the status is still “pending” or “confirmed”. It’s neither a visit nor a no-show, but a gap in the records.
Why it matters: We don’t move the stage or guess; the owner sees how many bookings aren’t marked and can put things in order.
same bookingLive
Reschedule
The day was changed in the same booking: one booking, new date.
Why it matters: This isn’t a lost visit.
cancellation + new bookingLive
Saved visit
The booking was cancelled, but within N days (7 by default) the client booked again in the same direction.
Why it matters: An administrator who persuaded the client to reschedule rather than cancel sees it in their numbers.
new bookingIn progress
Booked
The person has booked, but the visit is still ahead. We wait to see whether they come.
Why it matters: We don’t count a return on a promise; a booking after a reminder is a separate metric.
visit after a breakIn progress
Returned
A visit took place after “time to come back”, “sleeping” or “gone”. Rhythm is back to “in rhythm”, experience isn’t reset.
Why it matters: We measure a return by the visit — that shows whether reminders and tasks worked.
booking aheadLive
Future booking
A booking for a time later than now — not deleted, not marked “no-show”, at any branch in the network.
Why it matters: The platform doesn’t send comeback reminders to someone who’s already booked.
Reschedule or saved visit?
RescheduleOne booking — only the date changed.
Saved visitThe booking was cancelled, and a few days later a new one appeared. These are two events; the credit goes to whoever created the new booking.
And a visit is client × day × branch where at least one booking is marked “arrived”. Three services in one trip — one visit.