The standard advice says no: make tenants submit maintenance requests through a portal or a form, everything in writing, no exceptions. The standard reality is that your tenant just texted you a photo of the ceiling. For independent landlords with a handful of units, the practical answer is yes — accept texts, because you already do, and fighting the habit mostly produces delayed or unreported problems. But accept them with a system. Here’s the case, the real risks, and the four rules that make text intake work. (This is operational guidance, not legal advice — more on that below, because it matters.)
Why tenants default to texting
Texting is how your tenants talk to everyone about everything. Against that habit, a portal is homework: another account, another password, another app for a thing they do twice a year. A tenant standing in front of spreading water will always use the fastest channel they trust — and for most people that’s the message thread with your name already on it.
There’s also a relationship logic to it. At 1–20 units, tenants rent from you, not from a management company. Texting the landlord they know feels natural; filing a ticket into a system feels like shouting into a void. Forcing formality on people who chose a small landlord partly to avoid it is swimming upstream.
The worst outcome isn’t a disorganized request — it’s an unreported one. Every ounce of friction you add to reporting makes “eh, I’ll mention it eventually” more likely, and “eventually” is how a $40 drip becomes a $2,000 subfloor.
The real risks — worth naming honestly
Text intake fails in predictable ways when it’s just texts:
And one legal-flavored risk: many jurisdictions and leases attach repair obligations to written notice, sometimes in a specific form. Whether a text message satisfies your state’s notice requirement is a local question with different answers in different places. Accepting texts operationally does not mean a text checks every legal box — hold both thoughts at once.
The four rules below handle the operational failures. The legal one gets its own rule at the end.
- Requests scatter across a personal phone, mixed in with everything else in your life.
- There’s no status. “Did I ever deal with the disposal thing?” has no reliable answer.
- Nothing can be handed off — the history lives in your pocket, invisible to your partner or your plumber.
- “Did you get my text?” becomes a recurring conversation, because tenants get no confirmation beyond hope.
Rule 1: Give emergencies a separate route — before you need it
Texts are a fine default channel precisely because most requests aren’t urgent. The dangerous ones need a different path, defined in the lease and repeated in a move-in welcome note. Something like: repairs and requests — text or email me any time; you’ll get a confirmation, and I’ll follow up. Emergencies (flooding you can’t stop, no heat in winter, break-in) — call me. Gas smell, CO alarm, or fire — leave the unit and call the utility or 911 first, then me.
A text can sit unseen for hours; that’s acceptable for a dripping faucet and not for a burst pipe. Separating the routes is what makes “text me anytime” a safe policy instead of a gamble.
Rule 2: Acknowledge everything, promise nothing
Every request gets a fast receipt: “Got it — thanks for letting me know about the [disposal]. I’ve logged it and will update you by [tomorrow evening].”
Note what the receipt is not: it isn’t a diagnosis (“sounds like the motor”), it isn’t a completion promise (“we’ll fix it this week”), and it isn’t a commitment to any repair timeline at all. It commits to one thing — when you’ll next communicate — which is the only thing you fully control before anyone has looked at the problem. Acknowledgment is what stops the re-texting cycle; the absence of promises is what keeps you honest when the part takes ten days.
Rule 3: One issue, one thread
The system’s spine: every update about an issue stays attached to that issue’s original conversation. Reply about the sink in the sink thread. When a tenant reports two things in one message, split them explicitly (“logging the window screen separately so it doesn’t get lost”). When something arrives by phone call, drop a one-line summary into the thread right after.
Do this and a text-based system stays reconstructable — any issue’s full history is one scroll. Skip it and you’re back to screenshots and memory, which is the exact failure that makes people swear off texts entirely. This rule is also the tedious one, which is why it’s the part worth handing to software: Tenvo, for instance, turns each incoming text or email into its own ticket, auto-sends the templated receipt from Rule 2, threads every later reply to the right issue, and gives you a daily digest of what’s open — while every outbound message beyond that receipt waits for your approval. The tenant just keeps texting; the structure happens on your side.
Rule 4: Know your local written-notice rules
Repair clocks, habitability standards, entry notice, and what counts as “written notice” are set by your state and city, and they vary more than most landlords expect. In some places a text likely satisfies a written-notice standard; in others, statutes or your own lease contemplate something more formal. Deadlines differ the same way — essential services like heat and water typically carry short clocks, everything else a “reasonable time” that means different things in different statutes.
So: for routine matters, texts plus your log are a sound operating record. When something touches habitability — no heat, no water, mold, anything a tenant might escalate — follow the text with whatever formal notice or documentation your jurisdiction expects, and get the actual rules from your state landlord association or a local attorney once, in advance, rather than mid-dispute. No tool or template makes a response legally compliant; that part stays with you and local law.
What accepting texts doesn’t mean
It doesn’t mean 24/7 instant response. Set the expectation alongside the channel: routine requests get a receipt fast and attention during business hours; emergencies use the call route from Rule 1. Tenants accept boundaries easily when the receipt is reliable — it’s silence, not office hours, that breaks trust.
Accept the texts. Add the receipt, the threads, the emergency route, and a once-a-week review of what’s open, and you’ll have a system sturdier than most portals achieve at this scale. And if you’d rather the receipt-and-threading layer ran itself while you keep final say over every message, that’s the specific job Tenvo does — $29/month, built for landlords with 1–20 units whose maintenance already lives in texts.