Run appointments, walk-ins, and capacity in one live queue.
Replace the whiteboard with a live schedule and queue that understands resource capacity.
Front-desk order for a service business: capacity-checked bookings, a live queue with wait estimates, and a timing history that remembers every delay and extension.
For appointment and walk-in teams balancing people, rooms, equipment, and customer wait times.
Protect capacity before the booking reaches the front desk.
Booking treats staff, rooms, chairs, beds, and equipment as real constraints, then keeps the day moving in one queue.
- Capacity checks
- Validate the attendee, resource, time, duration, and buffers before saving so conflicting work is rejected at the source.
- Appointments + walk-ins
- Place scheduled customers and walk-ins into the same operating queue without losing their different arrival context.
- Deterministic waits
- Update positions and estimates from the actual queue and service timing instead of presenting an unexplained prediction.
- Timing history
- Retain check-in, call, start, completion, delay, and extension events for operational review and customer disputes.
This is Booking.
Built from the product's own components and design tokens — the spacing, density, and status colours here are the ones you get after signing in.
Live queue
- J. Lim · Cut and finishChair 2 · started 2:41 pmIn service
- S. Kaur · ColourChair 1 · started 2:05 pmIn service
- Walk-in · 2:38 pmNo appointment · next available stylistWaiting
- R. Chen · TreatmentBooked 3:15 pm · room capacity confirmedScheduled
See the day by time and resource.
Replace the whiteboard with a live schedule and queue that understands resource capacity.
Define capacity once; make each booking a few decisions.
Resources hold the reusable rules. Staff choose the attendee, service, resource, and time while availability handles the rest.
Capacity checked before saving
Bookings validate against your rooms, staff, and equipment — double-booking is rejected at the source.
A queue that runs the floor
Check in → call → start → complete, with live wait estimates and positions, refreshed automatically.
Every timing change remembered
Delays and extensions stay with the booking as an audit trail — useful the day a customer disputes one.
Setup in plain language
Resources are “people, rooms, beds, or equipment”; appointment types carry durations and buffers that “protect preparation and turnover time.”
The mechanisms behind Booking.
Not features — the guarantees. Each one is enforced in the product rather than promised in a policy.
- Capacity is checked, not assumed
- A booking resolves the attendee, the service, and the required resource together. If the room or the chair is not free, the slot is not offered.
- Resources are reusable rules
- Rooms, chairs, equipment, and staff are defined once with their own availability, so every booking inherits the constraint instead of restating it.
- One queue for both
- Scheduled appointments and walk-ins move through the same states — waiting, called, in service, complete — so the floor has one truth.
- Timestamps make it improvable
- Wait and service times are recorded at each transition, which turns “today felt slow” into a specific point where the floor actually stalled.
Better together.
The modules share one organization record — connections are built in, not integrations to configure.
Evaluating Booking? Start here.
Direct answers about local fit, controls, and how the module works with the rest of ThePlatform.
- Can Booking manage both appointments and walk-ins?
- Yes. Scheduled bookings and walk-ins enter the same live queue while retaining their own attendee, service, and arrival details.
- How does ThePlatform prevent double-booking?
- A booking is checked against the capacity of its assigned staff, room, chair, bed, or equipment before it can be saved.
- How are queue wait estimates calculated?
- Estimates follow the current queue, service durations, and timing state. The product keeps the underlying timeline so the estimate can be reviewed later.
- Does Booking collect payments?
- Payments are not part of the current Booking workflow. The module focuses on capacity, appointments, walk-ins, queue operation, and timing history.
Run the calendar and the floor as one system.
Put Booking to work inside the same platform as the rest of your operation.