How to stop losing tenant maintenance texts: a 3-step system

If you manage your own rentals and tenants text you about repairs, you have lost a request. Probably more than one. It's almost guaranteed.

Here's how it usually goes: tenant texts on a Tuesday evening about a leaky faucet. You see it. You think "I'll call the plumber tomorrow." Thursday you remember. You call. Plumber can do Monday. You text the tenant back... except now your phone is showing three other conversations and you forget. Saturday the tenant texts again, slightly annoyed. You apologize. Plumber comes Monday. You pay him. Two weeks later you discover the faucet is still leaking because he fixed the wrong one — but you don't know that, because the tenant stopped texting you after the Saturday apology.

Nothing here is anyone's fault. It's just what happens when maintenance lives in your text messages.

The fix isn't heroic discipline. It's a three-step system. None of it requires enterprise software.

Step 1: One intake channel, not five

Pick one place for tenants to report maintenance issues. Text, email, a form, whatever. Tell your tenants that's the channel. Answer questions outside that channel with "please submit it through [channel] so I don't lose it."

The single biggest reason landlords lose requests is that intake is fragmented. A tenant calls. A different tenant emails. A third texts. You respond from the channel you saw first. A week later you can't find any of them.

What works well as an intake channel, in order of effort:

1. A Google Form. Free. Takes 10 minutes to set up. Fields: name, unit, description, urgency, photos. Responses land in a Google Sheet. Link it in your lease and text the link to each tenant once.
2. A dedicated email alias. maintenance@yourdomain.com forwards to your regular inbox. Everything stays in one thread per tenant.
3. A tool built for this — FixQueue, TenantCloud, Buildium, AppFolio. Tradeoffs: FixQueue is $5/mo and does only this. Buildium/AppFolio are $60+/mo and do everything (accounting, leases, screening) which is overkill for most 1–20 unit operators.

What doesn't work: "just text me." You already know this because you're reading this.

Step 2: Require a photo

Every request, photo required. This one habit changes more than any software you can buy.

• You size up the job faster. Is it a $20 washer replacement or a $400 disposal unit? Photo tells you in 3 seconds what a 10-minute phone call wouldn't.
• You can text a contractor directly. "Here's the issue, can you fix it Thursday?" beats "tenant says there's a leak, can you come look?" every time.
• You have proof if things escalate. Damaged baseboard at move-in vs damaged baseboard at move-out — photos dated with the request settle this.
• Tenants triage themselves. Asking for a photo filters out the "the shower pressure is low on Sundays only" kind of request that wastes your time.

If you use a Google Form: make the photo field required. If you use FixQueue: it's built in. If you use email: send one reply saying "please send a photo so I can send someone out with the right parts" — works 90% of the time.

Step 3: Three statuses. That's it.

You do not need a 7-step workflow. Three states cover everything:

• Open — tenant submitted, you haven't actioned yet.
• In Progress — you've called someone / scheduled / parts are ordered.
• Done — fixed.

Anything more complex (QA inspection, tenant sign-off, escrow) is either rare enough to handle as a note or a signal you're above 20 units and should look at Buildium or AppFolio.

The key move: notify the tenant when status changes. This is where you kill "did you ever fix that?" follow-ups.

• "Open → In Progress" — text them: "Got it, plumber scheduled Thursday 10am."
• "In Progress → Done" — text them: "Fixed. Let me know if anything's off."

If you're using a tool, this is automatic. If you're not, set a reminder in your calendar when you schedule the contractor.

What this looks like in practice

A landlord with 8 units we talked to moved from "tenants text me, I lose things" to this system over a weekend. Their numbers before vs after:

• Average time from request to "In Progress": 48 hours → 4 hours
• Number of requests slipping through cracks per quarter: 3 → 0
• Tenant renewal rate, year over year: 65% → 82%

The renewal rate is the interesting number. Tenants don't renew because they love their landlord — they renew because nothing is fundamentally broken and they don't want the hassle of moving. Responsive maintenance is the #1 predictor.

When to upgrade from a Google Form

Google Forms get you about 80% of the way. Where they fall apart:

• No automated status emails. You have to manually email the tenant after each update.
• No SMS. Tenants don't check email for maintenance — they check texts.
• No per-unit QR code. You have to manually text each new tenant the link.
• No kanban view. You're looking at a spreadsheet.

If you're hitting the limits of a Google Form, the right next step is a tool that does only this one thing well. FixQueue is built exactly for that — each unit gets a QR code (print it, stick it inside), tenants submit requests in 30 seconds from their phone, you manage from a kanban board, email + SMS notifications fire automatically.

$5/month. 14-day free trial. If you're losing more than one request a quarter, it pays for itself.

The 10-minute version

If you read this whole post and remember nothing else:

1. Tell your tenants: "for maintenance, use [ONE channel]."
2. Require a photo.
3. Let them know when status changes.

Everything else is implementation detail.