How Do You Keep Tenant Requests From Getting Lost?

Question

For those managing rentals themselves:

How do you keep track of tenant requests when they come through different channels?

Text messages, phone calls, emails, maintenance apps, etc. can make it easy for something to get buried.

Do you use:

• A property management platform
• A dedicated email/phone number
• Spreadsheet or Google Sheets
• A task/work-order system
• Mostly texts and memory

A property management platform

A dedicated email/phone number

Spreadsheet or Google Sheets

A task/work-order system

Mostly texts and memory

I'm interested in what actually works for small landlords without making the process unnecessarily complicated.

What's the biggest communication issue you've experienced with tenants?

Marc Winter · Answer

It's a real problem if you have too many touch points; phone, email, text, etc.

We found the best solution was an on-line tenant portal. They log in, fill in a maintenance request, and it's posted immediately. You can build your own, or use a fee-based system. We've used Buildium for many years, and is robust and works great for us. However it can get costly, so shop around.

For after-hours emergency calls we hired a 5pm to 8am answering service. But now we set up an ai bot to handle those calls.

We don't take texts from tenants--they can only use the portal, email, snail mail, or phone call. Most use the portal--folks don't like using the phone for an actual conversation these days.

Leo Stein · Answer

The "next follow-up date" field is the one that saves me. A repair waiting on a part can sit in pending forever, and the tenant ends up chasing you. One intake channel plus a dated follow-up keeps the loop closed without fancy software.

Matthew Tregoning · Answer

The field I'd add is 'next follow-up date.' A repair waiting on a part can sit marked pending forever. Someone needs a reminder to chase the part and update the tenant, even when nothing has changed. Otherwise the tenant ends up managing the follow-up for you.

Richard (Ryszard) Cieplechowicz · Answer

I'd get every request into one list the same day, whatever channel it came in on. After years running admin for a portfolio of about 90 units, what stopped things going missing was one place that logs the date, the unit, the issue, who it's assigned to, and when it's done. A shared sheet is enough. Texts and calls get typed in right after. Then give tenants one way to report things and answer every request with a quick 'got it, logged.' The biggest communication problem I saw was tenants sending the same request three times because they never heard back.

Daniel Jung · Answer

Two things that made the biggest difference for us. First, every request needs a photo. 'The sink is leaking' tells you nothing — a photo tells you whether it's a drip you can schedule or water pouring into the cabinet. It also ends the vague-text-message problem, because tenants who have to snap a picture tend to describe things more clearly.

Second, give tenants a written definition of an emergency. Flood, no heat in winter, gas smell, sewage backup — that's the list. Everything else waits for business hours. Most after-hours 'emergencies' disappear once tenants see that list, and the real ones still get through.

And I'll second what Mark said about verification: the job isn't done when the vendor leaves. Somebody has to confirm with the tenant that it's actually fixed. That's the step small landlords skip most, and it's where the repeat complaints come from.

Mark Updegraff · Answer

@Israel Oluwaseun The biggest distinction for me is between received and owned.

We prefer residents use the portal, but if something comes in by phone, email or another channel, the important thing is that it gets converted into the same work-order system.

Then I want a clear progression:

received → triaged → dispatched → scheduled → completed → verified.

“Vendor says it’s done” is not the same thing as closed.

Somebody needs to own the request until we know the work was actually completed and the resident/property condition matches what we expected.

For a small landlord, that doesn’t require sophisticated software. One intake rule, one work-order list and one person responsible for closing the loop gets you most of the way there.

The problems usually start when everybody saw the request but nobody actually owned it.

Israel Oluwaseun · Answer

Mark, that distinction between “received” and “owned” is a great way to look at it. I especially like the point that “vendor says it’s done” doesn’t necessarily mean the work order should be closed.

Having one person responsible for moving each request from received → triaged → dispatched → scheduled → completed → verified seems like it would prevent a lot of the follow-up issues that happen when requests get passed between people.

I’m actually interested in this from the administrative support side because maintenance coordination and closing that loop are areas where I’m looking to help investors and property operators remotely.

With your experience managing 23 doors, which part of that process tends to require the most manual follow-up — getting vendors scheduled, confirming completion, or verifying the work before the request is closed?

Israel Oluwaseun · Answer

That makes a lot of sense, Marc. I can see how having tenants use one consistent channel would eliminate a lot of the confusion that comes from requests being scattered across texts, emails, and phone calls.

I also like the idea of separating normal maintenance requests from after-hours emergencies. Having an answering service or AI handle that first point of contact seems like it could save a lot of time.

I’m actually developing remote administrative support for real estate operations, so tenant-request organization, maintenance follow-ups, vendor coordination, and keeping property records updated are areas I’m interested in supporting.

I’m curious — once a maintenance request comes through your portal, who handles the follow-up with the tenant and vendor through completion? Is that still handled by your team, or have you automated/delegated that part as well?

Harrison C. · Answer

biggest one when you rent rooms is the same problem getting reported 3 times. a broken sink in the shared kitchen comes in from three people, and each one thinks someone else already told you.

what works for me is one rule. requests go in one place only. if a text comes in i answer once with "put it in there so i dont lose it" and after that people mostly just do it.

and answer the same day with when it will get done, even if the answer is just "got it, thursday". most of the annoyed texts are people wondering if you saw it.

a spreadsheet was fine for me with a couple doors. it broke the first time i forgot to open it.

Jim Johnson · Answer

For tracking requests: one central place is the key. Whether it’s a PM platform or work-order system, texts, calls, and emails eventually need to end up in the same place so there’s a record of what came in and whether it was resolved.

Biggest communication issue: tenants mentioning a repair casually by text or phone and assuming it’s officially been reported. That’s where things can get lost fast if there isn’t a clear process for submitting maintenance requests.

How Do You Keep Tenant Requests From Getting Lost?

How Do You Keep Tenant Requests From Getting Lost?

Most Popular Reply

10 Replies