Granular Trigger Controls for Booking Events (Multi-Condition Automation Needed)

Feature Request:

We would love to request more advanced trigger controls within the messaging and automation system—specifically the ability to combine multiple booking conditions into a single reliable trigger event.

Currently, triggers such as:

• Booking Created
• Booking Paid in Full
• Rental Agreement Signed

operate independently, while key guest readiness indicators (such as screening completion via Truvi tags) are only available under “conditions,” not as true trigger events.

The Challenge:

In real-world workflows, especially for hosts using screening tools like Truvi, guest readiness does not happen in a single step. Instead, it’s a sequence:

1. Booking is created (often marked as “paid in full” immediately via OTA)
2. Rental agreement is signed
3. Guest screening/verification is completed (via tags)

Because these actions happen asynchronously, there is currently no reliable way to trigger a message only when ALL required steps are complete.

This creates a gap where:

• Messages may send too early (before screening is complete), or
• Messages fail to send at all due to condition mismatches at the time of the trigger

Requested Solution:

We would love to see one (or both) of the following enhancements:

1. Multi-Condition Trigger Logic

Allow triggers such as:

“Fire when booking is updated AND all conditions are met”

Example:

• Rental Agreement Signed = Yes
• Tag = Truvi Screening Complete
• Property + Source filters

This would allow automation to run only when the booking is truly “guest-ready.”

2. “Booking Updated” or “Condition Met” Event Trigger

Introduce a trigger that fires when:

• A booking is updated
• OR when a condition becomes true (e.g., a tag is added)

This would allow the system to respond dynamically as the booking progresses through its lifecycle.

3. Optional: “Send Only Once” Safeguard

A simple toggle to ensure a message:

• Sends only once per booking
• Even if conditions are met multiple times

Why This Matters:

For hosts managing higher-touch guest experiences, this is critical for:

• Ensuring correct timing of guest communications
• Avoiding premature or missed messages
• Supporting third-party integrations like Truvi
• Reducing manual intervention and workarounds

Right now, many of us are forced into imperfect solutions that either:

• Risk sending messages too early, or
• Require manual monitoring to ensure proper delivery

Impact:

This enhancement would significantly improve:

• Automation reliability
• Guest experience
• Operational efficiency

Especially for professional hosts managing multiple properties and workflows.

Thank you for considering this—OwnerRez is an incredibly powerful platform, and this addition would take automation to the next level.

We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.