Curious how other self-managing landlords deal with this. When a tenant texts, calls, or emails about something (AC not working, leak, broken appliance, etc.), how do you figure out what needs immediate attention vs. what can wait?
Is it mostly judgment call based on how the message sounds, or do you have some kind of system? And does anything ever fall through the cracks like a request gets buried in texts and you forget about it until they follow up annoyed?
Just trying to learn how people handle this in practice, especially once you've got more than a couple units going. Appreciate any insight!
This is literally what we do all day running a PM company so let me share the system that actually works at scale.
First, get off text messages for maintenance requests. I know it feels more personal but texts get buried, you cannot track them, and there is no audit trail when a tenant says they reported something two months ago. We use Buildium which has a tenant portal for maintenance requests. The tenant submits a request with photos and a description, it goes into a queue, and nothing gets lost.
For triage we use a simple three tier system. Tier one is emergency and gets a same day response: water leaks, no heat in winter, no AC when it is over 90, gas smell, anything that threatens safety or causes active property damage. Tier two is urgent and gets a 24 to 48 hour response: appliance failures, plumbing issues that are not actively leaking, electrical problems. Tier three is routine and gets scheduled within the week: cosmetic issues, minor repairs, things that are annoying but not damaging.
The key is having the tiers defined before the request comes in so you are not making judgment calls every time your phone buzzes. Your tenants should know the system too. We put the triage categories in our lease addendum so expectations are set on day one.
Biggest thing that changed our operation was requiring photos with every maintenance request. Tenants will describe a small drip that turns out to be a busted pipe, or describe a major emergency that is actually a running toilet. Photos cut through the noise and help you dispatch the right vendor the first time instead of sending someone out just to diagnose.
Once you get past three or four units, self managing maintenance without a system will eat you alive. Ask me how I know.
Our tenants have two ways to deal with a maintenance request: online maintenance request form, or text.
The only system that works well for me is immediate handoff and follow-up.
For emergencies only we have a 24/7 hotline.
No system is perfect, simply because humans aren't perfect. However, when we deal with an issue--assign to the proper maintenance person immediately, log it in, and follow up within 24 hours--we reduce or eliminate frustration for both tenant and manager.
Good question and one I thought about a lot before buying. The biggest mistake I see small landlords make is keeping maintenance communication in their personal texts and email. It works until it doesn't, and when a tenant dispute comes up you have no clean paper trail.
What I landed on after a lot of trial and error is pretty simple. Every request has to come in writing through one channel, text to a dedicated landlord number or email, no exceptions. Even if they call you first you ask them to follow up in writing. That one habit alone changes everything because now you have a timestamped record of every request.
From there you log it immediately, classify it by urgency, acknowledge the tenant within 24 hours even if you have no update yet, and assign a vendor from a pre-vetted roster. The acknowledgment piece is underrated. Tenants don't escalate because repairs take time, they escalate because they feel ignored.
I came from 18 years running personnel operations in the Navy and built out a full system around this including scripts for every communication scenario and a vendor vetting scorecard so I'm not calling random contractors off Google when something breaks. Happy to share more detail if it's useful.
Relying on judgment calls based on a tenant's text is exactly how you bleed margins on $150 blind maintenance runs. It works for two units; it breaks at ten.
My background is in writing industrial safety and operational procedures for heavy manufacturing, and I apply that exact same strict methodology to my rentals. The only way to stop things from falling through the cracks is to shift the triage process to the very front of the workflow.
Here is the SOP my husband and I use for every single request:
1. The Visual Requirement: We do not roll a truck or call a handyman based on a text. Every maintenance request must include a clear photo of the leak, the broken fixture, or the appliance error code/data tag.
2. The Diagnostic Protocol: We use those photos to diagnose the exact mechanical failure before anyone drives to the property. We isolate whether we are dealing with a $10 toilet flapper or a cracked tank.
3. The Targeted Handoff: When we dispatch our handyman, we don't just say 'the tenant says the sink is leaking.' We send them the exact root cause and the specific parts manifest required to fix it.
When you force a visual diagnostic step first, you completely eliminate the administrative ping-pong. You can reply to the tenant instantly saying, 'Issue identified, the exact part is on order,' which stops them from feeling ignored.
This is literally what we do all day running a PM company so let me share the system that actually works at scale.
First, get off text messages for maintenance requests. I know it feels more personal but texts get buried, you cannot track them, and there is no audit trail when a tenant says they reported something two months ago. We use Buildium which has a tenant portal for maintenance requests. The tenant submits a request with photos and a description, it goes into a queue, and nothing gets lost.
For triage we use a simple three tier system. Tier one is emergency and gets a same day response: water leaks, no heat in winter, no AC when it is over 90, gas smell, anything that threatens safety or causes active property damage. Tier two is urgent and gets a 24 to 48 hour response: appliance failures, plumbing issues that are not actively leaking, electrical problems. Tier three is routine and gets scheduled within the week: cosmetic issues, minor repairs, things that are annoying but not damaging.
The key is having the tiers defined before the request comes in so you are not making judgment calls every time your phone buzzes. Your tenants should know the system too. We put the triage categories in our lease addendum so expectations are set on day one.
Biggest thing that changed our operation was requiring photos with every maintenance request. Tenants will describe a small drip that turns out to be a busted pipe, or describe a major emergency that is actually a running toilet. Photos cut through the noise and help you dispatch the right vendor the first time instead of sending someone out just to diagnose.
Once you get past three or four units, self managing maintenance without a system will eat you alive. Ask me how I know.
This is literally what we do all day running a PM company so let me share the system that actually works at scale.
First, get off text messages for maintenance requests. I know it feels more personal but texts get buried, you cannot track them, and there is no audit trail when a tenant says they reported something two months ago. We use Buildium which has a tenant portal for maintenance requests. The tenant submits a request with photos and a description, it goes into a queue, and nothing gets lost.
For triage we use a simple three tier system. Tier one is emergency and gets a same day response: water leaks, no heat in winter, no AC when it is over 90, gas smell, anything that threatens safety or causes active property damage. Tier two is urgent and gets a 24 to 48 hour response: appliance failures, plumbing issues that are not actively leaking, electrical problems. Tier three is routine and gets scheduled within the week: cosmetic issues, minor repairs, things that are annoying but not damaging.
The key is having the tiers defined before the request comes in so you are not making judgment calls every time your phone buzzes. Your tenants should know the system too. We put the triage categories in our lease addendum so expectations are set on day one.
Biggest thing that changed our operation was requiring photos with every maintenance request. Tenants will describe a small drip that turns out to be a busted pipe, or describe a major emergency that is actually a running toilet. Photos cut through the noise and help you dispatch the right vendor the first time instead of sending someone out just to diagnose.
Once you get past three or four units, self managing maintenance without a system will eat you alive. Ask me how I know.
The tricky part isn’t really triaging urgency — it’s making sure nothing gets lost between channels before you even get to that step.
What’s your current setup for tracking incoming requests?
The tricky part isn’t really triaging urgency — it’s making sure nothing gets lost between channels before you even get to that step.
What’s your current setup for tracking incoming requests?
Jojo's pointing at the part most of these systems quietly assume away. The tiers and photos advice is all correct in my opinion - but it only works once the request is sitting in one place to be triaged. For self-managers who can't force tenants onto a portal like Buildium, the breakage happens earlier: a text here, an email there, a call you meant to write down. It's lost before triage ever starts.
The way I'd close that gap is a thin intake layer in front of the system everyone's describing — every channel funnels into one logged queue automatically, each request gets a timestamp and an instant auto-acknowledgment back to the tenant ("got it, logged, here's your ticket #"). Nobody feels ignored, and nothing depends on you remembering to write it down. Your tiers and vendor handoff then run cleanly on top.
Curious - for those of you past 10 units, what breaks first: the capturing, or the follow-up after handoff?
The tricky part isn’t really triaging urgency — it’s making sure nothing gets lost between channels before you even get to that step.
What’s your current setup for tracking incoming requests?
Jojo's pointing at the part most of these systems quietly assume away. The tiers and photos advice is all correct in my opinion - but it only works once the request is sitting in one place to be triaged. For self-managers who can't force tenants onto a portal like Buildium, the breakage happens earlier: a text here, an email there, a call you meant to write down. It's lost before triage ever starts.
The way I'd close that gap is a thin intake layer in front of the system everyone's describing — every channel funnels into one logged queue automatically, each request gets a timestamp and an instant auto-acknowledgment back to the tenant ("got it, logged, here's your ticket #"). Nobody feels ignored, and nothing depends on you remembering to write it down. Your tiers and vendor handoff then run cleanly on top.
Curious - for those of you past 10 units, what breaks first: the capturing, or the follow-up after handoff?
The tricky part isn’t really triaging urgency — it’s making sure nothing gets lost between channels before you even get to that step.
What’s your current setup for tracking incoming requests?
Jojo's pointing at the part most of these systems quietly assume away. The tiers and photos advice is all correct in my opinion - but it only works once the request is sitting in one place to be triaged. For self-managers who can't force tenants onto a portal like Buildium, the breakage happens earlier: a text here, an email there, a call you meant to write down. It's lost before triage ever starts.
The way I'd close that gap is a thin intake layer in front of the system everyone's describing — every channel funnels into one logged queue automatically, each request gets a timestamp and an instant auto-acknowledgment back to the tenant ("got it, logged, here's your ticket #"). Nobody feels ignored, and nothing depends on you remembering to write it down. Your tiers and vendor handoff then run cleanly on top.
Curious - for those of you past 10 units, what breaks first: the capturing, or the follow-up after handoff?
That’s a really sharp breakdown. I agree — a lot of systems assume the request is already captured cleanly, when in reality that’s often where things start breaking.
I like how you separated capture from post-handoff follow-up because they create very different operational bottlenecks.
From what I’ve seen, smaller portfolios usually struggle more with capture, while larger portfolios tend to feel the pain more in follow-up and vendor coordination.
Interesting question—my guess is the failure point shifts as unit count grows.
@Joshua Bygate great question — and the thread responses here are gold.
The photo requirement and triage tiers Stephen and Ali outlined are exactly right. The piece I'd add is what happens between the request coming in and the vendor being dispatched — that middle layer is where things fall through the cracks for most self-managing landlords.
An automated intake system fixes this completely. Tenant texts or submits a request → it's automatically logged with a timestamp → you get an instant notification with the details → tenant gets an acknowledgment within seconds so they don't feel ignored → you dispatch the vendor with full context already in hand. No request buried in texts, no tenant following up annoyed because they heard nothing for 3 days.
John's point about the acknowledgment being underrated is exactly right — tenants don't escalate because repairs take time, they escalate because silence makes them feel ignored. Automating that first response alone changes the tenant relationship significantly.
Once you're past 3-4 units the manual approach stops being a time issue and starts being a liability issue — every unanswered request is a potential dispute without a paper trail.
We've found that having a simple system matters more than the specific software.
For us, the biggest thing is getting good information upfront. We ask tenants to send photos whenever possible because what sounds like a major issue in a text can end up being something minor, and vice versa.
We also try to categorize requests as emergency, urgent, or routine so we're not making a judgment call from scratch every time. Active leaks, safety issues, and anything causing property damage get immediate attention. Everything else gets prioritized accordingly.
One lesson I learned early on is that maintenance requests can easily get lost when they're scattered across texts, emails, and voicemails. Even if you're only managing a handful of units, having one place where every request is logged makes life a lot easier and helps avoid the "I told you about this weeks ago" conversation.
Curious how many units you're managing now? The right system often depends on the size of the portfolio.
Curious how other self-managing landlords deal with this. When a tenant texts, calls, or emails about something (AC not working, leak, broken appliance, etc.), how do you figure out what needs immediate attention vs. what can wait?
Is it mostly judgment call based on how the message sounds, or do you have some kind of system? And does anything ever fall through the cracks like a request gets buried in texts and you forget about it until they follow up annoyed?
Just trying to learn how people handle this in practice, especially once you've got more than a couple units going. Appreciate any insight!
First, you should have one form of communication, probably email. Priority would be almost as simple as how you would handle it at your own home. In the middle of the night if you had a stopped-up toilet would you start calling plumbers? If the AC went out? Electric? If you would consider it a priority then so will your tenant.
If you only have a few rentals, do not make it overly complicated. Keep records, but you don't need software or other things to have them submit requests. People get tired of trying to keep track of a bunch of different platforms, passwords and usernames. To prioritize-ask what you would do if it was your home and you had X problem.
I’ve actually been thinking about this a lot as a landlord. Once you have multiple properties, it’s really easy for maintenance requests and tenant messages to get scattered between texts, calls, and emails.
I’ve been working on a tool called Landlord Ally that helps centralize that communication and organize maintenance requests so things don’t fall through the cracks.
Still building it out, so I’m curious to hear how other landlords handle it. Do you have a specific system you use, or is it mostly just keeping up with everything as it comes in?
It is mostly judgment based on a couple of keywords for me: anything with water, smoke, or no heat/AC jumps the line, everything else waits for a daily check-in. What actually stopped things falling through the cracks was writing every request down the moment it came in, even the small ones, instead of trusting myself to remember a text from three days ago. The forgetting happens more with the minor stuff than the urgent stuff, ironically, since urgent things get handled same day anyway.
The “buried in texts” part sounds like the key issue. Even if a tenant first calls or texts, I’d create one record for the issue with the unit, date reported, photos, current status, next action, and who owns that action. Then a reply such as “received; I’ll update you by tomorrow” gives the tenant a clear expectation.
I’d also tell tenants what number to call for an immediate safety or active-damage emergency, since an ordinary request queue should not be the only route for that.
Do you find requests get lost at the initial report stage, or later when you’re waiting on a contractor or tenant response?