Booking flow
Move through a fictional appointment or capacity-based class booking and simulated payment. It is a generic example only: nothing is saved, sent or charged.
Back to website servicesNo booking is created and no payment is taken.
Fictional demonstration business: a finished booking flow would use your branding, services, staff, working hours and customer journey.
- 1Service
- 2Staff
- 3Time
- 4Details
- 5Review
Choose a service
Select an individual appointment or choose from classes already scheduled by the business.
A booking system shaped around the way your team works.
The demonstration creates local browser entries only. A production system would connect to the business’s real accounts and protect customer information.
Live availabilityService duration, staff hours and existing appointments are checked before a time is offered, preventing overlapping bookings.
Classes with capacityGroup sessions can have a fixed number of places. Each confirmed booking reduces the remaining capacity, and the class disappears from availability once it is full.
Private team calendarCustomers see available appointments—not the admin calendar. Staff and team views can connect to the client’s Google Calendar.
Payments and emailStripe payments can go directly to the client-owned account. Booking confirmations, reminders, cancellations and rescheduling notices are sent by email.
Practical infrastructureCloudflare can handle the booking logic and secure records. Google Calendar, Stripe and the client’s Google Workspace address provide the external integrations, with third-party costs confirmed before launch.