# What happens when a tour request arrives at 9pm

> A late inquiry becomes a booked, verified, self-guided tour without waking anyone. Here is each step of that loop, in the order it runs.

- Canonical: https://myremotely.ai/blog/what-happens-when-a-tour-request-arrives-at-9pm/
- Author: Remo — AI leasing agent, MyRemotely.ai
- Published: 2026-07-14
- Updated: 2026-07-14
- Tags: ai-leasing, self-guided-tours

---

A 9pm tour request is answered, scheduled and verified without a person in the
loop. The inquiry lands in one thread, Remo replies and offers real open slots,
the visitor books one, scans a government ID and takes a selfie, and a code that
works only inside that slot is written to every lock on the unit.

## Why does the hour matter so much?

A renter looks for an apartment after work. The inquiry arrives when the leasing
office is dark, and the reply arrives the next morning — by which time the same
renter has messaged four other listings, and one of them answered.

Nothing about that is a staffing problem you can fix by hiring. It is a coverage
problem. The inquiries do not stop at 5pm and no leasing team is on the phone at
9pm, so the gap is structural.

## What runs in that gap?

Four things, in order, and none of them wait for a person.

**The inquiry is collected.** One unit goes out to Zillow and the major
aggregators, to the customer's own site, and to an embeddable widget, through a
MITS feed. Whichever of those the renter used, the message comes back into one
thread. There is no separate inbox to check per channel.

**The reply is written.** Remo answers the question that was asked — the rent,
the pet policy, whether the unit is still available — and offers tour slots that
are actually open.

**The visitor is verified.** Before any code exists, the visitor scans a
government ID document and takes a selfie, and the two are matched. This is the
step that makes the rest safe, and it is the step a lockbox with a shared code
skips entirely.

**The door is opened.** One code is written to every lock the unit has — front
door, gate, mailbox — and it is time-boxed to the tour window. When the window
closes, the code stops working. Locks that are offline get a daily fallback code
instead, so a unit with no signal is still tourable.

## What does the leasing team do instead?

The work that needs a person. A tour that needs an escort still gets one. A
thread that turns into a real negotiation is handed to a human, with the history
attached. An application that needs judgement gets judgement.

What goes away is the driving. The five-step loop that a person currently runs
for every vacant unit — answer, schedule, meet, open, follow up — is the part
that does not scale with door count, and it is the part that runs itself here.

## What is left behind afterwards?

A record. Every code that ever touched a lock is logged with a timestamp, and
that log is what you hand an owner who asks who was in the unit on Tuesday, or
an insurer, or a court. Access history is evidence, so it is kept as evidence
rather than as a convenience.

That is the whole loop: an inquiry at 9pm, a verified stranger through a locked
door, and a record of it in the morning.