How to organise online appointments without resource conflicts
An online calendar needs to reserve the time and resources required for the service. Showing a free time is insufficient when a professional, room or equipment is also needed. This guide helps prepare booking, confirmation and change rules so customers and staff receive consistent information.
By the end, you can:
- Define resources and availability
- Handle confirmation and cancellation
- Test conflicts and time zones
Define what an appointment occupies
List services with duration, preparation, the following interval and required resources. Distinguish the time shown to customers from the time blocked in operations. A 45-minute session may need another 15 to prepare the room for the next session. Customers do not need to carry out that preparation, but availability must account for it.
In a fictitious training-studio example, an individual session requires a trainer and a room. A group session uses the same room but has capacity for six participants. These are different rules: in the first case the resource is exclusive; in the second, new registrations can join the same session up to the limit. Do not treat both services simply as blocks of equal duration.
| Fictitious service | Occupancy | Condition |
|---|---|---|
| Individual session | 45 min + 15 min preparation | A free trainer and room |
| Group session | 60 min + 15 min preparation | Session created and up to six participants |
| Technical visit | 60 min + defined travel time | Available technician and location served |
Calculate availability as an intersection of conditions
Publishable times result from combining opening hours, professional availability, resource capacity and service rules. Add holidays, public holidays, breaks and occasional blocks. Define minimum notice, the future booking limit and who may make an exception. The rule should be centralised for the website and staff.
Google Calendar’s free/busy API returns busy periods from calendars. That query is a source of availability, not a reservation of the interval. If booking depends on several systems, confirm which mechanism decides final occupancy and how a conflict discovered after the query is resolved.
Give request, reservation and confirmation clear meanings
Choose the states the process uses: request received, temporary reservation, confirmed, completed, cancelled or no-show. Do not present final confirmation if approval or an unfinished operation is still required. Customers need to know what is guaranteed and the next step.
If a temporary reservation exists during form completion or payment, define its duration and release on expiry. Before confirming, check conditions again and apply the concurrency rule. Two people may choose the same time almost simultaneously; confirmation must respect agreed capacity even if both saw availability.
The confirmation message should originate from a saved appointment with an identifier. Failure to send the message should not automatically create a second appointment. Provide a way to check status or contact staff when customers do not receive the expected confirmation.
- Choose
Show service, time, time zone and conditions.
- Validate
Review resources, capacity and necessary data.
- Save
Create the appointment with the correct state.
- Inform
Send confirmation and a way to manage the appointment.
The journey should include failure recovery and release of temporary reservations.
Treat time zones and repetition as service rules
State the time zone when presenting times, especially where customers and staff may be in different countries. Google Calendar documentation uses IANA identifiers such as Europe/Lisbon and distinguishes timed events from all-day events. Saving only “10:00” loses information needed to interpret the commitment.
For a recurring activity, decide whether the intention is to maintain the service’s local time or the same instant in a global reference. Clock changes may alter the relationship between time zones. Test dates near those changes and show the final time before confirmation instead of applying a fixed offset all year.
When changing a series, distinguish one occurrence, this and following occurrences, or the entire series according to implemented functionality. Google recurrence documentation separates series, instances and exceptions. Users should understand exactly which appointments will change before performing the action.
Prepare cancellation, rescheduling and reminders
Define who may change an appointment, until when and with which operational consequences. Present relevant conditions before confirmation. If payment exists, cancellation rules must connect to the corresponding process; changing calendar status does not demonstrate that a refund was made.
When rescheduling, reserve the new interval according to capacity rules and release the old one consistently. Update reminders so they do not send the old time. Messages should include the service, date, time zone where needed and useful instructions without exposing private details in shared calendars or notifications visible to others.
Choose the system responsible for appointments and document how copies synchronise. A change in an external calendar may not reach the website immediately. Define what staff see when synchronisation fails and how they avoid accepting new commitments on outdated information.
Test a calendar with conflicts, not only empty times
Use fictitious professionals, resources and customers. Make a normal appointment, one ending close to closing time and another conflicting with preparation or holidays. Test the same journey on mobile and confirm customers can correct data without unnecessarily losing their chosen time.
Include two concurrent attempts for a session’s last place. Check final capacity and both messages. Also test cancellation, series changes and confirmation failure. An approved calendar should let you explain each attempt’s state without relying on scattered messages.
| Test | Expected result |
|---|---|
| Last time of the day | Duration and preparation fit within permitted hours. |
| Room occupied, professional free | Do not offer the incompatible interval. |
| Two attempts for one place | Respect capacity without ambiguous confirmation. |
| Confirmed rescheduling | Old time released and reminders updated. |
| Date with a clock change | Time and time zone presented consistently. |
| Message not delivered | Appointment can be checked without automatic duplication. |
How do you compare two calendars for a salon or practice?
Ask to see the journey from the perspective of reception, the professional and the person booking. Use the same fictitious times in both calendars. Record the result observed in each and who needed to intervene.
In a salon, try a service with stages. In a clinic, if you also provide remote consultations, test joining the call. For testing, a fictitious team and a second person acting as customer or patient are sufficient.
| Fictitious test | What to do | What to check |
|---|---|---|
| Colouring followed by a cut | Book the colouring and observe availability while the colour develops. Try booking another customer during that period. | The professional is free only during the salon-defined interval and is reserved again for the cut. |
| Time change | Reschedule through the customer link. Check the professional’s calendar and confirmation message. | The old time becomes available and the new message refers to a single appointment at the correct time. |
| Remote consultation at the practice | A colleague opens the link on a phone and the professional joins through their own access. Also try denying microphone access. | The patient finds the waiting room, understands when admitted and knows how to restore sound. |
Deliver a rules worksheet before configuration
The worksheet should be understood by the person configuring the tool and those receiving customers. Start with a service and resource set that allows operation to be observed. Then adjust rules from specific occurrences while preserving the history of already confirmed appointments.
Worksheet for your project
Online appointment worksheet Services, duration and preparation: Professionals, rooms, equipment and capacity: Opening hours, breaks, holidays and blocks: Minimum notice and booking horizon: Displayed time zone and recurrence rule: Appointment states and meaning of confirmation: Temporary reservation and release: Rule for simultaneous attempts: Cancellation, rescheduling and responsibilities: Messages, reminders and included information: System responsible and synchronisation with other calendars: Tests of conflicts, time zones, failures and capacity: Person responsible for operations and review:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
