The five states
Every booking moves through a small, closed state set. The database enforces the valid values, and the operational surfaces are built around exactly these five.
| State | Meaning | Typical transition |
|---|---|---|
| pending | Created, awaiting confirmation conditions (e.g. payment or manual confirmation) | → confirmed when conditions are met |
| confirmed | Ready to happen: slot held, staff and resource committed | → completed, cancelled, or no_show |
| completed | The appointment happened | Terminal |
| cancelled | The appointment will not happen, policy-applied | Terminal; slot released |
| no_show | The appointment window passed without the customer arriving | Terminal; policy may apply |
What a booking connects
A booking is the intersection point of the whole model: it references the customer, the service, the staff member who owns it, the resource it consumes, the location, and the reminder waves planned for it. When any of those changes — a reschedule moves the time, a cancellation releases the slot — the connected objects update consistently because the change flows through the same booking API that created it.
Customer self-service
Customers manage their own bookings through the token in their confirmation link: they can cancel or reschedule without logging in. Token endpoints validate the token and the booking's tenant on every request, so a customer link can never reach another tenant's data and a stale link simply stops working.
Changes are operational events
A moved booking retains its reason or policy path, shows old and new state where appropriate, and makes ownership visible. A cancellation follows the approved policy. The system does not claim to prevent no-shows automatically — that is an operational decision the business makes.