When PreArrive sends the signing invite

• Send offset: 72 hours before the check-in date. The packet lands while the guest is still home prepping, not mid-flight.
• Reminder cadence: every 24 hours after the first send, while the packet is still unsigned. The reminder goes to the guest and to you (one email each).
• Reminder cap: 5 reminders per reservation. After the fifth, the loop stops on its own.
• Recipients: guest reminders go to whichever address you sent to (host-provided or Airbnb relay). Host reminders go to your account email and can be turned off in Settings → Notifications.

A signed reservation stops reminding the moment the signature lands. A reservation whose check-in date has passed also stops. The scheduler doesn't nag after the guest is already on-site.

Three layers, in order of specificity. The closest layer to the reservation wins:

1. System default: 72h send, 24h reminders, 5-cap. Always the floor.
2. Workspace defaults. Settings → Workspace. Change the default offset, the reminder cadence, or turn either off for every new property you create. Doesn't back-fill existing properties you've already customized.
3. Per-property. Property → Schedule + reminders card. Change offset, cadence, or pick "Don't schedule." Every reservation on the property inherits unless overridden.
4. Per-reservation. Reservation → Actions ▾ → Schedule + Reminder cadence. The most specific override. Useful for the one stay where the guest needs a packet at booking time, or the one stay you want to skip.

Each layer has its own "Inherit" option so you can selectively reset a single override without losing the others.

Picking Don't schedule writes 0 to the offset column, the explicit-off sentinel. That's different from "Inherit," which leaves the column NULL and lets a higher layer decide.

Use "Don't schedule" when you want to send the packet manually (you're still working out the cleaning slot, the guest has a special accommodation, the property is in onboarding). The reservation sits in draft until you click Send.

The scheduler runs as a cron Worker every 30 minutes. If check-in is at 3:00 PM on Friday and the offset is 72h, the packet is eligible to send any time after 3:00 PM on Tuesday, but the next tick that picks it up could be 3:12, 3:24, or 3:43 depending on where in the half-hour the calculation lands.

The offset is anchored on the local check-in moment when both the property timezone and a per-reservation check-in time are set. A 3:00 PM check-in in America/New_York reads as 8:00 PM UTC, and 72 hours before that is the eligibility point. If a property has no timezone or no check-in time, the math falls back to the check-in date at midnight UTC, slightly fuzzier, but predictable.

See Showing check-in and check-out times for how to set those.

Three ways to stop reminders for an unsigned reservation:

• Per reservation. Actions ▾ → toggle Reminders off, or set cadence to "Don't remind." The reservation's reminder loop stops immediately; existing reminders that already fired stay in the count.
• Per property. Property settings → Reminders → Off. All reservations on the property inherit unless one has its own override.
• Per recipient. Settings → Notifications → uncheck "Reminders when a packet is still unsigned" to stop the host-side email. The guest reminder still fires.

If the cap (5) has already been reached, the loop is already off. No further reminders fire.

When the new defaults shipped, existing properties were left alone. If you'd already customized your workspace defaults, your settings stay; if you'd never visited the Workspace card, the workspace default flipped to 72h / 24h-cadence / reminders-on, and any new properties you create now inherit those values.

To force every property onto the new defaults, open each property and set its schedule and reminders fields to Inherit workspace. That removes the per-property override and the property follows the workspace setting.