Skip to content

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
  1. On the Agent Hub, 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.

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

  4. Press Save.

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.

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

A held send surfaces on Today under Automations waiting on you - “An agent tried to act and stopped. Clear the blocker and it sends on its own.” 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, the code goes out with no further human step. The run history records one hold per booking per day, then the send.

The run history - door-code sends held, each with the blocker spelled out