Send door codes before check-in

Door code to the guest before check-in sends the guest their access code a chosen number of minutes before check-in, with no human pressing the button. It is the only automation that releases something sensitive, so it carries a guardrail no setting can remove.

Screen /agents · Roles: Account Manager, Property Manager, Admin configure; the same automation is the Point of Contact’s seat

Set it up

1. On Automation → Agent Hub (the Built-in tab), find Door code to the guest before check-in and press Set up. The card itself states the guardrail: “Sends only when payment and ID are verified. Otherwise it holds and shows on Today.”

2. Tick the properties it should cover, set Status to On, and pick the channels: Email, WhatsApp (once your workspace’s WhatsApp is connected), or both. The gate below applies the same way on either; see Send guest messages on WhatsApp.

3. Set Minutes before check-in - 30 by default; 0 sends at check-in time, 1440 is a full day ahead.

4. Press Save.

The dual gate, at send time

Every single send re-checks the dual gate: payment verified AND ID verified - at the moment of sending, never at configuration time. Verified payments must cover the booking total, and if any ID check exists on the booking, all of them must be verified. There is no setting, on this rule or anywhere, that skips the gate.

When the gate says no: held sends

A send that fails the gate is recorded as held, with its reason:

• Payment not verified yet
• ID not verified yet
• No access code set on the unit
• No email on file for the guest (or, when WhatsApp is picked, no email or WhatsApp number)
• When WhatsApp is the only channel and the guest has no email: the WhatsApp reason, for example that the guest has not written on WhatsApp in the last 24 hours and no guest template is set

A held send surfaces on Home → Today under Automations waiting on you - “An agent tried to act and stopped. A door code sends on its own once its blocker clears.” That sentence is literal: the hold is re-evaluated on every tick, and the moment you verify the payment, verify the ID, set the unit’s code, or add the guest’s email (or the guest writes to you on WhatsApp), the code goes out with no further human step. The run history records one hold per booking per day, then the send.

The code value stays secret

The run history entry never contains the code itself - it is readable by more seats than may ever see a code. The code travels only in the message to the guest.

No rule, no automated send

Without this rule configured, nothing sends codes automatically - the human hand-off on the booking page is the only path, and it checks the same gate. And no agent rule of any kind can move money.

What’s next

• Door-code operations
• Read the run history