Mews: what works today

With Mews, MAYA is a place to write rules and watch them run against your real bookings, without any price reaching Mews. It is useful for trying rules out. Here is what a Mews property does not have yet: sending, your own rates, the history import and a connect screen you can use yourself. This page says exactly what a Mews property gets today.

What works and what does not

How a Mews property is connected

The screen titled Connect your property system lists Mews under Coming soon with the label Not yet available. You cannot click it. Instead, email us after you pay and we connect Mews for you.

Mews connects with keys rather than a sign-in. One key identifies MAYA and we hold it, so you never need to find a client token. The other is an access token for your property, which Mews creates when your property is connected to MAYA. If your Mews account covers more than one enterprise, we also need this property's Enterprise ID.

We arrange a secure way to share keys when we connect you, so never paste them into an ordinary email. We test the keys against Mews, save them, and mark the property as connected. MAYA only ever talks to Mews' own service, and nothing is installed on your computers.

MAYA does not copy your property's name, time zone or currency from Mews, so we set them with you when we connect it. We also set a number of rooms per category, which MAYA uses only if Mews lists none of your rooms (more on that below). Check the time zone and currency under Time zone and currency on the PMS tab, and email us if either is wrong. The calendar, the booking window and every "past week" count run on the time zone.

Every property starts in simulation, and for Mews it stays effectively that way, because nothing is sent either way. Read simulation mode.

What a Mews property pays

A Mews property pays the same as any other property: the same price per room, in the same brackets, monthly or yearly. There is no lower price while nothing is sent to Mews. Read what it costs.

You pay before we connect Mews, and you pick Mews on the payment screen. A code may be needed: the field reads Your code when one is required and Your code (optional) when it is not.

There is no free trial for Mews. The trial (7 days) comes only with the Cloudbeds Marketplace. So unless a code gives free days, your first charge is when you finish checkout. Read codes and the free trial.

Your bill is per room, and MAYA checks the count you pay for against the rooms it counts in your Mews room categories ticked as rooms (read below). Check the Room count section of the Billing page after we connect you, and email us if it does not match the rooms you run. Read your room count and what you pay.

What MAYA reads from Mews

On every cycle, about every five minutes, MAYA reads from Mews:

