Narrow a rule with conditions

Screen /agents · Roles: Admin (an agent:manage seat)

A rule with no conditions fires for every booking that reaches it. Conditions narrow it to the bookings it is actually for.

To stop a rule firing for one property, add that property to the rule’s exclude list. To stop it firing for a whole channel, a length of stay, a party size or a booking made at short notice, use the matching condition below. Every condition is optional and every one of them only ever narrows.

1. Open /agents and edit the rule.

2. Open its conditions. Only the kinds that resolve one booking per message offer them - see the note below.

3. Set what you need. Everything is optional.

4. Save, then watch the run history to see what fired and what was filtered out.

What you can filter on

Condition	What it means
Except these properties	An exclude list. A property you add next month is included by it.
Channels	Fire only for these booking channels. There is an exclude list too, and exclude always wins.
Advance notice	Same-day bookings only, or booked at least N days ahead.
Length of stay	Single-night stays, or multi-night stays.
Party size	A minimum and a maximum, inclusive at both ends.
Returning guest	Yes, no, or do not care.
ID verified	Every identity check on the booking has passed - yes, no, or do not care.
Free nights after	The turnover gap after this stay. Useful for “offer a late checkout when nothing follows”.

Exclude and include are different sentences about the future

“All properties except the Atrium” and “only these four properties” behave identically today and diverge the moment you add a property: the exclude list includes it, the include list does not. The screen says so where it matters; choose deliberately.

Blank is not false

Leaving Returning guest or ID verified unset means “do not filter on this”. It does not mean “must be false”. “I do not care whether they are returning” and “they must not be returning” are different rules, and the screen keeps them different.

Two kinds have no conditions, and that is structural

The reception digest emits one brief per property, so a filter like “single-night stays only” would have to drop lines from a brief rather than decline to send it. The daily ops report is not fired by this engine at all. Both are absent from the conditions editor rather than offering a filter that would not do what it says.

Adding conditions never widens a rule

Conditions are only ever a narrowing. There is no combination that makes a rule fire where it did not before, and an empty set matches everything - so a rule that has been running untouched keeps running exactly as it did.

When a rule goes quiet

Every filtered-out candidate is counted with its reason, so a rule that suddenly sends nothing has an answer rather than a silence. Read it on the run history.

What’s next

• Meet the Agent Hub.
• Read the run history.
• Reply automatically out of hours.