AI assistant for property and housing management: requests, balances and visits without the phone queue
How a property manager would configure Kav: request status, service-charge balances and visit changes, using mechanisms already proven on city requests.
A property manager's inbox is full of two questions: what is happening with my repair, and what do I owe. Both are answerable from the management system, and both arrive at the moments nobody in the office is looking.
What exists today, and what does not. No property-management connector is built. What is live is the same mechanism on a city's own systems: resident requests tracked from a chat, and balances read from the billing system. This article maps that across; no property company is named.
What a tenant or owner asks, and how it would work
- "What is happening with my leak?" Request status, read from the management system, works the way a permit or a resident request is tracked in the municipal deployment (filing a permit from a chat).
- "What do I owe?" A service-charge or rent balance follows the pattern of a property-tax balance: read from the system of record, shown through a template, never written by the model (a tax balance without the call centre). It can lead straight to a live payment link (from balance to a live payment link).
- "Move my repair visit to Thursday." Shown before it is made and carried out once, as confirmed (confirmed before it runs).
Where the money moves
The bold rows are the levers a property manager leans on most. Rows describe the mechanism, not a live deployment.
| Lever | What Kav does here | What you measure |
|---|---|---|
| Fewer repeat contacts | Request-status and balance questions are answered from the management system. | "Status of my request" contacts per 100 open requests. |
| Faster when a person steps in | A new request arrives structured, with location and category, instead of as a phone description. | Time from a report to dispatch. |
| Out of hours, every channel | A burst pipe reported at midnight is captured; a status asked on a Sunday is answered. | Out-of-hours reports, and how each was handled. |
| Fewer errors and rework | Balances and dates come from the system of record, not from a retyped message. | Disputed balances. |
| Revenue kept | A balance answer can lead directly to a payment link. | Payments started from a chat, against before. |
Work out your own number
- Count status and balance contacts in your log for four weeks.
- Cost per contact = office hours × loaded hourly cost ÷ contacts handled.
- Value = those contacts answered without a person × cost per contact. Track payments started from the chat separately.
Work out your break-even from the published prices, or talk to us about connecting your management system.