Written by 4SYSTEMPublished on Updated on
7 min read
Reliable booking starts with capacity and availability rules, followed by confirmations that reflect the actual status of each request.
To organise online booking, first define what customers reserve: a person, a place, a room or several resources together. Then specify duration, capacity, unavailable periods and confirmation conditions. The visible calendar must reflect these rules. A slot shown as free must not become a promise if the team still needs to review the request.
Remember that availability results from rules, not simply a list of times. Distinguish the offered start time, the resource actually occupied and the booking status. This separation makes exceptions manageable without improvising each customer message.
Define online booking rules
Start with the unit being booked. An individual appointment consumes a staff member's availability; a group workshop consumes places; a service may require both a room and equipment. Include telephone bookings too. Unless they enter the same inventory, the public form cannot know the capacity actually remaining.
Separate service duration from the interval between offered start times. Microsoft Bookings documents these settings separately: a start interval does not define appointment duration.[1] Add preparation or recovery time and specify the time zone. These operating decisions should be written down before customising the calendar's appearance.
Choose how availability is calculated
Assign priorities to rules. Normal opening hours provide a baseline; an exceptional closure should override them; an unavailable resource must remain blocking. The grid identifies what needs configuration, synchronisation or manual approval. It does not assume one tool covers every case.
| Booking requirement | Booking decision | Expected booking check |
|---|---|---|
| Individual appointment | Required staff member and actual duration | No overlap for the same person. |
| Group workshop | Capacity and requested places | The final place cannot be sold twice. |
| Shared resources | Essential room or equipment | An occupied resource blocks the slot. |
| Dated exception | Closure or special opening hours | The exception overrides the usual rule. |
Microsoft Bookings describes date ranges overriding general availability and buffer time included in availability calculations.[2] Check this behaviour in the selected solution, especially with multiple calendars. An advertised synchronisation feature alone does not explain propagation speed or how conflicts are resolved.
Build booking states and messages
Write booking states before message templates. A received request, a temporarily held place and a confirmed booking must not share the same label. Specify which action moves a booking between states.
- Define the source of truth for places and resources. Explain how manual bookings enter it and who can correct errors.
- Set booking, amendment and cancellation deadlines. Specify whether they use elapsed hours or opening hours.
- If places are held temporarily, define expiry and release. Also handle payment or approval arriving after expiry.
- Write confirmations stating the service, date, time zone, location and amendment procedure. A pending request must remain explicitly pending.
- Name the alert recipient and exception owner. Prepare a response when customers do not receive messages or enter an incorrect address.
These rules complement a usage-led website specification. Add boundary cases and the expected decision for each. The aim is to let staff understand why a booking was accepted or refused without needing a technical explanation for every incident.
Fictional example: a capacity-limited workshop
Entirely fictional example: a workshop has 6 places and requires a tutor and a room. The session lasts 45 minutes, with 15 minutes of room preparation. The form submits a booking request, followed by confirmation after approval. A telephone booking must consume the same capacity as an approved online request.
Two people may try to book the final place. Final approval must recheck capacity and, if necessary, decline one request clearly. An exceptional closure must not silently cancel confirmed bookings: staff must identify them and contact those affected. This example prepares scenarios; it describes neither an installation nor tests performed.
Check conflicts and exceptions
Acceptance checks should examine states and messages together. Microsoft Bookings documents email confirmations and reminders, plus a maximum-attendee setting for group services.[3] These documented possibilities do not establish that your activity's particular rules are already configured correctly.
- Submit simultaneous requests for the final place, then check final capacity and the messages sent to each person.
- Add exceptional unavailability and a manual booking, then check their effect on the customer-facing calendar.
- Amend or cancel a booking and check released capacity, history and consistency with earlier notifications.
- On mobile, check the displayed time zone, recovery after an error and access to the amendment link in the received message.
Also check fields, buttons and messages using the keyboard. The keyboard and mobile accessibility guide complements this review. Keep expected and observed results, particularly where an external calendar or notification service forms part of the journey.
Frequently asked questions
Should every booking be confirmed immediately?
No. Confirmation may depend on approval or another stated condition. From the form onwards, customers must understand whether they are booking or submitting a request. An acknowledgement must never be written as a definitive confirmation.
How should holidays and closures be handled?
Use dated exceptions rather than improvised changes to normal opening hours. Review confirmed bookings before applying a closure. Specify who informs customers and how amendments are offered, without assuming the calendar does this automatically.
Is a reminder enough to prevent no-shows?
A reminder can convey useful information but does not guarantee attendance. Check its recipient, content and amendment link. Do not promise fewer no-shows without actual measurement; also plan for incorrect addresses and undelivered messages.
Prepare booking that the team can manage
Online booking needs explicit capacity, timing and confirmation rules. Gather your services, exceptions and scenarios requiring human intervention. To scope the journey with 4SYSTEM, present them through the servicespage. This allows responsibilities and checks to be discussed before selecting a calendar or promising automation.