In plain words
On the Rules tab, add a rule with Metric set to Booking speed (recommended), Speed Slower Than Normal, Measured over Past month, Then waits (advanced) 1 week, a second row of Sellable occupancy (%) Less than 70, and Decrease the rate by 7%. A night under 70% full whose bookings over the past month are slower than had by the same point is cut 7%. After a week the rule counts only the bookings made since that cut, and cuts again if those are still slow. This rule is not a copy of the "Slow-date trim", which cuts only nights that read exactly Slower Than Normal.
Build the rule
- 1
Open the builder and name it
On the Rules tab, click + Add a rule. In Rule name, type Slow nights.
- 2
Choose booking speed
In the condition row, change Metric to Booking speed (recommended). The row changes to a Speed dropdown: pick Slower Than Normal.
- 3
Set the window and the wait
Under the row, set Measured over to Past month and Then waits (advanced) to 1 week. The ? beside each explains what it does in the app's own words.
- 4
Keep it off nearly full nights
Click + Add condition. The new row starts on Sellable occupancy (%): set Compare to Less than and Threshold to 70. Both rows must be true, so a night 70% full or more is never cut, as with the starter cut rules.
- 5
Set the cut, pick the room types, add it
Under Rate adjustment, choose Decrease the rate and type 7 in Adjust by percent (%). Leave every room type ticked and click Add Rule. A window shows the days the rule will change: click Apply price adjustments, or Skip price adjustments to leave those days' prices as they are. Read Turning a rule on, Apply or Skip.
What the rule reads
For each night in the window (tonight and the next 395), MAYA counts the bookings that night received over the 30 full days up to yesterday and compares the count with what (same weekday, same time of year, up to 3 years back) had received over the same stretch of their own run-up. A rule that cuts judges complete days only, so a quiet morning never counts against a night. A booking counts once, however many rooms it holds. Only the room types the rule measures are counted.
How a wedding block counts depends on how it was booked. On Cloudbeds and ThinkReservations, one reservation that holds several rooms counts as one booking. When guests book their own rooms from a Cloudbeds allotment block, or in one ThinkReservations group or group block, their reservations count as one booking too (or as up to the number under Count a group as up to in Settings), once MAYA has read your history with the group links. On Mews every room is its own reservation, so a group counts once per room, unless you turn on Count bookings made together as one in Settings: then 3 or more separate reservations for the same room type and dates, made within 3 hours of each other, count as one booking (or as up to the number under Count a group as up to), on any system, once MAYA has read your booking history with booking times. For occupancy, every booked room counts either way.
Slower Than Normal means that slow or slower: the rule fires on Slower Than Normal, Much Slower Than Normal and Stalled. With an expected count of 5, a night with 1 booking reads as Much Slower Than Normal and fires. With 5 or 6 it reads Normal and does not. When the difference is small, MAYA reads it as Normal, so the rule does not fire. With fewer than 5 similar nights to compare with, MAYA calls a slow night at most Slower Than Normal: that still fires this rule, but keeps a rule set to Much Slower Than Normal, such as "Slow-date rescue", from firing.
What happens after it cuts
The cut stays on the price. Cancellations only make a slow night slower, so they never take it off. For 1 week the rule leaves that night alone for that room type. When the wait is over it counts only the bookings made in the full days after the newest cut still on that night by this rule or a stronger one, up to yesterday. A cut from a weaker rule, or from a such as "Last minute", does not restart the count. It compares those bookings with the same days on the , and if they read slow on their own, it cuts another 7%, and that run's change in the change log reads "Slow nights" lowered this night 7%, from the price the first cut left, with "Slow nights' -7% still applies." under it. Once three of its cuts are on the same night, the amber banner asks whether to keep adjusting or stop.
A cut that comes off by itself: behind usual
A cut on stays on the price. For a cut that holds only while the night is behind, and comes off once it catches up, use booked so far vs usual instead: Metric Booked so far vs usual, Compare Behind usual by at least, Threshold 20, and Decrease the rate by 7%. A night with at least 20% of the rooms it measures fewer booked than had by the same point is cut 7%. It is a : one cut while that holds, no wait, and the cut comes off at the next check once bookings close the gap. Every room of a group counts, so a wedding block lifts the night at once. It needs at least 3 similar nights with bookings, and does nothing without them. Read Booked so far vs usual.