Core Operations
Booking and calendar control for service teams.
Manage appointments, staff or resource availability, booking status, reschedules, cancellations, and no-shows from the same console your team uses for customer history and checkout.
View
Calendar, board, list
Linked to
Customer and checkout
Capacity
Staff and resources
AI role
Assistive intake
Day timeline
Today, front desk view
09:00
Maya Tan
Consultation
10:30
Jon Lim
Follow-up visit
12:00
Priya K.
Package session
Status board
Capacity check
The gap
What breaks when booking is separate
01
Schedules drift from customer context
Staff have to jump between calendars, customer notes, receipts, and chat history to understand the appointment.
02
Capacity gets treated like a price list
Rooms, chairs, machines, staff, and equipment need operational scheduling separate from sellable services.
03
Status is unclear before checkout
Arrivals, no-shows, cancellations, and completed visits need visible state before the final bill is closed.
04
Booking does not flow into checkout
The booked service should start the bill, but staff still need to adjust what actually happened.
Core capabilities
What booking operations cover
A daily operating layer for schedule visibility, capacity assignment, booking status, and the handoff into checkout.
Calendar and live board
View today's bookings in the format your front desk and service team can act on.
- Customer, service, time, and staff/resource stay visible together.
Booking status workflow
Track the appointment from scheduled through completion.
- Arrived, in progress, cancelled, no-show, and completed states stay clear where supported.
Staff and resource availability
Assign appointments to the operational capacity needed to deliver the service.
- Staff, rooms, chairs, machines, or equipment stay separate from sellable services.
Customer context
Open the customer record from the booking before the visit or checkout.
- History, notes, packages, membership, and follow-up state are available where supported.
Booking to checkout
Move from booked service to final bill without losing context.
- Start from the booked service, then adjust the final bill when the visit changes.
AI assist boundary
AI can help with intake and safe reply drafting where enabled.
- AI stays behind availability rules, staff control, confirmation policy, and audit requirements.
How it runs
From booking to completed visit
Appointment created
The booking connects customer, service, time, and staff/resource context.
Day is managed
Staff view the booking in calendar, board, or operational list form.
Status changes
Arrival, in-progress, cancellation, no-show, or completion state is recorded where supported.
Checkout starts
The booking context carries into the staff-managed final bill and receipt.
Every step is tracked, every outcome logged — nothing disappears.
The result
Appointments stay connected to operations.
Booking, customer, service, resource, and checkout context stay together.
Staff can see what is happening today without reconstructing it from chat.
Operational capacity is treated separately from sellable services.
AI stays an assistant, not the owner of booking control.
Built for your business
See how it works in your industry
Ready to see how Runbook would work for your business?
We’ll walk you through the workflow, show how enquiries move from message to action, and help you evaluate the best starting setup.