Naming stay restrictions
Right now, going through each stay restrictions requires your read each specific variable. However, just each restriction should be able to be named so that we can quickly figure out what each one does by title instead of reading through each variable.
Hello from the Mews product team. Thank you for your suggestion, we have updated your request and set it as one to be upvoted by the Mews Community. Remember you can share a link to your request so that your colleagues can also upvote your suggestion.
-
Neïla Rebrab commented
Hi,
I truly think this is critical for many MEWS users. It is possible to know how likely it is that this feature will be released any time soon? -
Neïla Rebrab commented
This would be incredibly helpful ! It takes a crazy time to figure out to what corresponds each restriction. Especially when planning ahead in the next year !
-
Madelaine McKinnon commented
This would be extremely helpful when we have lots of different restrictions or multiple staff working across the system
Being able to look and say "No sorry, it's a 3 night minimum because there is a popular event on in the city" is more professional than saying "Sorry it's a 3 night minimum and I don't know why" -
Hans Ning commented
An addition to this would be to give a restriction a name as well, which doesn't appear possible. This should be an available option, and not required.
-
Edris Mir commented
Sometimes if you want to achieve a specific thing, you need to set up some not so logical restrictions. It would be a nice feature to be able to write notes on restrictions to be able to understand why you made those specific restrictions in the past.