Automating maintenance requests: the first twenty minutes of your day don't have to go on sorting

It's Monday morning, quarter past eight. Your coffee is still steaming and your inbox already holds twenty-eight new messages. A leak in the bathroom, two questions about servicekosten (service charges), a boiler that's ticking, someone who's lost their tenancy agreement, and a request that takes three reads before you realise it's actually a sticking front door. Before you've done anything useful today, you've clicked open twenty emails with a single purpose: working out what's urgent, what's a routine repair, and what's actually an administrative question.

That sorting feels like part of the job, but it isn't. It's groundwork. None of it involves a decision that needs your knowledge of the property or your relationship with the tenant. Yet almost every property manager starts the day with it, and will again tomorrow.

The tricky part is that this time never shows up anywhere. Twenty minutes of sorting doesn't appear on any timesheet, but spread across a working year it adds up to roughly eighty hours per person. Time that doesn't go to the contractor, the inspection or the tenant, but to moving messages from one list to another.

The sorting is more predictable than it feels

Every morning feels different, but the inflow isn't. According to Aedes's exploration of the maintenance process, a rental unit generates roughly one repair request per year on average. If you manage eight hundred units, you know fairly precisely how many requests you'll be sorting this year, even if you don't know which ones.

The mix is stable too. Customer contact teams in the woningcorporatie (Dutch social housing association) sector see the same mix of repairs, payment questions and administrative requests come in day after day, and aim to resolve around 80 percent of it at first contact. And repair contact isn't just one stream among many: in the tenant judgement measure of the Aedes benchmark, the tenant with a repair request counts for 55 percent of the final score. The moment you're still sorting is exactly the moment that judgement is already being formed.

Work that's predictable in volume and stable in distribution is work a system can take over.

Automating maintenance requests starts at the front end

Most property managers who think about automation start at the back end: scheduling, the work order, the link with the contractor. But the biggest daily gain sits at the front, in triage. A conversation layer sitting in front of your inbox does three things with every incoming message: it extracts the intent, classifies the request as urgent, repair or administrative, and puts the message in the right list with the information you need to act.

This isn't science fiction. Sector overviews describe how such systems read a request, identify the type of fault and determine urgency before a staff member has even seen the message. The tenant who writes that no hot water comes out of the tap is already in your urgent list by quarter past eight, complete with address and property details, rather than sitting as message number fourteen in an unsorted inbox.

What you win back isn't just those twenty minutes. It's also the difference between an urgent request recognised at 07:40 and one that isn't read until 09:15 because thirteen other emails came first. The tenant notices that difference before you do.

The two places where you keep looking yourself

Automatic triage is good at recognising patterns, and precisely because of that you need to know where the patterns stop.

The first is the urgent request that doesn't present itself as urgent. A tenant who writes about a "funny smell in the hallway" may be describing a gas leak, but doesn't use a single word that would alarm a classification model. Make sure anything that comes even close to gas, water on electrics, or a safety risk escalates upward by default, and accept that some of those will be false positives. An unnecessary phone call is cheaper than a missed report.

The second is the loaded message. A tenant who emails for the third time about the same leak and threatens to go to the Huurcommissie (Dutch rent tribunal) is technically a repair request, but in reality a file that needs attention. Content based classification sees the repair; you see the history. Make sure repeat reports at the same address and messages with legal signal words don't quietly land in the standard list, but come to you instead.

Start by measuring for a week

Before you set anything up, there's a simpler first step: track for a week how much time sorting costs you and what distribution you see. Tally each day how many messages were urgent, repair or administrative. Those two numbers tell you exactly what automatic triage would earn you, and they give you the yardstick you can later use to judge a system. Chances are the outcome won't surprise you. That's exactly the point: work whose outcome you already know before you do it doesn't belong in the first twenty minutes of your day.