In plain words
On the Rules tab, add a rule with Metric Booking speed (recommended), Speed Surging, Measured over Past day, Then waits (advanced) 1 day, and Increase the rate by 25%. A night that received far more bookings today than had on the same day of their run-up is raised 25%. The next day the rule counts only the bookings made since that raise, and raises again if those still read Surging. This is the "Sudden-spike catcher", so check your list first.
Build the rule
- 1
Open the builder and name it
On the Rules tab, click + Add a rule. In Rule name, type Sudden rush.
- 2
Choose Surging over the past day
Change Metric to Booking speed (recommended) and pick Surging in Speed. Set Measured over to Past day and Then waits (advanced) to 1 day.
- 3
Set the raise, pick the room types, add it
Under Rate adjustment, choose Increase the rate and type 25 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 Surging takes
Past day counts the bookings dated today, on your property's own calendar, so a reading soon after midnight has almost nothing in it yet. MAYA compares that count with what received on the same single day of their own run-up. Surging is the top of seven levels: the night needs at least 3.5 times the usual count, and at least 4 more bookings than usual, to read as Surging. With an expected count of 5, that is 18 bookings or more in one day. With fewer than 5 similar nights to compare with, the call is capped at one step from Normal and Surging cannot be reached.
Picking Surging means the rule fires on Surging only. To fire on a broader rush, pick Much Faster Than Normal (at least twice the usual count) or Faster Than Normal, which fire on that level and everything above it.
What happens after it raises
The raise stays on the price, up to the room type's ceiling. For 1 day the rule leaves that night alone. Then it counts only the bookings made since the newest raise still on that night by this rule or a stronger one. If those alone read Surging against what a similar night gets in a whole day, it raises another 25%.
A raise by a weaker rule, or by a (no or condition), does not restart that count. One burst of bookings raises a night once, not once per rule. Once three of its raises are on the same night, the amber banner asks whether to keep adjusting or stop.
The rule's undo box, Take this change back if cancellations remove the bookings that triggered it, starts ticked. With it ticked, a raise comes off when bookings it counted cancel and the ones still booked no longer read Surging, unless bookings made since keep the rule true. The change log then reads: Cancellations meant "Sudden rush" was no longer true, so its 25% raise came off. Untick the box and cancellations never take the raise off. Read When a price change comes off.