Settings and activity
33 results found
-
12 votes
Hello all,
This status update is part of our ongoing work to simplify and streamline how our UserVoice feedback forum operates. We are reducing the number of statuses to two (Idea to Upvote + Released) to help manage expectations about where each idea stands and to minimize the number of status updates required from our product teams. Our product team reviews everything you share, and we might reach out for more info if we need it.
Thanks for your patience as we work to bring your ideas to life! You can learn more about the changes coming to UserVoice from this post in the Mews Community.
An error occurred while saving the comment 
Leo Blouin
supported this idea
·
-
73 votes
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.
Leo Blouin
supported this idea
·
-
124 votesLeo Blouin
supported this idea
·
-
1 vote
An error occurred while saving the comment Leo Blouin
commented
We’re running into the same issue almost daily. A guest checks into a room, stays only a few minutes or an hour, then switches to another room. Mews immediately flips that first room back to “Dirty,” even though it was fully cleaned and inspected earlier that day.
Housekeeping ends up wondering why a clean room suddenly looks like it needs a full turnover when, in reality, it only needs a quick touch-up. It slows the team down and creates unnecessary backtracking.
What we really need are two things:
1. Automatic “Pickup” logic for short occupancy
In another PMS, this would fall under a Pickup status, meaning the room was used lightly and only needs a refresh, not a full clean.
Mews could handle this with:
• a “Pickup” status, or
• an automated rule triggered when the guest stays in the room less than X hours, or
• any system tag that prevents a fully cleaned room from coming back as “Dirty” when the use was minimal.2. A report showing all room changes for a selected period
To better understand patterns and support housekeeping, we need a simple audit that shows:
• every room change
• timestamps
• who triggered the change
• original room → new roomThis would help us catch problem patterns, reduce confusion for the team, and avoid double work.
Both improvements would make day-to-day operations smoother and give housekeeping a clearer picture of what actually happened during the shift.
Leo Blouin
shared this idea
·
-
36 votes
An error occurred while saving the comment Leo Blouin
commented
It should be a grid-like table, with each line representing an action divided by columns. The columns should have the following headers: action name, date, time, user, before value, and after value.
This way, when we search for the last time a reservation’s space allocation was changed by +10 log, it will take only 2 seconds. The action would be clear, and we could simply look at the value we’re searching for to find the room number.
Leo Blouin
supported this idea
·
-
2 votesLeo Blouin
supported this idea
·
-
15 votesLeo Blouin
supported this idea
·
-
2 votes
An error occurred while saving the comment Leo Blouin
commented
That would be fantastic! We often have over 200 arrivals daily, and people end up waiting in line. This way, they can occupy themselves and, when they finally reach the desk or kiosk, they can simply grab the key and go
Leo Blouin
supported this idea
·
-
8 votesLeo Blouin
supported this idea
·
-
3 votesLeo Blouin
supported this idea
·
-
5 votesLeo Blouin
supported this idea
·
-
20 votesLeo Blouin
supported this idea
·
-
2 votesLeo Blouin
supported this idea
·
-
11 votesLeo Blouin
supported this idea
·
-
12 votesLeo Blouin
supported this idea
·
-
12 votesLeo Blouin
supported this idea
·
-
4 votesLeo Blouin
supported this idea
·
-
5 votes
An error occurred while saving the comment Leo Blouin
commented
We have a very low government rate and need to verify their work ID. They can easily bypass this by using the kiosk
Leo Blouin
supported this idea
·
-
105 votesLeo Blouin
supported this idea
·
-
228 votesLeo Blouin
supported this idea
·
Adding a grace period would also be helpful.
In the marketplace integration setting to add a grace period, like 15 minutes after checkout time, so people who arrive a bit late for C/O don’t have to return to the desk to speak to reception to re-do the key to grab their luggage.
This is especially useful for kiosk-only properties.