To reinstate future bookings that were canceled (or marked as a no-show) up to one day after the original check-in date. This feature will simplify the procedure of amending booking that were not meant to be canceled. It will boost efficiency since clicking on a reinstate button, it is easier than creating a new booking.

In the date filters, latest date remains in the past after earliest date has been set in the future.

To prevent additional manual work:
MEWS should automatically change the calendar date to a date later than the check-in date selected. For example, check in date 1/1/2021, check out date should default to 2/1/2021 (and not remain to todays date).

Would be good to have the ability to have a mid - stay rate change.
For example New Years eve package and additional nights on a BB rate. Currently have to make two separate reservations?

When a payment request is expired or paid - it is not assigned to any departments.
Can we create a setting that this task automatically is assigned to Front Office?

sometimes you need to alert more than one department and/or people of the same task.
would be handy if you had the opportunity to chose more than one department for the task, or be able to copy it, rather than having to type it all again.

Would be nice if the room number shows up behind the name while using the search bar. If you look up a name now, you have to click on the name before you see the room number.

For properties, only the reservation manager has access to the Rate Management in Mews. So when employees are changing the rate of the booking, they will not be able to know what was the original price of the rate. They will only see from the action log the original rate and not the original price. Properties are pushing not just the original rate but also the original price of the rate in the action log without the products attached.

Due to the actual situation we have a high interest in walk in numbers. At the moment there is possibility to get a walk in figure. It can be only assumed reservations for the same day are walk ins, but its not clear at all. Therefore we request a walk in origin code which can be much better tracked.

When you cancel a group reservation, the tasks attached to one of the reservation will remain active. It would be helpful if tasks can be solved by default after you cancel the reservation

We are migrating all our services to Azure and towards Azure Active Directory for all our users. With this in mind we are looking for information whether Mews can be federated and connected to our AAD for authentication and managing all users directly through our AD rather than managing them from within Mews?

Can we please get a simple number of nights count when viewing/managing a reservation? As simple as placing it next to the "nights" section would be immensely helpful when working with guests, particularly guests who have more lengthy stays. Currently, the only option Mews offers is to manually count or do math, which takes up uneccessary time while interacting with guests, and gets frustrating for such a simple and essential part of that interaction.

Be able to add text to a confirmation of a booking. e.g. add the time of golf arrangement, confirm table reservation, or congratulate on honeymoon etc

When dealing with a booking extension ( checked-in) Mews automatically changes the room allocation to a new vacant room. This does not make any sense as the guest is already in house, and Mews should not be able to change by itself an In-house reservation. This is leading into a lot of check-ins into occupied rooms and therefore, guest complaints.

A list of general notices, birthdays, VIPS etc.

we need a reason - test. We run tests in demo and smoke tests in prod.
Would be great if we can take out cancellation statistics by this reason, in case they were test bookings

Products and services that are bookable during the reservation process should have a Day of Week Restriction.

IE: Hotel wants to offer a product that is only available if a guest is going to be staying over a Tuesday, Thursday or Saturday.

If a guest is going to be checking in Sunday and Checking out Wednesday, the product should display and be bookable.

However, if they are checking in Wedneday & Checking out Thursday, the product should not display and be bookable as they guest wont be in house when the product is offered.

add the payment in the POS MEWS so that we can invoice a product and charge the customer directly (for the bar, the restaurant...).
Can also be used with the TPE MEWS for direct billing.

It makes sense to be able to see not only imminent (Pending) or past-date (Missed) tasks but also upcoming (Future) tasks on the main page ("Tasks" doughnut) - without having to go into the report every single time.

The current state of affairs makes it often necessary to remind staffers of upcoming tasks outside of that section (or outside of MEWS e.g. emails, sticky-notes et al.), which does not make for a stellar user experience.