Most maintenance complaints aren't about slow repairs. They're about silence. A resident submits a request and hears nothing for days. That gap between "submitted" and "completed" is where frustration builds, phone calls multiply, and online reviews turn negative.
This guide gives you response-time targets, status-update workflows, and copy-paste scripts you can put to use today.
Why Maintenance Complaints Are Really Communication Problems
You're halfway through a tour when your phone buzzes: three residents are calling about the same work order, each asking the same question. Nobody told them a part was on order. Nobody told them when the contractor would arrive. The repair itself is on track. The communication isn't.
This pattern shows up across properties. Requests arrive by phone, text, email, paper form, and portal with no unified tracking. Response times go unpublished, so residents invent their own expectations. Nothing bridges the gap between "submitted" and "completed."
Owners feel this gap too. According to Buildium's research on how rental owners evaluate property managers, 43% expect a same-day response to maintenance issues and another 42% expect a response by the next business day, and response time is one of the top criteria owners use to judge performance. When residents don't get that same responsiveness, the fallout is familiar to anyone who's worked a leasing desk: more negative reviews, softer renewals, and staff time spent explaining status instead of scheduling repairs.
The categories worth getting right first are the ones residents feel fastest. A Hemlane analysis of more than 193,000 rental work orders found that plumbing, HVAC, appliance, and electrical issues together account for roughly 71% of all requests. These are the categories where unclear communication does the most damage, since they hit comfort and habitability directly.
Everything below is built to fix that this week: no new software required, just a clear process and consistent scripts.
Set Response-Time Expectations Before the First Work Order
Publish your response-time targets before residents ever need to submit a request: during move-in, on your property website, in the resident app, and in every confirmation email. Once residents know what "fast" means at your property, they stop guessing.
Start by defining three priority levels:
- Emergency – active threats to safety or property, requiring immediate action. Examples: fire risk, gas smell, a major leak flooding a unit, loss of heat in winter.
- Urgent – essential comfort compromised without immediate danger. Examples: A/C not cooling, refrigerator out, the only toilet in the unit not flushing.
- Standard – cosmetic or low-impact issues. Examples: broken blinds, loose cabinet doors, paint touch-ups, non-essential lighting.
Attach a response and resolution target to each level:
- Emergency: acknowledge within 15–60 minutes, send someone onsite the same day (even after hours), and put in a safe temporary fix or full repair same day.
- Urgent: acknowledge within 4 business hours, schedule within 1–3 business days, and complete within 3–5 business days.
- Standard: acknowledge by the next business day and complete within 7–10 calendar days.
Put these targets in your welcome packet and on the resident portal. A published SLA does more to prevent complaints than almost any other change on this list.
Standardize How Residents Submit a Request
One primary submission channel, with accessible backups, cuts down on lost requests and confused residents. Centralizing everything in a single system keeps every request auditable and searchable.
Make the digital path the default: a portal or simple online form accessible from any device. Required fields should include unit number, contact information, a detailed issue description, priority selection, permission to enter if the resident will be absent, preferred time windows, pet details, and the option to attach photos or a short video.
Digital submissions beat the alternatives on every measure that matters to your team. They create a timestamped, auditable record automatically, cut down on lost requests and re-typed notes, and give techs photos to diagnose the issue before they arrive. Paper forms get misplaced and require manual entry. Phone-only requests are hard to track and rarely come with images.
Keep paper forms in the office for residents who need them, but enter every one into the same system immediately so nothing lives outside the record. At minimum, every request needs the unit number, access instructions, pet details, a best contact window, written consent to enter, and photos when possible.
Build an End-to-End Communication Flow
Map every request from "submitted" to "completed" against these touchpoints:
- The resident submits a request through the portal, an email link, or a paper form that staff enter into the system.
- Staff or the system assigns the work order to a technician based on skill and availability.
- An automatic acknowledgment goes out with a ticket number, priority level, and estimated response window, so the resident knows the request landed.
- Status updates go out at each milestone: scheduled, in progress, parts on order, completed.
- A follow-up message or short survey goes out after completion to confirm the fix held and close the loop.
Picture this on a resident's portal timeline: "Request Submitted (Monday 9:14 a.m.) → Acknowledged (Monday 9:30 a.m.) → Scheduled (Tuesday 2:00 p.m.) → Parts Ordered, ETA Friday → Repair Completed (Friday 11:00 a.m.)." One clear "we've ordered the part, ETA Friday" message heads off three or four follow-up calls.
The flow has to be identical regardless of channel. Whether the request came in by phone, email, or paper, log it in the same system so the history ties back to one work order no matter who picks up the phone next.
Response-Time Scripts for Leasing and Office Teams
Use consistent wording across your team so every resident hears the same message, no matter who they reach.
Phone: acknowledging a new request during business hours"Thank you for calling. I've logged your request for [issue]. Your ticket number is [number]. Because this is [priority level], our team will [action and timeline]. I'll send a confirmation email today. Is there a time window when someone can access your unit?"
Phone: an upset resident asking about a delayed repair"I understand you expected someone sooner. Your ticket shows 'Scheduled' for [date]. We're waiting on [parts/vendor confirmation], and I'll send an update as soon as I have one."
Phone: clarifying priority without being dismissive"Can you help me understand more? Is this causing a safety risk or active damage? If so, we treat it as an emergency. If it's causing discomfort but no immediate danger, we classify it as urgent and schedule within 1–3 business days."
Email/text: new request confirmation"Hello [Name], your request '[description]' for unit [number] has been submitted. Ticket #[number]. Priority: [level]. Expected response: [window]. If this becomes a safety issue, call our emergency line at [number]."
Text: technician running late"Hello [Name], our technician for ticket #[number] was delayed. New estimated arrival: [time]. Apologies for the inconvenience."
Text: parts on order"Hello [Name], for ticket #[number], we need to order a replacement part. ETA: [date]. Once it arrives, we'll schedule installation. Thank you for your patience."
Setting business-hours boundaries"Our maintenance team is onsite Monday through Friday, 8:00 a.m. to 5:00 p.m. Emergencies after hours are routed to our on-call technician at [number]. Non-urgent requests submitted after hours are acknowledged the next business day."
Using Technology to Cut Repeat Calls
Maintenance software isn't required to run this process, but it removes a lot of manual tracking. Look for tools that can:
- Auto-create and assign work orders from incoming requests, and route status updates through whichever channel each resident prefers.
- Trigger status updates automatically at each stage, so residents aren't calling in to ask what "in progress" means.
- Show open versus overdue work in a dashboard, filtered by priority, so managers triage emergencies first.
- Let techs update status and attach before-and-after photos from the field.
- Keep a full communication history tied to each unit for quick reference during disputes.
If you're rolling this out for the first time, phase it in: start with digital requests and automatic acknowledgments, then layer in real-time status updates once the basics are stable. Feeding everything into your existing property management system keeps communication from scattering across handwritten notes, spreadsheets, and side apps.
Communicating Emergencies vs. Routine Repairs
Post plain-language guidance near elevators, in welcome packets, and on the resident portal:
"If you smell gas, see active flooding, or have no heat in winter, call our emergency line at [number] immediately. These are emergencies."
"For urgent but non-life-threatening issues like an A/C not cooling or a refrigerator not keeping food cold, use the portal and select 'Urgent' so we can triage quickly."
Set the same clarity for after-hours coverage: emergencies go to a 24/7 call line with an on-call tech, while non-emergencies can be submitted anytime through the portal but are processed the next business day. For any scheduled work that affects unit access, such as inspections or larger projects, give residents 24–48 hours of written notice.
When a resident texts a non-emergency at midnight, respond the next morning with the same care: "Thank you for reporting this. I've logged your request under ticket #[number]. Our team will contact you by [time] to schedule. Our portal also lets you track progress and upload photos anytime."
Tracking emergency work orders over time also surfaces patterns worth acting on, like the same building losing heat every January because of aging equipment in the boiler room.
Training Your Team to Communicate Consistently
Run a 30–45 minute session with leasing consultants, assistant managers, and community managers. Build a communication playbook that covers:
- Priority definitions and response-time targets.
- The scripts and templates above, ready to copy into email or text.
- A rule that every verbal promise, like "we'll be there Tuesday," gets logged in the work order with date, time, and staff name.
Follow up with monthly 10–15 minute huddles to review recent complaints about communication and any work orders that generated repeat calls, then adjust scripts or timelines accordingly. Track a few simple metrics over time: average acknowledgment time, the share of work orders with at least one status update, and the number of repeat "what's the status?" calls per week.
Turning Maintenance Data Into Fewer Complaints
Every request, timestamp, and status change is a data point you can use to improve the process. Watch for:
- Request volume by building or unit type.
- Response and completion times by priority level.
- Recurring issues that keep affecting the same units or buildings.
If Building C logs the same HVAC failure every August, schedule preventive maintenance before summer starts. Adjust staffing and contractor schedules around known peak seasons, and time janitorial and seasonal inspections to head off emergency volume.
Include communication metrics in owner reporting alongside maintenance activity: fewer complaints, fewer repeat calls, better ratings. When follow-up call volume drops after a process change, share that win with the onsite team.
