Booking Clashes on Go Book
Problem
Customers cannot book a session on Go Book, or join its waiting list, because it overlaps something they have already booked, and you need to know what Go allows and what to test.
Root Cause
By default Go stops a customer booking anything that overlaps an existing booking, even by a few minutes (for example two squash courts, or a court and a class). This includes joining a waiting list for a clashing class.
Resolution
Check the timetable for overlaps
- Back-to-back classes that overlap need programming changes, because Go will not let one customer book both.
Check desk booking settings (if applicable)
- Staff booking in Plus2 or 360 are not bound by the online rules or clash rules, so clashes can still be created at the desk. Check Connect/GMC settings such as allow duplicate bookings.
- Decide whether staff may override the rules and how that is authorised.
Test waiting-list behaviour before go-live
- A customer who is not booked can join several waiting lists for classes at the same time. Once they accept one, they cannot book the others.
- An edge case has been reported where accepting a conflicting alert-list place removed the customer's existing booking. Test this before go-live.
- Also test exact-time and partial overlaps on every customer-facing channel.
Notes
- The clash rule is about overlapping times. Caps on the number of bookings per day come from the booking-limit settings, not from this default: see Booking Restrictions in Go Book.
- Related: Go Book Booking and Cancellation Settings in Operator; GladstoneGo: Alert List Notification Setup; Testing Gladstone Go Before Go-Live.