Rezzy: Give it visibility to booking tags so directives can reference them

I've been trying to build directive logic that treats certain guests differently based on tags applied to their booking -- but it's clear from sandbox testing that Rezzy doesn't have visibility to booking tags at all.

The use case: We use a "BAD GUEST" tag to flag bookings of guests we are having issues with. When a tagged guest asks about extending their stay or requests late check-out, we'd want Rezzy to skip its normal quoting/approval logic and respond with a warm generic acknowledgment while routing the request to our team for review. Essentially a "pass off to a human" flag that overrides Rezzy's usual behavior in those categories.

I tested two approaches. First, a standalone override directive ("When the booking has the BAD GUEST tag applied, do NOT quote pricing, present offers, or confirm modifications. Respond generically and create an urgent task for team review."). Then when that didn't work, I built the same trigger directly into the Adjacent Night Upsell directive itself as an in-directive carve-out, placed right alongside the standard quoting logic. Same result both times: Rezzy quoted the extension normally, as if the tag wasn't there. The thinking log shows no evidence Rezzy considered or even saw the tag.

Would love to see Rezzy given access to booking tags so directives can reference them as conditions. Bad-guest handling is my primary need, but I can imagine plenty of other applications -- VIP guests, repeat guests, guests flagged for specific known issues, etc.

Thanks for putting this feature request together! These ideas grow when more voices weigh in, so if you know other users who'd find this useful, send them the link and ask them to upvote.

Community feedback really helps us prioritize what to build next.