Most property management offices have one maintenance address, and everything goes to it. Leaks, lockouts, invoices, a contractor's reply, an owner asking for an update. Someone reads each one, works out which unit it's about, and copies the important part somewhere else so it isn't lost. When that person is busy or away, the picture falls apart, and owners and tenants call to ask where things stand.
You can stop the copying without asking tenants to change anything. Keep the address they already use. Let every email become a tracked request, linked to the right unit, tenant and owner, with a status everyone can see.
Here is how we set this up for Eagleson Properties, and what we learned along the way.
Keep the address tenants already use
Don't launch a portal and hope tenants find it. They won't, and the form ends up feeding a list nobody watches. Instead, connect the existing maintenance address to your request system. Each email creates a request, and a copy can still land in the shared inbox for anyone who wants it there.
Tenants don't have to learn anything new.
Let the sender fill in the rest
The slow part of handling a maintenance email is working out what it's about. Which unit, which tenancy, who owns the place, who to call.
If your tenants, units, tenancies, properties and owners are records in the same system, the sender's email address can answer most of that. A known tenant's email links to their tenant record, which links to their unit, which links to the current tenancy, the property and the owner. All of it fills in shortly after the request is created.
Two rules keep this honest:
- Only use the current lease. A tenant who moved units last year should link to where they live now, not where they used to.
- When there is no match, leave it blank. A wrong link is worse than none, because someone will trust it. If the sender isn't recognised, a person picks the unit and everything else fills in from that one choice.
Give tenants a short list of statuses
Your team needs detailed steps: triage, ready for a work order, in progress, on hold, escalated, owner managed. Tenants don't. Show them four plain states: open, in progress, action needed from you, and resolved. Internal steps send them nothing.
Fewer, clearer updates mean fewer "just checking in" emails and calls.
Give contractors and owners their own thread
A tenant's request and the conversation with the plumber are different conversations. Keep them apart. When someone needs to be looped in, create a linked request for that contractor or owner. The tenant doesn't see it, and the tenant's request can't be closed while the contractor's is still open, so nothing gets marked done before the work is.
What to watch for
These all caught us at some point. Plan for them on day one.
- Replies from the shared inbox start new requests. An email sent from the normal inbox doesn't carry the request number, so the tenant's reply opens a fresh request. One leak turned into five. Reply from inside the request instead.
- New senders can be dropped silently. Many systems only accept email from people they already know. Check that a first-time sender still creates a request, and test it with a real outside address before you rely on it.
- Not every email is a request. CCs, invoices and newsletters all arrive at the same address. In the first two weeks at Eagleson, about one in five new requests was something that didn't need work. Decide early who clears those, and how.
- One "we got it" message for everyone. A single auto-reply can go to tenants, owners and contractors alike. Check what each of them receives.
- Test data makes matching look wrong. If test tenancies share a real email address, one sender can match several units. Clean them out before you judge the matching.
Start with one inbox
You don't need to rebuild the whole back office to do this. Start with the maintenance address. Once requests, units and owners live in one place, the next steps get easier: AI that sorts and drafts replies, reports owners can read without calling, and dashboards that show where work is stuck.
We built Eagleson's in Jira Service Management, but the approach works in any system that can link records together. If your maintenance inbox is held together by one person's memory, reach out to discuss. We'll tell you where to start, or tell you it isn't worth building.