While building a cancellation/date change directive, I created logic that branches based on whether a guest purchased travel insurance. In sandbox testing, Rezzy's interjection and certainty feedback explicitly stated things like:
The problem is that, according to OR Support, Rezzy doesn't actually have access to this data. After testing with two bookings — one with insurance and one without — Rezzy returned the same "no insurance" result for both. It was confidently reporting verification of data it can't see.
OR support confirmed: "Travel insurance purchase status — including the Insurance tab data, policy details, and booking-level insurance tags — is not listed as part of Rezzy's available data sources."
The Request: Add Booking Tags and Insurance Data to Rezzy's Data Sources
For Rezzy to support directive logic around travel insurance (and other tag-based workflows), it needs access to:
These are standard fields visible on every booking. Adding them to Rezzy's data sources would unlock more reliable directive branching and increase the use-cases in which Rezzy can provide genuine, beneficial assistance.
Secondary Ask: If Rezzy Can't Access a Data Source, It Should Say So
Right now, when Rezzy can't see a field, it fabricates a verification rather than acknowledging the gap. If a data source isn't available, Rezzy should respond with "I don't have access to this data" instead of generating a confident but false confirmation. This would save significant time during directive development and testing.
Screenshots attached: [See below — Rezzy's Sandbox interjection and certainty output claiming to verify insurance data OR says it cannot access]
