Appointments & reminders
Book by stylist, by chair or by room, hold the slot properly, and remind the customer before they forget.
The problem
A diary that any staff member can overwrite, on a phone that gets passed around, is not a booking system. It is a suggestion. The cost shows up as an empty chair on a Saturday.
Two clients booked into the same stylist at the same time
A ninety-minute colour booked into a thirty-minute gap
No-shows nobody chased because nobody was sure who was expected
In practice
Capabilities
A booking holds a stylist, a chair or a room — whichever is actually the constraint. A colour that needs a basin and a chair holds both, so the diary cannot promise something the floor cannot deliver.
A reminder is queued when the booking is made, not when someone remembers. Delivery is logged, so "we sent it" is a fact rather than a claim.
A three-hour balayage that no-shows costs a day of margin. Ask for a deposit on high-value services only, and let it settle against the final bill automatically.
When a cancellation lands, the slot does not just sit empty. Anyone waiting for that stylist and service is surfaced immediately, in the order they asked.
0
Resource types a booking can hold
0 taps
Appointment to open session
0
Reminder queued per booking, automatically
0
Double bookings the diary will accept
The flow
Pick the service; the diary only offers times where the stylist, chair and duration all actually fit.
The resource is locked. A deposit is requested if the service rules ask for one.
Queued at booking, sent in the branch window, and logged when it lands.
Convert the appointment into a live session in one tap — the services are already on the ticket.
Questions
Not yet — bookings are taken by staff today. The resource model and deposit rules were built first because self-service booking on top of a diary that can double-book only spreads the problem.
Keep reading
Set up in an afternoon. Cancel whenever.