Five agents work inside Guester, each covering one domain of the business: operations, revenue, customer, finance and growth. We split the work on purpose, for scope and accountability. The split pays off only because the agents share context. Five specialists that cannot see each other’s work would rebuild the very fragmentation the system exists to remove.
Why specialize at all
A single agent with access to every system would be easy to describe and hard to trust. It would have to hold the rules of revenue, guest communication and accounting at the same time. An operator would have no clean way to say what it may touch, or to tell which part of it made a given decision.
Our systems coordinate specialized agents instead. Each one has a domain and a defined set of systems it works through. That keeps every scope legible: anyone can see what the finance agent works through and what lies outside its domain.
Specialization also matches stakes to scope. A mistaken marketing email and a mistaken payment are different kinds of mistake. Separating the work lets each kind be judged by its own standard.
Hotels already organize themselves this way. Each department, from the front desk to housekeeping, goes deep on its part of the operation while the general manager holds the whole. The agents are not copies of those departments, but the logic is the same: depth in a domain, with a shared view of everything else.
The five roles and their systems
The roles follow the domains of a business rather than its software. Each agent works through the systems its domain depends on:
- Operations: the PMS, calendar, communications and internal software.
- Revenue: the PMS, payments, analytics and external APIs.
- Customer: the PMS, CRM, email and communications.
- Finance: the ERP, payments and analytics.
- Growth: the CRM, email, analytics and external APIs.
Every item on that list is a kind of software a business already runs. The hotel keeps the PMS, CRM, ERP, payments and messaging tools it has today. The agents work through those systems instead of replacing them, from an operating layer that sits above them.
Organizing by software would have been the obvious alternative: a PMS agent, a CRM agent, an email agent. Each would know its tool and nothing about the purpose behind it. Organizing by domain means each agent serves a part of the business, such as revenue, reaching into whichever systems that part depends on.
What the overlaps show
Read the list across instead of down. The PMS appears under operations, revenue and customer. Payments sit under revenue and finance, while analytics serves revenue, finance and growth. The CRM, email, communications and external APIs are each shared too.
That overlap is the honest shape of a hotel. A single reservation is an operational fact, a revenue fact and a guest fact at once. It means something different to each agent that touches it. None of them owns it alone.
This is where a naive design breaks. If each agent kept a private copy of the business, the copies would drift apart. The revenue agent would plan around a booking the customer agent had already seen change. Specialization without shared context produces five confident agents working from five different hotels.
Shared context is the point
In Guester, the agents share context and coordinate decisions. Our systems hold persistent context for the whole operation. They coordinate the specialized agents and carry workflows through to execution. By shared context we mean that a change one agent sees becomes part of the picture every other agent works from.
Shared context does not mean every agent does everything. The revenue agent still works through its own systems; it simply does so knowing what the others know. Specialization decides where an agent acts. Shared context decides what it acts on.
As an illustration, suppose a large group booking arrives. For revenue, it changes what is left to sell. For operations, it reshapes the days the group is in house. For customer, it means many arrivals to prepare for; for finance, a payment to follow; for growth, a relationship worth keeping.
With shared context, each agent responds to the same booking and the decisions fit together. Without it, the same event triggers five separate reactions that someone has to reconcile by hand. That reconciliation is the manual work agents are meant to take off the operator’s desk.
Coordination is not freedom: each agent works only within its permissions and the approvals a business requires, and every action can be traced, which is how operators keep control. How an agent moves from signal to action follows one decision from the first signal to the finished work.
The number of agents is the least important thing about them. What matters is the behavior they are designed for: a reservation, a payment or a guest message is understood once and seen in full by every agent it affects. Five agents that share context make one operation. Five that do not are five more tools to manage.
