Monday morning, you open your system's inbox and scroll through the weekend's automated replies. You stop at report 47. A tenant asked on Friday evening whether the replacement of his boiler had been scheduled. The bot answered neatly with an explanation of the reporting procedure and linked to the tenant portal. The same tenant called on Saturday morning, irritated, with the same question. You look at the transcript and think: I could have solved this manually in ten seconds, and now I've got an unhappy tenant on top of it.
That is the pattern almost every property manager runs into once AI sits somewhere in the first line. The idea that a chatbot catches standard questions around the clock is correct, but it breaks down the moment a question touches on something specific. And that exact difference between "works brilliantly" and "tenant switched off" is rarely worked out in advance.
What AI in the first line actually works for
The questions suited to automation are the ones you get a hundred times a month in exactly the same form. What are the opening hours, how do I report a repair, when is my rent collected, where do I find my annual statement. A large share of that traffic comes in outside office hours. A conversational chat implementation described in CorporatieGids shows that around ten percent of messages arrive outside opening hours. That is exactly the flow you want to catch without a tenant having to wait until ten o'clock on Monday morning for a status update that is already sitting in his portal.
What works here is that the question has one unambiguous answer, the answer doesn't change over time, and the tenant isn't expecting an escalation. Then the bot simply confirms what the tenant already suspected, and everyone is happy.
Where it breaks down
It starts to grate the moment a question needs context that sits outside the general FAQ. A tenant who asks "why hasn't my repair been scheduled yet" doesn't want an explanation of how reports are prioritised. He wants to know why the report he filed three weeks ago still hasn't been dealt with. An AI that misses this and gives him a generic answer feels, to the tenant, like a landlord who isn't listening.
Research by the Woonbond (the Dutch tenants' association) showed that twenty seven percent of all reports to their reporting point concern landlords who fail to respond to complaints. An automated answer that doesn't actually answer the question falls, for the tenant, into that same category. In fact, a bot that fires something back quickly without engaging with the substance of the report feels even more cynical than no reply at all.
The Aedes benchmark 2025 backs this up. In the repair process, a good explanation of why a repair can't be completed straight away is worth one and a half to two points of improvement on the tenant satisfaction score. That is exactly the explanation a first-line AI can almost never give properly, because the real reason sits in the file, not in the FAQ.
What helps you draw the line
There's a rule of thumb that works well in practice. If a question can be answered without looking at that specific tenant's file, the AI can handle it. The moment the answer needs personal context, automation breaks down. Directions, opening hours, generic procedures, payment references, energy label explanations, notice periods: these are all questions AI handles perfectly well. A specific report, an ongoing repair, a payment arrangement, a complaint about a neighbour: that belongs with a person.
What AI can do in that second category is prepare. Triage a report based on free text, flag that the same tenant already called last week, draft a reply that your staff member turns into something personal in fifteen seconds. That's a different path from answering automatically, and it often saves more time than a bot handling the question itself.
The hidden cost of getting automation wrong
The Aedes benchmark also shows that for repairs the average score is 8.5 when the repair is fixed in one visit, dropping to 6.6 once a contractor has to call four or more times. The same mechanism applies to communication. A tenant who gets an unsatisfying AI answer to the same question three times files a formal complaint the fourth time. That complaint costs you an hour of casework, while the original question could have been dealt with in two minutes.
The gain from AI in first-line contact isn't in handling as many messages as possible, but in handling the right messages. A deflection rate of forty percent on the right category is worth more than sixty percent on a mix where a quarter of tenants still come back dissatisfied. The question for your own portfolio isn't whether you use AI, but which question flows you explicitly exclude from automation, and how you make that visible to the tenant.
See what automatic ticket handling feels like
We are almost ready to let in our first property managers. Leave your details and we will be in touch the moment we open up.
Already have an account? Log in
