Small hotels

Booking emails into door codes

The hotel's reservation system has no public connection, so its only way to report a booking, change or checkout is an automatic email. The front desk reads each one and sets the door code by hand, and a missed cancellation leaves a working code with a guest who is not coming.

Who it is forIndependent hotels and guesthouses whose reservation system reaches the outside world only by email
Who decidesThe front desk manager
Where the work livesReservation system emails → smart lock platform → guest message
BuildTen business days
A hotel room door with a keypad smart lock, a brass room number plate on the door, and a printed booking confirmation lying on a small console table beside it.

Who does what

The hours go to reading emails the lock never sees.

New bookings The agent reads guest, room and dates from the confirmation email. It creates a code for those dates and queues the guest message for the day before arrival.The agent
Checkouts and cancellations The checkout or cancellation email ends the stay. The agent switches the code off at the time the hotel sets.The agent
Changed stays A date change, room move or early arrival arrives in a different email layout. The agent drafts the change of old code to new code and holds it for review.The agent
Emails that do not match A change to a booking the agent never saw, or a guest name that differs from the original. The front desk manager decides, because a code made on a guess opens a real door.The front desk manager
Lock or service down When the lock platform does not answer, the front desk issues a code by the hotel's manual method.The front desk manager

What you get

A door code created for each guest's room and dates, a message sent the day before arrival, and the code switched off at checkout.

Draft for review

Email
Change email: the surname matches a two-night booking for room 12. The new dates start one night later, and the room shown is 14.
Draft
Hold. End nothing and create nothing until the front desk confirms the room.
Based on
The original booking holds room 12 from Thursday. Room 14 already has another guest's code for Friday night.
How sure it is Moderate
Why a person decides Moving the code to room 14 would overlap another stay. The front desk manager confirms the room before any code changes.

The rules it follows

It follows the hotel's own check-in rules from the first day.

These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.

  • Codes start at the hotel's check-in time and end at its checkout time.
  • The guest message goes out a set number of hours before arrival.
  • Early arrivals and late checkouts get codes only once the front desk approves them.
  • Any change that moves a guest to another room goes to the front desk manager.

What it learns when your team adjusts its work

Useful from the first day, and it keeps getting better. The front desk manager reviews its work.

The busywork it takes off the front desk manager. It takes over the re-entering of every booking into the lock app and the check for codes still running after checkout. That time goes back to the work only they can do.

What it starts out knowing

  • Every email layout the reservation system sends
  • The hotel's check-in and checkout times
  • Which lock belongs to which room
  • When guests hear from the hotel and what the message says

It works from these sources, shows which one an answer came from, and asks when the answer is not there.

Who reviews its work, and when review can stop

The front desk manager reviews each code at first. Review stops for a routine type, such as plain new bookings, once the agent's record on them is good and the hotel agrees.

Room moves, mismatched emails and anything that touches another guest's stay keep going to a person.

It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.

When your team adjusts its work

When the front desk manager changes a code to start two hours early for a returning guest, the change is saved as an exception for that guest, and the agent offers the early start on that guest's next booking. The team decides whether it becomes a rule.

It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.

From a request a business posted

A hotel weighing its options, on a public automation forum.

A hotel asked whether the system emails from its reservation software, which has no public connection, could drive its smart locks. It wanted the guest, room and dates read from each booking, check-in and checkout email. It also wanted a PIN code made and later switched off for each stay, plus a message to the guest a day before arrival.

Paraphrased from a public post, not quoted, and not a client engagement.

From first principles

Which door should open, for whom, and between which two times?

Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.

  1. What has to be true

    • Every code matches one guest, one room and one stay.
    • A code stops working when the stay ends or is canceled.
    • The guest gets the code in time to use it.
  2. What is only habit

    Copying names, rooms and dates from an email into the lock app is only habit. It exists because the two systems cannot reach each other.

  3. What we delete before building anything

    We drop the re-entering of booking details into the lock app and the end-of-day check for codes left running. The email already holds that data.

  4. What is left

    The agent. We build an agent that reads each reservation email, creates or ends the code on the right door for the right dates, and sends the guest message on schedule. It holds any email that does not line up with a booking it knows.

    A person. The front desk manager decides on room moves, mismatched names and any code that would overlap another stay.

The kind of work: Systems that don't talk to each other. This is the work of carrying the same facts from one system into another: a client's details into each carrier site, a client's figures into a review sheet, a booking into a door code. Connecting the systems moves the data, but it does not read the email, check the figures against the rules or chase the missing piece, so people still do that part by hand.

What the engagement needs

What we need from you, and how it runs.

The engagement needs read access to the inbox that receives reservation emails and an account on the lock platform's interface. A month of past booking emails shows every layout the system sends. The hotel sets when codes start and end and when guests hear from it.

How the engagement runs

  1. 01

    Fit test first

    We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.

  2. 02

    Build in ten business days

    Senior engineers agree the rules with the front desk manager, test on past cases and set approval limits and a way to switch it off.

  3. 03

    Ninety days of support, included

    Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.

  4. 04

    Keep improving it, with your choice of operator

    You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.

When we'd point you elsewhere

Sometimes a ready-made tool is enough.

The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.

  • The reservation system already connects to the lock platform The built-in integration between the two is the better answer
  • The hotel has a handful of rooms and few changes The lock maker's own app with scheduled codes is enough

Honest limits

What this page does not claim.

A physical lock is less forgiving than a spreadsheet, so the hotel needs a manual way to issue a code when the agent or the lock service is down.

The situation on this page is drawn from a public request a hotel posted while weighing its options, paraphrased. It is not a client engagement.

Show us the work

More use cases

More work of the same kind: systems that don't talk to each other.