Handing workflows to agents does not remove the operator. It moves the operator’s work up a level, from carrying out each step to deciding what the steps are for. Operators define outcomes, set limits, approve what matters and handle what no rule anticipated. We think that job asks more of a person than clicking through screens and gives more back.
From operating software to directing outcomes
A general manager and the department teams around them keep reviews, reservations, tickets and tasks in hand all day, fitting that work around guests and shift changes. Without one shared surface, that means moving between separate tools.
In that arrangement, the connections live in the manager’s head. They notice that a review, a reservation and a staff note concern the same guest, then link them by hand. The software holds the facts; the person holds the relationships between them. It works, but it spends a skilled person’s attention on bookkeeping between systems.
That is effort spent operating software rather than running the hotel. The architecture we are building changes the order of things. Operators define outcomes, while agents coordinate the systems and execute the work. In our comparison with copilots, work starts when an outcome is defined rather than when someone writes a prompt.
Writing a good outcome
If the outcome is where the work starts, the quality of the outcome sets the quality of the work. A vague outcome produces confident work in the wrong direction. A good outcome tends to have a recognizable shape:
- It names a result, not the clicks that produce it.
- It states the limits the agents must stay inside on the way.
- It says which decisions come back to a person for approval.
- It can be checked afterward against what actually happened.
As an illustration, an operator might write: no guest who reports a problem at breakfast is still waiting for an answer at check-out; any compensation goes to the duty manager first. It names a result, it can be checked and it reserves one decision for a person.
Compare that with an instruction to check the inbox every hour. It describes a step rather than a result. Nothing about it tells anyone whether a guest was actually helped. Steps are what agents should work out for themselves, inside the limits.
Most of the difficulty sits in the limits. An outcome with no limits invites an agent to reach it any way it can. We expect writing limits well to become the core skill of the role. The mechanics underneath (permissions, approvals and traces) have a post of their own.
Outcomes are not written once. Seasons change, teams change and a hotel changes what it wants to be known for. Revisiting outcomes and limits should become a routine part of running the property.
Exceptions are where judgment lives
If agents act only within the limits a business sets, everything outside those limits is a person’s call by definition. That is not a gap in the design. It is where we think much of the judgment in hospitality lives. Agents can take on the routine because people keep the unusual.
Consider a few illustrative cases. A guest’s stay has gone wrong in a way no rule anticipated. A request is reasonable but unusual. What revenue would prefer conflicts with what a loyal guest deserves.
None of these should be settled by an agent guessing at what the hotel would want. Our aim is for exceptions to reach people with their context attached, instead of buried among routine tasks. Handling them well can also improve the limits themselves. An operator who meets the same exception again and again has found a limit worth rewriting.
Exceptions are also where a hotel’s character shows. Properties with the same systems and the same agents will still handle a difficult evening differently. That difference belongs to their people. It should stay with them.
What does not change
The general manager is still responsible for the property. Housekeeping still turns rooms, the front desk still greets arrivals and sales still builds relationships. Guests still meet people at the desk and in the corridors. What changes is where the operator’s attention goes.
Shift handovers still matter, though what gets handed over changes. Instead of a list of tasks someone must remember, a handover can center on open exceptions and the decisions waiting for a person.
Every workflow an agent carries should hand an operator back to the decisions only the business can make. A feature that only adds another screen to watch fails that test.
The operator’s job does not shrink when agents arrive. It concentrates on what the business wants, what it will not do, what needs a person and what to do when the rules run out. The better the agents become, the more a hotel depends on operators who know what they want.
