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 report that takes three reads before you work out 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 work feels like part of the job, but it isn't. It's preparatory work. None of the decisions in it require your knowledge of the property portfolio 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 over 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 work is more predictable than it feels

Every morning feels different, but the inflow isn't. According to Aedes's review of the maintenance process, on average about one repair request comes in per rental unit per year. If you manage eight hundred units, you know fairly precisely how many reports 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 coming in day after day, and aim to resolve around 80 percent of it at first contact. Repair contact isn't just one stream among many either: 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 precisely the moment that judgement is already being formed.

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

Automating maintenance requests starts at the front door

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 report as urgent, repair or admin, 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 report, recognise the type of fault and determine urgency before a staff member has even seen the message. The tenant who writes that there's no hot water coming from the tap is already sitting in your urgent list by quarter past eight, complete with address and property details, rather than 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 report recognised at 7:40am and one that isn't read until 9:15am because thirteen other emails came first. The tenant notices that difference before you do.

The two places where you still need to keep looking

Automatic triage is good at recognising patterns, and that's exactly why you need to know where the patterns stop.

The first is the urgent report that doesn't present itself as urgent. A tenant who writes about a "weird smell in the hallway" might be describing a gas leak, but doesn't use a single word that would trigger a classification model. Make sure anything that comes anywhere near gas, water on electrics or a safety risk escalates upward by default, and accept that some false positives will slip in with that. An unnecessary phone call is cheaper than a missed report.

The second is the charged message. A tenant emailing for the third time about the same leak and threatening to go to the Huurcommissie (the Dutch rent tribunal) is technically a repair report, 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 warning 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 mix you see. Tally each day how many messages were urgent, repair or admin. Those two numbers tell you exactly what automatic triage would gain you, and they give you the yardstick you can later hold a system to. Chances are the outcome won't surprise you. That's precisely the point: work whose outcome you already know before you do it doesn't belong in the first twenty minutes of your day.