Settings and activity
1 result found
-
87 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 
Nell Lindquist
supported this idea
·
This continues to be a real pain point for us. We run a small motel on Mews and integrate with Hello Hotel for guest messaging, and the inability to send a working check-in link outside of Mews's own emails creates friction on every front:
Guests — open rates on the Mews emails are low, especially when they're competing with OTA-masked addresses and overflowing inboxes. We'd much rather send the link via SMS (where open rates are 90%+) but currently can't, because the bare navigator URL dead-ends at a login screen for anyone without an active Mews session.
Our team — we spend time fielding "why am I being asked to log in?" support questions from guests who tap the texted link, when the answer is just "Mews doesn't let us send you the working URL."
I understand the security rationale around the token, but five years into this request, the gap is costing real check-in completions and creating support load on hoteliers. Even an opt-in / scope-limited version of this endpoint would be a meaningful improvement.