Building an AI Phone Agent for Property Management: Triage Logic

#ai #telephony #saas #proptech

Property management is one of the more interesting use cases for AI phone agents because the call triage logic is non-trivial.

The Challenge

Unlike a dental practice (90% of calls = "book an appointment"), property management calls are diverse:

Emergency maintenance (immediate escalation needed)
Routine maintenance (log and queue)
Tenant questions (answer from knowledge base)
Prospective tenant calls (availability, viewings, pricing)
Contractor callbacks (route to manager)

An AI agent needs to classify intent quickly and route appropriately. Getting this wrong has real consequences — missing a burst pipe emergency because it was classified as routine is a legal liability.

Triage Implementation

The key is keyword + sentiment analysis in the first 10 seconds:

Emergency signals:
- "flooding", "burst", "no heating", "locked out", "fire", "gas smell"
- Urgency in voice (raised volume, fast speech)
- Time context: "it's 2am and..."

→ Action: Immediate SMS/call to on-call manager + log

Routine signals:
- "dripping", "broken blind", "door handle", "paint peeling"
- Calm tone, descriptive language
- No time urgency expressed

→ Action: Log ticket, confirm acknowledgment, set expectation

What Makes Property Management Hard

Emotional callers: Tenants with emergencies are stressed. The AI needs to de-escalate, not just classify.
Multi-property context: "My apartment" means nothing without knowing which building, which unit.
Contractor coordination: The AI might need to schedule a plumber and notify the tenant — two-party coordination.
Legal sensitivity: Some maintenance issues have legal deadlines (heating failures in winter, for instance).