Settings and activity
3 results found
-
129 votes
Hey everyone!
I'm happy to announce that we're currently working on various improvements around Routing Rules 👏 We've significantly scaled the solution from continuous and monthly routing to route additional services through integrations to cover many use cases and we're now in closed beta.
If you're interested in finding more or join the beta testing to share your feedback, please, reply to the email.
Alvaro Bautista
supported this idea
·
-
71 votes
We reopened this request for further upvotes. It is fairly clear what is being requested and it will need more investigation from Mews. In the mean time we would ask you to continue to up vote if this is still a required connectivity feature request.
An error occurred while saving the comment Alvaro Bautista
supported this idea
·
-
11 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.
Alvaro Bautista
supported this idea
·
In the same way as Marion Leijtens, we use an integration for guest messaging (in our case Hijiffy) with our guests, and we want to send them the link for check-in through Mews, that now can only be sent through the Mews emails. These emails have a low open rate, and therefore no so much people check-in online. I suppose the solution would be to add to Connector API the option to take the data for that link or token associated to that guest/reservation.