Fixes for common issues with the amenity booking overhaul: blocked bookings, missing multi-day options, vendor tickets not created, and deposit reminder emails.
Last updated
If you try to book a time that overlaps another reservation, or that falls inside the required after-service cleaning buffer right after another booking, you'll see a message that those dates or times aren't available.
Residents: this is always a hard block. Pick a different time or date. There's no way to override it from the resident app. If you believe the time should be open, contact your building staff.
Staff: you can override a buffer or boundary conflict (not the maximum overlapping-bookings cap) from the booking wizard by entering a reason. See the "Booking with Overrides" article for the exact steps.
This can happen for two reasons:
Your property hasn't turned on multi-day bookings for this amenity. Contact your building staff to ask about enabling it (requires a KORE or PREMIUM property).
Your property was recently downgraded below KORE. Any multi-day bookings made before the downgrade are still honored, but new multi-day bookings are blocked until the property is back on KORE or PREMIUM. You'll see a notice explaining this if staff try to create one.
Check the following, in order:
Was the booking cancelled or never confirmed? Vendor rules only fire when a booking is confirmed. A cancelled or voided booking never creates a service ticket or notifies a vendor.
Was vendor notification turned off for this specific booking? Staff creating a booking manually can toggle off "Auto-create vendor service tickets on confirmation" for just that one booking, without changing the underlying rule.
Does a matching rule actually exist for this amenity? Check the Vendor Rules tab on the amenity to confirm a rule is set up, and that its price gate (if any) matches what was booked.
Reminder emails stop as soon as your payment is confirmed, and you'll receive a separate confirmation email once it processes. If you receive one more reminder shortly after paying, it was likely already queued to send before your payment was recorded, and it can be safely ignored.