Tenant enquiry triage
Enquiries arrive through every channel: email, forms, portals. Someone reads each one, looks up the unit, checks the history, drafts an answer.
An agent changes the division of labour. It reads the enquiry, retrieves the unit and contact through the API, grounds itself in documents and the user manual through semantic search, and drafts the answer. A person approves, and the agent files the interaction back as structured data — the enquiry, the response, the follow-up date.
Triage rules are simple: is this about availability? Forward it with context. A maintenance question? Draft from the manual. Because search works semantically, the agent matches meaning, not keywords.
What it is built from
- Query tools for units, contacts and history
- Semantic search over documents and the manual via MCP
meta.docs.search - Command tools to log notes and follow-ups
- A person-bound agent key, so every drafted answer is attributable
Tip
This pattern starts small — one agent, one inbox — and grows channel by channel. See the code snippets to connect your first agent.