Skip to content

Agent rules reference

The Agent Hub is where your workspace’s automations are configured. Five rule kinds exist today. Each is listed here with its exact trigger, audience, and options - the same catalog the hub itself renders from.

Common to all kinds:

  • Scope. Most rules are configured per property, with an optional workspace default. A property’s own rule replaces the workspace default entirely (no field-by-field merging) - and a property rule that is switched off wins: it never falls through to an enabled workspace default.
  • Channels. Each kind declares which channels it can use, from: email, WhatsApp, SMS, in-app. SMS is not yet available - it appears in the vocabulary but has no transport, so the picker disables it and the engine refuses it.
  • Attribution. Every automated action is recorded with actor system plus the rule that acted, and shows in the hub’s Run history tab.
  • No rule touches money. The vocabulary contains no money verb; see The approval system.

guest.booking-confirmed

Trigger The moment a booking is confirmed (the booking.confirmed event)
Sends The booking confirmation, to the guest
Channels Email, WhatsApp (SMS listed, unavailable)
Scope Per property
Options Enable/disable and channel choice only - no timing, no recipient list

guest.lock-code-pre-checkin

Trigger A sweep comparing the clock against check-in time minus your lead minutes
Sends The stay’s access code, to the guest
Channels Email, WhatsApp, in-app (SMS listed, unavailable)
Scope Per property
Options Enable/disable, lead minutes, channel choice

reception.daily-arrivals

Trigger A daily schedule - the send-at time you choose, in your workspace’s local time
Sends One digest listing every arrival per apartment, to a recipient list you enter (fixed addresses - reception desks aren’t seats)
Channels Email, WhatsApp
Scope Per property
Options Enable/disable, send-at time, recipients, channel choice

reception.instant-arrival

Trigger A booking confirms for an arrival today (the booking.confirmed event, filtered to same-day)
Sends An immediate alert, to the same kind of recipient list as the daily digest
Channels Email, WhatsApp
Scope Per property
Options Enable/disable, recipients, channel choice

ops.daily-report

Trigger A daily schedule - send-at time, workspace-local. Default: midnight, which is what every workspace gets until someone opens the card
Sends The full midnight brief: board, arrivals, departures, cleaning queue, pending payments, and tonight’s vacancies
Channels Email, WhatsApp (WhatsApp always gets the minimal summary)
Scope Workspace only - it is one brief spanning every property, so there is no per-property version
Options Enable/disable, send-at time, channel choice, and which renderings to email: minimal, detailed, or both (unset means both)

Two deliberate differences from the reception kinds:

  • The audience is seats, not addresses. Every delivery is recorded per recipient seat for the audit trail, so the recipient list on this card picks workspace members (it can never drop to zero - an owner/admin floor remains). Who may read the report is a permission every member-floor seat already holds.
  • Enabled by default. With no rule configured, the report still goes out at midnight by email with both renderings - configuring the rule adjusts it rather than turns it on.

The hub also lists planned automations that are declared in the catalog but not yet available - they render under Coming soon and cannot be enabled. This page documents only the five live kinds above.