From a request a business posted
Re-entering client details across carrier sites
Account managers retype one client's details into each carrier site, then re-enter the result in the management system.
Small hotels
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 does what
What you get
Draft for review
The rules it follows
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.
What it learns when your team adjusts 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
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 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
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.
What has to be true
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.
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.
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
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.
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.
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.
Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.
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
The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.
Honest limits
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.
More use cases
From a request a business posted
Account managers retype one client's details into each carrier site, then re-enter the result in the management system.
From a request a business posted
Staff log into each client's platform one by one at month end, then re-enter the figures into a review sheet by hand.