The popular “Public Booking Request” features of MIDAS allow non-users (i.e. visitors to your website) to check the availability of your venues and submit booking “requests” online. These requests can be quickly approved by an administrative user with just a couple of clicks and converted to “confirmed” bookings, or they can be rejected just as easily.

To make a public booking request, a requestor would go to https://your_midas_url/request. If requests have been enabled they can then select a venue (or venues), date (or dates), times, and resources, and check availability accordingly. They can then enter their details, and any additional details relating to their request and submit their request online.

For v4.15, we’re giving administrators more flexibility when it comes to the initial venue selection step of the Public Booking Request process.

Previously, a requestor would need to manually select the venue (or venues) they wish to request. However, in v4.15 an administrator can instead replace the traditional individual/manual venue selection for Public Booking Requests with automatic venue selection instead.

If the automatic venue selection option is enabled, a requestor simply selects a venue group. MIDAS will in turn automatically select a venue from within the selected group accordingly.

This is ideal if you allow public requesting of similar rooms. For example, if you have 10 identically sized/equipped meeting rooms, a requestor doesn’t necessarily care which one of these rooms their meeting takes place in. These new options would allow them to simply select that they wish to request a “Meeting Room”, and MIDAS will allocate a meeting room accordingly.

How MIDAS allocates venues when the automatic venue selection option is enabled may be configured by an administrative user….

Auto Venue Selection options include:

• Random – MIDAS will attempt to select an available venue at random from the all publicly requestable venues within the selected venue group.
• Venue Order – MIDAS will attempt to select the next available venue from the all publicly requestable venues within the selected venue group, based on the order your venues are configured to appear within MIDAS.
• Least Used (Number of Bookings) – MIDAS will attempt to select an available publicly requestable venue from the selected venue group with the least number of existing bookings in it.
• Least Used (Venue Utilization) – MIDAS will attempt to select an available publicly requestable venue from the selected venue group with the most free time in it (i.e. the least utilized venue)

These exciting new option for Public Booking Requests allow far grater flexibility, make it easier for people to make booking requests, and ensure more balanced usage of your venues!

Inundated by lots of booking requests? Following customer feedback, MIDAS v4.14 includes new “Reject All” and “Approve All” buttons on the Pending Booking Request screen. These new buttons provide an easy way to “bulk reject” or “bulk approve” all outstanding requests.

Clicking the “Reject All” button typically allows you to optionally enter a brief reason why you’re rejecting the requests. This reason will then be included in the rejection email notifications sent to the affected client.

If the “Approve/Reject requests silently” option is selected, clicking “Reject All” shows a confirmation of the number of booking requests to be rejected which if confirmed will then reject all those requests.

The “Approve All” button will also provide an indication of the number of booking requests to be approved. If confirmed MIDAS will then attempt to automatically approve all these requests.

Booking Approval Order

The order that these requests are automatically approved in is important. It may not be possible to automatically approve all booking requests. For example, if two requests are made by two different clients for the same venue and times, they can’t both be approved.

In such instances, a “Bulk Approval Order” setting (found via MIDAS Admin Options → Manage MIDAS → Web Requests) determines the order (priority) in which booking requests will be bulk processed for approval. The four possible options for this setting are as follows:

1. Earliest Requested First (Requests that were made earlier will be approved before requests that were made more recently)
2. Latest Requested First (Requests that were made more recently will be approved before requests that were made earlier)
3. Earliest Commencing First (Requests for bookings starting sooner will be approved before requests that start further in the future)
4. Latest Commencing First (Requests for bookings starting further in the future will be approved before requests that are due to start sooner)

You can read more about some of the other exciting improvements coming in v4.14 here!