A team of agents, not a bot
Property management holds worlds that have nothing in common: a resident reporting a leak, a manager asking for the monthly balance, a question about rental regulations, the invoice that goes out on the 1st. A single generic bot does all of that badly.
The answer was a team: seven agents, each with its own domain, tools, and tone, coordinated by one that hands out the work.
The orchestrator: who you are before what you ask
Everything comes in through one main agent. Before answering anything, it identifies the sender against the contacts CRM and assigns one of three roles: admin, resident, or public. That role decides what data is visible and which agents can be reached.
Only then does it act: read the intent, pick the specialist, build the call parameters, and return the answer in a single thread. The user never sees the handoff.
The seven, one by one
| Agent | What it handles |
|---|---|
| Orchestrator | Authenticates against the CRM, resolves the role, routes to the specialist, and holds conversation memory. |
| Alex | Maintenance: checks the resident's ticket status and opens new requests with their history in view. |
| Ben | Resident portal: documentation and admin for their unit, with contact details, financial status, and history. |
| Rico | Finance: per-property balances, with analysis and a professional read of the numbers, not just the figure. |
| Calendar CRM | Technician scheduling: checks availability, creates and reschedules visits without double-booking. |
| Legal | Answers on Los Angeles regulations, citing the source. It is barred from opinions: facts and regulations only. |
| Ava | Billing: on the 1st of each month it generates each resident's PDF, emails it, and escalates the notice based on how many unpaid invoices have piled up. |
What they do together
Separately they're seven assistants; together they're the whole operation:
- A resident writes once and behind it Alex (opens the ticket), Calendar CRM (finds the technician slot), and Ben (confirms against their file) all move. To them it was one message.
- The manager asks about the month and the orchestrator combines Rico (balances) with Ava (billing and arrears) to answer with numbers that come from the same source that bills.
- Nobody answers from memory. Each agent queries the systems live — CRM, balance sheets, calendar — so the answer reflects real state, not canned text.
- What can wait, waits for no one: monthly billing runs on schedule and only surfaces when something is off.
The hard part (and the interesting one)
Keeping the conversation intact across handoffs, stopping two agents from stepping on the same record, carrying the access level untouched from authentication down to the last subagent, and giving each specialist only the tools of its domain: that's what separates a demo from something the office uses every day.
