System to ignore setup and clean down times when calculating room availability
Use case : a user makes a room booking for a date without catering.
A few days before the meeting, he decides to add catering (eg meal trays). Unfortunately, if these services have setup and clean-down times, the system tries to set them up, but if in the meantime the slots before and after are busy (which is often the case), the system displays an incomprehensible error message saying that the room is not available.
To solve this problem ideally the setup and cleandown times should be applied within the booking schedule, and not outside. Because it is more logical that it is planned within the booking itself rather than block times before and after and penalize other users.
Admin LVMH
shared this idea
-
Peter Scobbie
commented
The error messages are indeed not clear and we often face this problem in our business. Unless you are an a experienced user and have been shown what this means before, it is always a bit pointless and often generates a support call.
I do agree in some scenarios that setup and clean down time shouldn't be applied if the services are added within the booking time frame, but in some cases, the services are added at the start and collected at the end of the meeting where this needs to be added.
I have asked this many times and the answer I receive every time is that it's inordinately complex to design this login into the system. Personally coding something like this wouldn't be too difficult if you were to discuss with service vendors and reception teams about how this should and could be implemented.
-
Kelli Kane
commented
This has been an on going issue for my company as well. The error message "endpoints not available" seems to be catch all for all errors and is meaningless.