Diagnostic guide
Two calendar entries can hide different kinds of conflict.
Check what resource was reserved, which system owns the appointment and how the two requests arrived.
Reviewed October 16, 2026 ยท Faith Forge Labs
Identify the actual constraint.
In a fictional example, two staff members are free but both appointments need the same room. Staff availability alone allows an impossible choice. List every required person and resource, including setup or travel buffers.
Compare request and confirmation times.
Two customers can view the same available slot before either finishes booking. Review whether the system checks and reserves capacity when it commits the appointment, rather than relying only on the earlier availability screen.
Separate the booking from calendar copies.
Find the owning record and its status. A delayed or failed calendar update can make connected views disagree without changing the stored reservation. Staff need to see and resolve that failed update.
Check changes and timezones.
Confirm that a reschedule releases the correct old reservation and creates only one current appointment. Record the named timezone and displayed time on both sides, particularly around daylight-saving changes.
Prepare a safe incident note.
Use appointment identifiers, relevant times, the required resource and expected versus actual behavior. Keep private customer details out of an initial inquiry. Reproduce with fictional bookings and approved test recipients rather than repeatedly contacting customers.