Maintenance communication fails in two directions. Over-promise — “we’ll have it fixed by Friday!” — and you’re now apologizing for a plumber’s schedule you never controlled. Go silent, and a patient tenant becomes an anxious one who texts twice a day and remembers the episode at renewal time. The messages that avoid both failures are boring on purpose: they confirm what happened, commit only to things you control, and always name the specific issue. Here are twelve you can copy, grouped by stage. Replace the bracketed parts.
Stage 1: When the request arrives
1. The receipt (no repair promise): “Got it — thanks for letting me know about the [bathroom sink]. I’ve logged it and will update you by [tomorrow evening].” The workhorse. Notice what it doesn’t contain: no diagnosis (“probably the washer”), no repair deadline (“we’ll fix it this week”). It commits to exactly one thing — when you’ll communicate next — which you can honor even when the repair slips. This is the message that should go out fast every single time, which is why it’s the one worth automating: Tenvo sends a templated receipt like this the moment a tenant’s text or email lands, then threads everything that follows to the same issue. That receipt is the only message it ever sends on its own — the other eleven below are always written or approved by you.
2. The after-hours receipt: “Received — thanks. I’ll review this first thing in the morning and update you by [noon]. If it turns into an emergency overnight (flooding you can’t stop, gas smell, no heat), call me at [number] — and for gas, leave the unit and call [utility/911] first.” Sets a boundary without going silent, and re-states the emergency route exactly when the tenant might need it.
Stage 2: Getting the details
3. The photo request: “Can you send a photo or a short video of [the leak]? A shot of [the pipe under the sink] helps me send the right person with the right parts on the first visit.” Explain the benefit to them — one visit instead of two — and compliance goes way up.
4. The vague-request follow-up: “Quick check so I get this right: which [bathroom] is it, and is the sink [dripping constantly, or only when the tap runs]? When did you first notice it?” “The sink is broken” could be six different repairs. Ask at most three targeted questions; a longer list feels like an interrogation and gets half-answered.
5. The containment check: “Is it still [leaking] right now? If so, there’s a shutoff valve [under the sink — turn it clockwise]. No worries if you can’t reach it; just tell me either way.” The answer changes your urgency level, and a tenant who can stop the water just turned an emergency into a scheduled repair.
Stage 3: Scheduling the visit
6. The access request: “[Marcos] from [Rivera Plumbing] can come [Thursday] between [1 and 3 pm]. Are you okay with him entering if you’re not home? Anything I should tell him — pets, parking, gate code?” Explicit permission to enter, in writing, plus the pet question that prevents a wasted trip. (Entry-notice rules vary by state — follow yours even when the tenant says “just come in whenever.”)
7. The confirmation: “Confirmed: [Thursday, 1–3 pm], [Rivera Plumbing], for the [water heater]. I’ll send a reminder the day before. Reply here if anything changes on your end.”
8. The day-before reminder: “Reminder: [Rivera Plumbing] comes tomorrow between [1 and 3 pm] for the [water heater]. Still good? Reply here if not.” No-show tenants and surprised tenants both come from skipped reminders. This one costs you fifteen seconds.
Stage 4: When things slip
9. The contractor reschedule: “Update on the [water heater]: [Rivera Plumbing] had to move the visit — the new window is [Monday, 10 to 12]. Sorry for the shuffle; I know you planned around Thursday. Does Monday still work?” Own the inconvenience even when it isn’t your fault, and ask rather than announce. The tenant rearranged their day for you once already.
10. The parts delay: “Update on the [dishwasher]: the [control board] is on order, expected [early next week]. I’ll confirm the install day as soon as it arrives. Nothing needed from you in the meantime.” “No news” is still news. An unprompted delay update reads as competence; the same delay discovered by the tenant’s follow-up text reads as neglect.
11. The still-working-on-it update: “Haven’t forgotten the [fence] — I’m waiting on [a second quote] before scheduling. Next update by [Friday].” Send this before the tenant sends “any update?” A good default cadence: every open issue gets some update at least every three or four business days, even when nothing has changed.
Stage 5: Closing it out
12. The completion check and recurrence instruction: “[Rivera Plumbing] marked the [sink] repair complete. Can you confirm everything looks good on your end? If it acts up again later, reply right here on this thread so I have the full history in one place.”
Two jobs in one message. First, it makes the tenant — not the contractor’s invoice — the definition of done; “completed” repairs that were never confirmed are where recurring problems hide. Second, it routes any recurrence back into the same conversation, so the second visit starts with the whole story instead of “wait, when was this fixed?”
The three rules behind all twelve
If you want the receipt automated and the rest kept firmly in your hands, that split is exactly how Tenvo works: incoming texts and emails become threaded tickets with an instant templated acknowledgment, and every other outbound message waits for your approval. It’s $29/month, built for landlords with 1–20 units.
- Promise communication, not outcomes. Every date in these templates is a date you’ll say something, not a date something will be fixed — until a repair is actually scheduled.
- One issue, one thread. Every message names its specific issue and belongs to that issue’s conversation. The moment updates scatter across chats, you’re managing from memory.
- You send them. Templates speed you up, but a human should read the situation before anything goes out — a form-letter reply to a distressed tenant does more harm than a slow one.