Tenant & owner enquiry triage
In property management, inquiries arrive through multiple channels: email, web forms, tenant portals, and service hotlines. For every message, staff must identify the resident, look up the affected property and unit, check historical service tickets, and formulate an appropriate response.
An AI agent fundamentally streamlines this workflow. It analyzes the incoming inquiry, resolves the unit and contact via the API, retrieves contextual guidance from property documents and house rules via semantic search, and drafts a precise response. A human property manager reviews and approves the draft with a single click, while the agent records the entire interaction back into etg24 as structured data — logging the inquiry, response, and scheduled follow-up dates.
Triage logic is clear and configurable:
- General inquiries (e.g. key orders, certificate requests): Draft responses directly from the knowledge base.
- Maintenance reports (e.g. heating failure, water leaks): Classify urgency, match the responsible vendor from property contacts, and prepare a work order.
- Semantic matching: Because retrieval is semantic rather than keyword-based, the agent identifies the true intent even with colloquial descriptions or typos.
Architectural building blocks
- Query tools: Retrieve unit data, resident contacts, and historical communication threads.
- Semantic search (
meta.docs.search): Search property documents, bylaws, and the user manual to ground answers in verified facts. - Command tools: Create internal notes, service tickets, and scheduled follow-ups.
- User-bound agent keys: Ensure every drafted message and ticket update is cleanly attributed to the responsible staff member.
Incremental adoption
Start small: deploy the triage agent on a single general inbox to draft responses for review. As confidence grows, expand the agent’s scope to additional channels and automated ticket dispatching. See code snippets to get started.