Rules & conditions

You can attach rules to an automation. Each rule has conditions (when) and actions (what to do). Typical use: change the message or escalate instead of sending automatically.

Condition (when)

Conditions check reservation or guest data. Examples:

• Guest phone missing — e.g. guest.phone not exists → escalate so you can ask for the number.
• Large group — e.g. reservation.numberOfGuests greater than 4 → append a line like “We’ve prepared extra amenities for your group.”
• Specific value — e.g. reservation.numberOfGuests equals 1 → append “Solo traveler” note.

Supported paths usually include guest.*, reservation.*, property.*. Operations may include: equals, notEquals, exists, notExists, in, notIn, lt, lte, gt, gte, contains. The exact list is in the Automation editor.

Actions

• append — Add text to the end of the message (e.g. a P.S.).
• replace — Replace the message content (e.g. different text for a condition).
• escalate — Do not send automatically; hand off to you. Optionally store a reason (e.g. “Missing guest phone”).

Order

Rules are evaluated in order. The first matching rule’s actions apply. If a rule escalates, the message is not sent by the automation; you handle it in Messages.

Where to configure

In Properties → property → Automation → select a trigger. You’ll see the template and a Rules section (often as JSON or a form). Add conditions and actions, then save. Use Preview or Schedule preview if available to test with a real reservation.

Next: Scheduling — How days and time are applied for each trigger.