Handling Conflicts and Double-Bookings
A double-booking is when two reservations claim the same asset on overlapping dates. It's the worst customer experience in any reservation business — two people show up to the same site, same slip, same cabin. The system is designed to prevent this in normal use, but it's worth knowing what the safeguards are and what to do if one slips through.
When you'd use this
Read this if:
- You're about to go live with reservations and want to understand the safeguards.
- You've just had a conflict and want to figure out how it happened.
- You're training staff and want them to know the rules of safe booking.
How conflicts are prevented
Three safeguards work together every time a booking is created.
Safeguard 1: The availability check
Every booking through the wizard checks availability before the asset is committed. If the asset is already booked on any of those dates, the wizard returns "not available" and won't let the booking proceed.
Safeguard 2: A short hold during checkout
When a customer starts checkout (public booking) or staff begin a booking (internal), the asset is held for a short time window — typically 10–15 minutes. During that window, no other booking can grab the same asset, even if two customers started looking at it at the same moment.
If the customer abandons checkout (closes the browser, fails payment), the hold expires and the asset returns to the pool. If they complete checkout, it becomes a real reservation.
This catches the case where two people click the same slip within seconds of each other.
Safeguard 3: A final conflict check at confirmation
Right before a reservation is saved, the system looks one more time for any overlapping reservation on the same asset. If something somehow slipped past the first two safeguards, this final check catches it and surfaces a warning to staff instead of writing a duplicate booking.
Why double-bookings still happen occasionally
Despite the safeguards, real double-bookings sometimes appear. The usual causes, in rough order of frequency:
A reservation moved to a now-occupied asset
Staff moved Reservation A from Asset X to Asset Y to accommodate a customer request. Asset Y was already booked by Reservation B for some of those dates. If staff overrode the conflict warning, both reservations now claim Asset Y on overlapping dates.
Lesson: Don't override the conflict warning when reassigning assets. If the only available asset is one with overlap, that's a conversation with the original tenant, not an override.
Reservations imported from a previous system
When you imported historical reservations from a previous system, that import may have been more forgiving than the booking wizard. Two existing reservations on the same asset on overlapping dates can survive an import.
Lesson: Run a one-time conflict report after any data import. Resolve any flagged conflicts before going live.
Reactivating an asset that had old reservations on it
If you mark an asset inactive and later reactivate it, reservations that were sitting dormant on it can suddenly overlap with new bookings.
Lesson: Be careful when reactivating assets. Check for any old reservations on it before opening it back up.
Resolving a conflict when it happens
If the system surfaces an actual double-booking — two reservations both claiming the same asset on overlapping dates — work through this fast:
Step 1: Confirm the conflict is real
Pull up both reservations. Verify the asset is the same, the dates overlap, and both are confirmed (not cancelled, not pending). Sometimes the alert is a false positive (e.g., reservations on different assets that share a name, or back-to-back stays where check-out and check-in fall on the same calendar day).
Step 2: Identify which booking is "right"
Usually the older booking takes precedence — first come, first served. Sometimes the newer booking has paid in full while the older one hasn't paid the deposit, in which case the older one might be the one to move. Sometimes both have paid, both are confirmed, and you have a real problem.
Step 3: Find an alternative for the displaced customer
Pull up the timeline and find a comparable asset for the affected dates. If you have one, the resolution is to call the displaced customer, apologize, explain the situation, and offer the alternative — ideally with an upgrade or partial refund as goodwill.
Step 4: Apologize like you mean it
Whichever customer gets moved is going to be unhappy. The right response is genuine apology and a meaningful concession (free night, complimentary upgrade, future-stay credit). The cost of those concessions is far less than the cost of a furious customer reviewing you online.
Step 5: Document what happened
Record the conflict, the cause, the resolution, and what you'll change so it doesn't happen again. If the cause was an override warning that shouldn't have been clicked, retrain staff on conflict warnings. If it was a stale reservation on a reactivated asset, add that check to your reactivation routine.
Recommended defaults
- Always book through the wizard or the reservation edit screen. They run the safeguards. Shortcuts skip them.
- Treat conflict warnings as stop signs, not yield signs. The default reaction to a conflict warning is "stop and figure out why," not "click through."
- Run a weekly conflict report during peak season to catch anything that slipped through.
- Escalate immediate-future double-bookings (in the next 7 days) to a manager for resolution. Don't let staff handle these alone — the customer experience is too important.
- Don't try to "split the difference" by giving each customer half the stay. They both wanted the full stay; one needs to be moved entirely.
- Track root cause. Every double-booking has a cause. If you don't fix the cause, the next one is coming.
Common mistakes
- Overriding conflict warnings. The whole point is that overriding makes the problem invisible until customers arrive at the same site.
- Skipping the booking wizard for "quick" changes. The wizard and the reservation edit screen are what run the safeguards. Adjusting reservations any other way leaves you exposed.
- Not training staff on the difference between "asset moved" and "dates moved." Each operation runs the availability checks a little differently. Staff need to understand both.
- Treating a double-booking as a single mistake. It's almost always a process failure (an override pattern, a missed step at reactivation, a stale import). Fix the process, not just the symptom.
- Apologizing weakly. A double-booking is a serious customer-experience failure. "Sorry about that" with no concession comes across as dismissive. Make a real gesture.
- Hiding double-bookings from leadership. Owners and operations managers need to know when these happen. Hiding them prevents process improvement.
- Solving with a discount alone. A 10% discount doesn't fix a customer arriving to find their site occupied. They need an alternative site of equivalent quality, plus the discount, plus a sincere apology. All three.