• Bookings (Mews calls them reservations) made or changed since the last read, with their room category, arrival and departure, and total price.
• Room categories (Mews' name for room types), by name.
• Spaces (your rooms, which Mews also calls resources): which room category each is in, and whether it is switched on. MAYA counts each category's rooms from them (read below).

Once a day, MAYA re-reads the whole window: 30 days back and about 13 months ahead. A booking missed in between is picked up within the day.

The nightly rate MAYA stores comes from the booking's total price. MAYA adds up the charges on the booking and splits the total evenly across its nights, so a 3-night stay at $450 is stored as $150 a night, even when its nights were charged at different prices. That total includes taxes, and it can include extras on the booking as well as the room, so it can sit above your room rate.

The booking date is the moment Mews recorded the booking as created, read on your property's own calendar. MAYA keeps that moment too, to the minute. A group of rooms booked at once in Mews arrives as separate reservations, so the moment is how 3 or more of them for the same room type and dates can count as one booking for booking speed, once you turn that on in Settings (What is counted). For bookings MAYA read before it kept the moment, it fills the moment in by itself from what it read.

MAYA does not read your rate plans, your availability, or any guest details from Mews. Guest fields that arrive with a booking are dropped before anything is stored. Read what MAYA reads and writes.

Which bookings count

MAYA removes a booking only when Mews marks it Canceled. Every other state it reads counts as a booked room: Confirmed, Started, Processed, and also Optional, Enquired and Requested. So an option held for a group, or an enquiry not yet firm, counts towards occupancy and booking speed exactly like a confirmed booking.

If you hold many options that never firm up, occupancy and booking speed read higher than your firm bookings. There is no setting in MAYA for this yet. Cancelling an option in Mews takes it off the count on the next read. Mews records a no-show as a cancelled reservation, so a no-show comes off the count like any cancellation.

A Mews booking is one room, so one booking is one booked room on each of its nights and one booking for booking speed. Nights run from arrival up to, but not including, departure.

How many rooms each room category has

MAYA counts the rooms in each room category from your spaces in Mews, on every cycle, about every five minutes. A space counts in the room category Mews has it in. A space switched off in Mews is not counted. A space that is out of order in Mews still counts, because it is out on some nights and not others: enter it under Rooms out of service on the PMS tab for the nights it is out, and MAYA takes it off those nights only. The Room types block on the PMS tab shows each count as "units" beside the category.

Sellable occupancy is rooms booked divided by rooms you can sell, so this count is the bottom half of every occupancy figure, and the rooms you are billed for are added up from it. Add a space in Mews, switch one off or move it to another category, and MAYA's counts follow on the next cycle. A category with no space switched on shows 0 units.

Mews keeps a space in one room category for each service that sells it, so a second service, such as a long stay one, has categories holding the same spaces again, and each shows them in its units. A space can also sit inside another, such as the bedrooms of an apartment. Adding those categories up would bill the same rooms twice, so while two categories that hold the same rooms are both ticked as rooms, MAYA measures nothing for your bill and the count you pay for stays as it is. Unticking one of them on the PMS tab ends that, but it also takes that category's bookings out of occupancy, so email us if you are not sure which.

If a read of your spaces fails, or a cycle has no time left for it, MAYA keeps the counts it already has, measures nothing for your bill on that cycle, and tries again on the next one. A room category MAYA has never counted, such as a new one that arrives while those reads fail, takes the number of rooms per category we set with you until a read works. Changing that number meanwhile reaches only those never-counted categories. We hear about it once three cycles in a row fail to count your rooms.

If Mews lists no spaces at all in your room categories, MAYA cannot count them, so every category gets that one number, set with you when we connect (100 until then). Occupancy is then right only for a category that has exactly that many rooms. If the PMS tab shows the same units for every category, email us and we check why Mews lists no spaces.

There is no field in MAYA to change a count. Change your spaces in Mews and MAYA follows. If the units on the PMS tab look wrong, email us. Read sellable occupancy.

Nothing is sent to Mews

A Mews property has no starter rules, and the amber strip at the top of the dashboard has no go-live button for Mews: it reads "Simulation · MAYA works out prices but sends nothing to Mews". Going live would change nothing in Mews anyway, and MAYA refuses it from your side: "MAYA doesn't send prices to Mews yet, so there is nothing to switch on." If you want the property to show as live, email us. Live or not, the calendar and the change log show the price your rules set for every night, which is what would have been sent. Once shown as live, the strip gives way to the small green Live tag, whose ? says nothing goes to Mews, live or not, and each live change in the change log says "Nothing was sent to Mews. MAYA doesn't send prices there yet."

Prices you type are saved and shown on the calendar the same way, and they are not sent either. In simulation the line after a save reads "Saved (simulation: not sent to Mews)." On a property we have set to show as live, it reads "Saved. MAYA doesn't send prices to Mews yet." If you want a price in Mews, set it there yourself.

Because nothing is sent, nothing is ever read back either. A rate you change in Mews is never shown as "Changed in Mews" and never kept as a manual price.

No date is promised for sending prices to Mews. To hear when that changes, join the waitlist on get-maya.com, or email us and we will tell you.

Where a night's starting price comes from

MAYA does not read your rate plans from Mews, so it has no "your own rate" for a night. A night's starting price is a price you typed for it, and nothing else: a night nobody has typed a price for is not priced at all, whatever its bookings paid. What a guest paid is never a starting price, on any system. Read What a rule starts from.

No history import yet

Cloudbeds and ThinkReservations properties get a history import at connect, a review of what MAYA found, and starter rules built from that history. Mews does not have that yet. A Mews property's history is what the reads cover: 30 days back at connect, growing by a day each day. So a booked so far vs usual rule stays quiet on most nights at first: it needs at least 3 similar past nights with bookings (read Booked so far vs usual). If you would like us to read further back once, email us and we can read up to a year back. Read the history import.

Get suggestions from my data on the Rules tab reads your history the same way, so on a Mews property it is greyed out, with the note "Not available for Mews yet. MAYA can't read its booking history." Build your rules in the rule builder. Read build your first rule.

When the keys stop working

If your Mews keys stop working, MAYA's reads fail. For about the first half hour nothing on screen warns you: the Connection card on the PMS tab still reads Connected, and no banner appears above the calendar. Once Mews has refused MAYA's keys three reads in a row, the card reads Error and the panel described below appears. About an hour after that, every General Manager and Hotel Admin gets one email headed "MAYA has lost its connection to Mews", asking you to reply so we can arrange new keys. Read emails MAYA sends.

Only refusals of the keys count. A read that fails for another reason, such as Mews being down, leaves the card at Connected, and a read that works starts the count again. Then the sign to look for is Last sync on the PMS tab, which stops moving.

MAYA keeps trying, less often after each failed read, until it tries about once an hour. While reads fail, nothing new is priced. Your rules, history and settings are untouched, and the first read that works catches up on everything that changed in between. Once we save new keys, the card reads Connected again.

Email us and we arrange new keys with you and save them. Leave the keys themselves out of the email: we set up a secure way to share them. There is no button for this in MAYA.

When we remove the keys, the Connection card reads Disconnected and reads stop, and no email is sent. Whenever the card reads Error or Disconnected, the PMS tab and the banner above the calendar show "Mews needs its keys re-entered", with the words "Ask us to re-enter the Mews keys: email info@modern-hospitality-solutions.com." Every role sees the same panel, and the address opens an email to us. We arrange new keys with you. Read reconnecting and disconnecting.

The PMS tab for a Mews property

The Connection card changes when we save or remove your keys, and to Error when Mews refuses MAYA's keys three reads in a row. It can read Connected while reads fail for any other reason. The Recent requests to Mews list and the Health (last 24 hours) card both read "Not tracked for this system", because MAYA keeps a log of its requests to Cloudbeds only. Last sync is the number to look at. Counts as a room and Rooms out of service work the same as on any property. Read the PMS tab.

Leaving

Cancel on the Billing page, then email us and we remove the keys, so MAYA no longer reads from Mews. Nothing in Mews was ever changed by MAYA, so there is nothing to put back. Your rules and settings stay in MAYA. Read Cancelling, restarting and leaving.