A tenant calls at 11 PM. The line item in your inbox reads "maintenance request," same as the one from this morning about a flickering hallway light. One of these is a burst pipe. You won't know which until someone actually asks. That gap — between "a request came in" and "we know what it actually is" — is where a purpose-built AI agent for property management earns its keep, because it asks the same triage questions every time, at any hour, without a person needing to be awake to ask them.
Managing a handful of buildings means every maintenance call competes for the same limited attention, usually yours. Without consistent triage, the sequence a request gets handled in is just the order it arrived — which has nothing to do with how urgent it actually is.
Every request looks the same until you ask
"Something's wrong with the tap" could mean a slow drip or a flooded kitchen. AIVA asks what a property manager would ask on any other call: which unit, what the issue actually is, how urgent it feels, and how to reach the tenant back. Asked consistently, every time, whether the call comes in at 2 PM or 2 AM — not just when someone happens to be free to pick up.
That consistency is the whole point. A tired night-shift call doesn't get a shorter, worse version of the intake than a Tuesday-afternoon one.
Two calls that sound identical until they aren't
Picture the same phrase — "there's an issue with the tap" — coming in twice in one evening. The first caller means a slow drip that's been going on for a week; asked a follow-up or two, AIVA logs it as routine, notes the unit and issue, and adds it to the next scheduled maintenance round. The second caller means water is actively pooling on the kitchen floor; the same follow-up questions surface the safety and urgency signal immediately, and that request gets flagged and escalated to a human or on-call vendor before the call even ends.
Neither caller had to know which questions to volunteer to get the right outcome. AIVA asks the questions that draw the distinction out, every time, rather than treating "maintenance request" as one undifferentiated bucket.
Routing by urgency, not by arrival order
Genuine emergencies — flooding, gas smell, no electricity, anything with a safety dimension — get flagged and escalated immediately to a human or an on-call vendor, with the details already gathered. Routine requests, the kind that can wait for the next scheduled round, get logged and batched instead of triggering the same urgency as an actual emergency.
The point of triage isn't handling every request faster. It's making sure the ones that can't wait don't sit in the same queue as the ones that can.
This is AIVA's escalation logic doing exactly what it's built for: not routing every uncertain case to a human, but recognising the specific situations — safety, urgency, an upset tenant — that genuinely need one, and sending those through immediately rather than queuing them.
Managing more than one building means asking one more question
A single-building manager knows the context of every call by default. Someone managing a portfolio of properties doesn't have that luxury — the same complaint can mean different things depending on which building, which block, which unit. AIVA handles this by confirming the property and unit as part of the standard intake, so a request about "the lift" gets routed and logged against the right building instead of creating ambiguity that has to get sorted out later, after a vendor's already been sent to the wrong address.
That same per-property awareness extends to anything that varies building to building — amenity hours, visitor policies, society rules — so a tenant in one building doesn't get an answer that was actually true for a different property in your portfolio.
Beyond maintenance: the other calls tenants make
Maintenance triage is the sharpest use case, but it isn't the only thing tenants call about. Rent due dates, payment confirmation, lease renewal timing, whether a specific amenity needs to be booked in advance — these follow the same pattern as maintenance intake: the answer already exists in your records, and the tenant just needs it given accurately and quickly. AIVA handles these from the same setup, so a tenant asking "has my payment gone through" gets a real answer instead of a callback promise.
Monsoon season is when triage actually earns its cost
Most of the year, maintenance calls trickle in at a manageable pace. Monsoon season doesn't work that way — leaks, seepage, and drainage complaints spike hard across a portfolio all at once, often within the same 48 hours, and a lot of those calls genuinely are urgent rather than routine. This is precisely the situation where inconsistent triage becomes expensive: if every call gets treated with the same "we'll look into it" response because there's simply too much volume to properly sort, an actual emergency can sit next to ten routine seepage reports for hours.
Because AIVA doesn't have a queue the way a person answering calls one at a time does, a burst of ten simultaneous calls during a heavy rain event still gets ten real, individually triaged conversations — not nine holds and a promise to call back. And because pricing is pay-as-you-go with no monthly fee, that spike costs more during the specific week it happens and nothing extra the rest of the year, rather than requiring you to staff up for a busy season that lasts a few weeks.
What owners want is different from what tenants want
A tenant calling about their own unit wants the problem fixed. An owner calling about a unit they hold wants to know what's happening across their property and why — history of requests, how quickly things get resolved, whether a recurring issue is actually recurring or just feels that way. AIVA can be set up to recognise the difference and respond accordingly: a tenant gets triage and a timeline, while an owner asking about their property's maintenance history gets pointed toward the reporting you already generate from the dashboard, rather than being walked through the same intake script meant for someone reporting a new problem.
One system, three ways in
Some tenants will call. Others — especially late at night, when nobody wants to be on hold — would rather text a description of the problem and get on with their evening. AIVA's SMS line is two-way and works from any phone, feature phones included, and it's asynchronous by design, so a tenant can start a conversation, walk away, and pick it back up hours later without repeating themselves. Others will use a chat widget on a tenant portal. All three feed the same triage logic and the same record.
What you actually see
Every request lands in a real-time dashboard — what's open, what's resolved, how fast, and which buildings or issue types keep coming up (a pattern worth knowing about before it becomes an expensive one). Data's retained 90 days by default and exportable, so it's there when an owner asks for a maintenance report, not buried across a dozen text threads.
Fitting into what you already run
AIVA connects via webhook or Google Sheets to whatever ticketing or logging system you're already using, so requests don't live in a separate silo you have to check manually. See the connection options on the integrations page, how the voice side handles an intake call on the voice platform page, or the pricing breakdown on the pricing page — pay-as-you-go, no monthly fee, ₹4 a minute on voice, ₹2 per chat conversation, ₹1 per SMS, with ₹500 of free credit to start. Call +91 96623 20707 to hear how a maintenance intake call actually sounds, or start free and connect it to your own portfolio.