Settings and activity
56 results found
-
48 votes
Eld Leijonhufvud
supported this idea
·
-
37 votesEld Leijonhufvud
supported this idea
·
-
19 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.
Eld Leijonhufvud
supported this idea
·
-
100 votesEld Leijonhufvud
supported this idea
·
-
3 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.
Eld Leijonhufvud
supported this idea
·
-
20 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.
Eld Leijonhufvud
supported this idea
·
-
9 votesEld Leijonhufvud
supported this idea
·
-
60 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.
Eld Leijonhufvud
supported this idea
·
-
3 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.
Eld Leijonhufvud
supported this idea
·
-
18 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.
Eld Leijonhufvud
supported this idea
·
-
9 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.
Eld Leijonhufvud
supported this idea
·
-
40 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.
Eld Leijonhufvud
supported this idea
·
-
24 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.
Kind regards,
The Mews Team
Eld Leijonhufvud
supported this idea
·
-
2 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.
Eld Leijonhufvud
supported this idea
·
-
12 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.
Eld Leijonhufvud
supported this idea
·
-
4 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.
Eld Leijonhufvud
supported this idea
·
-
10 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.
Eld Leijonhufvud
supported this idea
·
-
8 votesEld Leijonhufvud
supported this idea
·
-
103 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.
Eld Leijonhufvud
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Eld Leijonhufvud
commented
Availability Blocks:
1. Can these please - in some way - simply be visible in the Timeline?
2. Can this system please be adopted and clarified so that the terms - re e.g. which actor has responsibility/liability - become more understandable and consistent (re: free (or “Inquired”), “Picked-up”, “Optional” and “Confirmed” stages - respective “Guest”, “Companion”, “Customer”, “Company”, “Travel Agency”, “Booker” etc.)?
Background:
1. Hoteliers typically work with a timeline to get a quick clear overview re which rooms are:
(a) free (or merely “Inquired” = not blocked);
(b) “Optionally” booked (= blocked for public reservations);
(c) “Confirmed”.
Currently, only at the very late stage, merely when having been “Picked-up”, such reservations show in the Timeline (not shown at the “Optional” or even “Confirmed” stages). If only visible in the new, separate, “Availability Blocks” universe, viable overview will become impossible. The result will be confusion, double bookings etc. OR that the new system simply rather cannot be implemented.2. The question is then to have an understandable terminology re the different:
(a) stages and (b) actors.Three different typical group booking scenarios occur.
(i) The “Corporate” scenario:
A company is created. That company (legal entity, e.g. “ConfCo Ltd”) is RESPONSIBLE all the way through for the whole initial availability block, payment, cancellations etc. (i.e. regardless of if the MD or Donald Duck is entered as the contact person – him merely acting on behalf of ConfCo Ltd).(ii) The “Private” scenario:
The initial Booker (often not a company but instead an individual e.g. a bridegroom) is merely responsible for creating a block in the system and maybe for rooming lists etc. Yet, it is then for each individual guest who reserves (“Picks up”) each particular room to be RESPONSIBLE for correctly selecting, paying, cancelling etc.(iii) The “Agent” scenario:
This is very similar to the “Private” scenario. A travel agent or event agency (legal entity or individual) is registered in Mews and then merely responsible for creating a block in the system and maybe for rooming lists etc. Yet, it is then occasionally the principal among the guests (e.g. bridegroom) being responsible in some way, maybe for some deposit/minimum spend etc., but often simply for each individual guest who reserves (“Picks up”) each particular room to be RESPONSIBLE for correctly selecting, paying, cancelling etc.The above, with merely the normal Timeline and Mews “manual”/old group booking methods, results in many different communication and interpretation issues. With the new special “Availability Blocks” system and terms, it become even more complex and confusing. Different methods are used to try to clarify to the different actors which responsibilities they have.
A general method concerning the STATUS of the rooms is to create a “cut-off” date. This would typically simple be a deadline for: 100% refund, payment and remaining rooms block release.
Then, concerning different actors’ RESPONSIBILITIES, there are also, even before now also introducing the “Picked-up” status etc. different concepts to try to clarify this. Below could be an example of the different actors’ responsibilities in an “Agent” scenario:
- Booker: notifies hotel per offer confirmation which guests shall have the Suites.
- Depositor: provides deposit, repayable per group check-out, presuming group stay exceeded deposit.
- Guest: reserves and pays each Room through direct hotel contact.Not really clear why Mews now installed both “Optional” (why? understandably not possible to even create a Booking link or send a quote?) and “Confirmed” – whereby Confirmed is still for some reason not visible in Timeline – and then also the 3rd category “Picked up”.
We are then apparently forced to immediately create a “Confirmed” Availability Block to even be able to send a Booking Engine Link to the client company. Then those rooms are however not confirmed at all but merely optional, invisible in Timeline and available to be (individually) legally confirmed – which legal confirmation is now instead called “Picked up” (as opposed to normal Mews Timeline speech = “Confirmed”).
The fact that a company has agreed to block 10 rooms and then 1 room of that is “picked-up” by/for an individual, could hardly switch the initial legal obligation from a “Corporate” scenario; i.e. change the responsibility from the company to that individual. Alternatively, the new Mews Availability Blocks setup now intends to result in that each individual should opt (“pick”) each respective blocked room and thereby also be obliged to pay for it individually?
In other words, there are two different aspects there:
(a) “pick-up” (understandably meani -
9 votes
Hello from the Mews product team,
Thank you for sharing your feedback with. We are currently resolving this request and would like to offer you the opportunity to test the updates in your demo, or live environment.
The updates are as follows:
When a block is created, we now copy the rate price per space category, per day as well as any price overrides and pricing adjustments. This logic results in less manual price updates when creating availability blocks. You can find a visual overview for this functionality in the recording below:
https://www.loom.com/share/5f18009f6f514e81ac977dbe463af5ba?sid=e4d83ef2-8cf9-4f79-971d-9f7c20a67ae6
If you would be interested in testing this feature, please let me know by responding to this email.
Kind regards,
Aldair Borges
Product manager
Mews
Eld Leijonhufvud
supported this idea
·
Hi
Still no progress re this much awaited improvement? Mews indicated in some webinar Q&A back in time, that this would happen.
Just to be 100% clear, it would indeed be nice to have then, Mews sticking to uniform terms (and colors?) re Availability blocks status being visible on Timeline vs the normal Timeline request/booking status.
I.e. terms/markings to mean the same in both Timeline and Availability Blocks =
“Picked-up” (Availability Blocks) VS
(i) “Inquired” (= not blocked (for any public reservations) but marked in Timeline);
(ii) “Optional” (= blocked);
(iii) “Confirmed” (= blocked (for a certain person) and legally binding). )