Turn open time into momentum.

The Booking Calendar is the second of the module’s two run-the-day screens, and it answers a different question from the first. The list tells you what is booked; the calendar tells you the shape of the time it was booked into — where the work clusters, which days are untouched, and what next week already looks like before you promise anybody anything.

One set of appointments, four ways to read it. Month while you are planning, week while you are working, day while you are running it, and a plain list when reading down it beats looking at it. Every service and every provider lands in the same grid, so the month is the whole business rather than one person’s diary.

Where a booking stands is a colour, not a click. Pending, confirmed, completed, cancelled and the ones where nobody came each own a dot, named above the grid, so a month that is going wrong looks wrong. Nothing has to be opened to be understood.

And what fills this month is decided upstream, on the section this card points at. The hours you open, the buffer between them, the notice you insist on, the daily limit, the days you block — those rules decide which times a customer is ever offered. The calendar is where you find out whether the boundaries you set were the right ones.

Bookings is the run-the-day view of the module: one table holding every appointment across every service and every provider, rather than one calendar per person and an evening spent reconciling them. A row is the whole booking — the service, the provider taking it, the client and how to reach them, the day, the time, the seat, and where it stands.

The list narrows to the question you are actually asking. Upcoming, past, or only today; appointments, connect calls, or both together. The search box takes a client, a service or a provider by name, and whatever you are looking at can be taken out as a file exactly as it stands on the screen.

Status lives in the row. Confirmed, completed, and the ones where nobody came sit in the same column, so a booking that went wrong is something you can see rather than something you find out about. The rows still ahead of you carry their own controls — open the booking, or move it to another time.

And the appointment is only the beginning. The time joins the calendar, the client joins your contacts, the conversation stays attached to the same person, and a confirmed booking can begin the preparation that has to happen before the session does. Nothing is exported into another system and rebuilt there.