Booking systems that fill the calendar without filling your inbox.

The part most projects underestimate: availability

The form customers see is the easy part. The difficult part is the model behind it — the rules that decide which times can be booked. Before design starts, it helps to answer four questions in writing:

• What is being booked? A seat in a group class, one person's hour, a room, a piece of equipment, or a combination of them?
• How much can run at once? A class with twelve places behaves very differently from a therapist with one chair.
• What needs space around it? Preparation, cleaning, travel or rest time between bookings.
• How far ahead, and how late? The earliest and latest moments a customer may book, change or cancel.

Getting these rules right is usually worth more than any visual polish, because they decide whether the calendar can be trusted.

What a good first release includes

• A clear list of what can be booked, with duration and price shown before the customer commits.
• Live availability that reflects what is actually free, not a guess.
• A booking form that asks only for what you genuinely need.
• An immediate confirmation, in the customer's language, with the details they will want later.
• Rescheduling and cancelling within the rules you set, without a phone call.
• Reminders before the appointment, which is usually the cheapest way to reduce no-shows.
• An admin calendar where your team can see, edit, block out time and make exceptions by hand.

Waiting lists, packages, memberships and multi-branch rules are real needs, but they are better added after the basic flow has proved itself.

Hong Kong realities: typhoons, holidays and payments

• Typhoon and weather days. When a typhoon signal or a black rainstorm warning disrupts the day, you may need to cancel or move many bookings at once and tell everyone quickly. A bulk reschedule tool and a pre-written notification are far better than doing it one by one.
• Public holidays and shortened days. Availability rules should know about holidays, half-days and seasonal opening hours.
• Payment methods. Customers may expect more than cards — for example FPS or e-wallets. Which methods you can offer depends on your payment provider and merchant account, so confirm this early.
• WhatsApp reminders. Business messages on WhatsApp require consent and approved templates. They work well for reminders when set up properly, and badly when improvised. See our messaging guide.
• Bilingual confirmations. A customer who books in Chinese should receive Chinese confirmation and reminder text, and the other way round.
• Less personal data. Collect only what you need. In particular, avoid asking for Hong Kong ID card numbers unless there is a genuine requirement, and take advice if there is.

What makes a booking system bigger

A single-service booking page is a much smaller project than a multi-branch operation with staff schedules. These factors move the size of the work most:

• The number of different things that can be booked, and how different their rules are.
• Whether staff or resources have their own schedules and skills.
• Online payment, deposits and refunds.
• Connections to an existing calendar, point-of-sale or accounting system.
• The depth of the admin side: reports, blocking, bulk changes, roles.

To get a feel for the size, use the project cost estimator; it treats a booking system as its own project type.

Common mistakes

• Asking for too much on the form, so people abandon it.
• Having no manual override, so staff keep a parallel paper calendar.
• Letting cancellations leave gaps that nobody can refill.
• Sending so many notifications that customers stop reading them.
• Treating the calendar as a design problem when it is a rules problem.