Software Modification Request (SMR): Add Trigger for Tag Added / Tag Removed

Summary:
OwnerRez currently allows tags to be used as conditions, but there is no event‑based trigger for when a tag is added or removed from a booking. This removes the ability to use a tag as a simple binary switch to kick off a ton of downstream work.

Request:
Please add trigger events for:

• Booking is tagged
• Booking is untagged

Operational Need / Real Example:
Some booking channels do not provide guest email addresses at the time of reservation. Because of this, several automated messages fail to send at booking creation due to the missing email.

My intended workflow is:

1. When I later obtain and enter the correct email address, I add a tag such as Email Added.
2. Adding this tag should fire a trigger that sends the messages that were previously blocked due to the missing email.

Right now, because OwnerRez does not support “tag added” or “tag removed” as trigger events, there is no way to automate this recovery process. The system cannot detect the moment the tag changes, so the automation cannot run.

Why this matters:

• Many channels do not supply guest emails
• Messages that fail to send at booking time need a clean, automated recovery path
• A tag can be used as a simple switch (binary) to process a ton of work that depends on that state change
• Without tag‑change triggers, the workflow becomes fully manual
• Custom fields do not solve the issue because they also cannot fire triggers on change

Benefits to all users:

• Reliable automation for channels that do not supply guest emails
• Automatic recovery of failed or blocked messages
• More powerful and intuitive use of tags as operational state indicators
• Reduced manual work and fewer missed communications
• Aligns with how many PMS systems handle state‑based automation

Interim solution

For those interested in this concept, I'm using the following as an interim solution:

Since tag‑change events cannot currently fire triggers, I am using a custom field as a temporary state‑change mechanism.

Closing:
Adding “Booking is tagged” and “Booking is untagged” as trigger events would immediately solve these operational gaps and enable a powerful, flexible automation pattern for hosts.

Thank you for considering this enhancement.