You now have granular control over when guests receive waiver reminder emails — and when your team gets alerted about bookings with missing waivers. Settings are organized in a four-level hierarchy so you can set sensible defaults for your whole company and override them where needed.

Settings work like overrides — you set defaults at the company level, then can override them for specific situations:

The most specific setting always wins. So if your company default is ON, but you set a specific booking to OFF, that booking won't send reminders — even though your company setting says to send them.

When on, guests with unsigned waivers receive automated reminder emails before their trip. When off, no guest reminders are sent within that scope.

When on, guests are expected to sign a waiver before their trip and the system tracks waiver status across bookings. When off, waiver collection and all related reminders / admin alerts are silenced.

When on, your admin team gets an in-Origin notification when an upcoming booking still has missing waivers as the trip date approaches. You set how many days before the trip the alert should fire — we recommend 2-7 days. Each booking triggers at most one alert, so you won't see duplicates.

When on, admins receive an email in addition to the in-Origin notification. When off, admins only see dashboard alerts.

Go to Waivers → Notification Settings. You'll see four tabs — Company, Listings, Bookings, and Customers — each showing the relevant override options.

Scenario 1: You want all guests to get reminders, except for one VIP repeat customer who already signs every season.

Scenario 2: A specific listing doesn't legally require a waiver (e.g., a lodging-only booking).

Scenario 3: One booking has a guest who's been getting too many emails — you want to silence reminders for that booking only.