Rental Maintenance Troubleshooting: Fix It by Text First

Why troubleshooting is where maintenance goes wrong

A maintenance request has four stages: intake, diagnosis, repair and follow-up. Most software tracks intake and repair well. Diagnosis is the weak point, because it needs a conversation.

Consider a common request: “No heat in unit 4.” The cause might be a tripped breaker, a thermostat with dead batteries, a closed valve on a baseboard heater, a failed furnace, or a building-wide boiler problem. Each has a different fix and a different cost. Without a conversation, the default is to send a vendor and find out on arrival. If the cause was a thermostat setting, you have paid a call-out fee for a two-minute fix.

The usual alternatives both cost staff time:

• A phone call. Someone on your team asks questions, tries to interpret what the tenant describes, and often calls back after the tenant finds the breaker panel. After hours, the call lands on whoever is on call.
• An in-person visit. A maintenance technician or superintendent attends to look. This is thorough but slow, and it is the most expensive way to discover that a reset button was the issue.

There is a third pattern that is worse than either: the request sits in a queue because nobody has time to call the tenant back. The tenant waits, the problem grows, and the next message is a complaint.

The scale of the issue is not small. According to Statistics Canada’s 2022 housing data, 8.6% of renter households lived in housing in need of major repairs, compared with 6.6% of owner-occupied households. Rental housing carries more repair demand, so the quality of your intake and diagnosis process matters more for you than for a typical homeowner.

What a good troubleshooting process looks like

Whether you run it by phone, text or in person, the structure that works is the same.

1. Identify the emergency first

The first question is never “what is the issue?” It is “is anyone in danger, or is property being damaged right now?” Active flooding, a gas smell, smoke, no heat in winter, a failed exterior lock and exposed wiring all go to an emergency path immediately, before any troubleshooting.

Definitions vary by place. In Toronto, urgent service requests are those affecting electricity, gas, heat and water, and the city’s standards expect a faster landlord response for those than for everything else. Ottawa’s guidance adds security concerns, accessibility equipment failures and anything that could reasonably be expected to cause harm. If you operate in Atlantic Canada, check the rules of your own province. Nova Scotia’s Residential Tenancies Act, for example, allows a landlord to enter without written notice when there is an emergency and entry is necessary to protect life or property.

2. Ask the same diagnostic questions every time

Consistency is what makes triage cheap. For each category, a short script covers most cases:

The goal is not to turn tenants into repair technicians. It is to rule out the cheap fixes safely and to give a vendor a clear description when a visit is needed. Anything involving gas, live electrical work or structural elements should never be left to the tenant.

3. Collect evidence at intake

Photos, short videos and the tenant’s own wording make the diagnosis better and the record stronger. A photo of a water stain on a ceiling tells a plumber more than “leak in bathroom.” It also shows the date the issue was first reported, which matters later.

4. Decide: tenant fix, scheduled repair or urgent dispatch

Every request should end in one of three outcomes, with a recorded reason. If the tenant fixed it, record that. If a vendor is needed, send the diagnosis along. If it is urgent, escalate to the on-call contact and the right trade at once.

5. Follow up

A closed ticket is not a fixed problem. A quick message a day or two after the visit (“Is the heat working properly?”) catches incomplete repairs before they become repeat calls.

Water problems: the category that cannot wait

If you are going to tighten one part of your process, make it water. Health Canada’s guide to addressing moisture and mould states that unless the cause of a moisture problem is identified and solved, mould will reappear. The practical point for troubleshooting is that drying out a surface does not end the job: someone must find the source.

A federal study of construction problems in multi-family residential buildings found moisture to be the most common complaint, reported in 36 of the 44 buildings reviewed, and linked it to poor flashing and reliance on caulking to keep rain out. For a manager, this means a recurring “small leak” in the same area of a building is a signal to inspect the building envelope, not to keep patching.

A water-specific triage flow should ask:

1. Is water actively flowing? If yes, can the tenant shut off the fixture valve or the unit’s main?
2. Is it near electrical outlets, light fixtures or the panel?
3. Is it coming from above, meaning another unit may be involved?
4. How long has it been happening, and is there a photo?

Any answer pointing to active spread, electrical proximity or an upstairs source should escalate immediately and notify the manager.

Why written records matter as much as the repair

Troubleshooting by phone leaves little behind except a note, if someone wrote one. That becomes a problem when a repair cost is disputed or a tenant says they reported something months ago.

CMHC’s guidance on maintenance and repairs for renters points to the value of regular maintenance in forecasting repairs and limiting unexpected emergencies, and notes that some provinces require emergency contact information to be posted in a visible place. British Columbia’s repairs and maintenance guidance shows how landlords and tenants share a duty to limit loss: tenants report problems promptly, and landlords act on them. Rules differ by province, but a dated, written record of what was reported, what was asked, what was advised and what was done helps in every jurisdiction.

A useful record has these fields for every request:

• Unit, tenant and date and time reported
• Tenant’s description, plus photos
• Questions asked and answers given
• Whether it was classed as an emergency
• Whether the tenant tried a fix, and the result
• Vendor dispatched, date attended, cost
• Follow-up confirmation

Over a year, that log also becomes a capital planning tool. If the same boiler appears in thirty tickets, repair spending is telling you to replace it.

How text messaging changes the workflow

Text is the channel tenants already use. There is nothing to install, no portal password to forget at 11 p.m. with a flooded kitchen, and no need to be free to talk. A tenant can send a photo from the spot where the problem is.

What has been missing is troubleshooting over text. Until recently, diagnosis still needed a person on the other end, whether by phone or in the unit. GoLando’s conversational maintenance agent holds that conversation by SMS: it asks the diagnostic questions, walks the tenant through safe checks, identifies emergencies, and, when a professional is needed, coordinates the repair with an approved vendor. You can see how that looks from the tenant’s side on our page about tenant maintenance requests by text.

The operational effects are the ones you can reason about without any invented numbers:

• Fewer unnecessary service calls, because simple causes are ruled out before a vendor is booked.
• Fewer inbound calls to your office, because tenants are not waiting on hold or for a callback.
• Less after-hours interruption, because the first conversation happens without your on-call person, who is only pulled in when the situation calls for it.
• Better vendor handoffs, because the vendor receives a described problem, photos and access details rather than “tenant says it’s broken.”
• A complete record of each request without anyone typing notes.

Perspective: what we see in maintenance operations

We built GoLando because maintenance coordination is where property management teams lose the most hours for the least value. Most software on the market tracks a request once someone has entered it. It does not do the conversation that turns a vague complaint into a clear job.

Our view is that triage should be automated and judgment should not be. A tenant describing a leak needs questions asked in the right order, immediately, at any hour. A manager deciding whether to replace a roof section or approve a large invoice needs to keep that call. So we automate the repetitive conversation and leave the decisions with you.

We also do not think you should have to change your core system to get this. GoLando is not property management software. It complements the platform you already use, integrates with Buildium, and works with your own vendors or, optionally, our vendor network. Your leasing, accounting and tenant files stay where they are.

We are Canadian-owned and operated, and Canada is our first market. That shapes how we think about it: provincial rules differ, winters are hard on heating systems, and a no-heat call in January is a different kind of problem from a dripping tap. Triage has to reflect that.

— Ryan

What to look for in any troubleshooting system

Whether you build a process on your own or adopt a tool, test it against these criteria.

The last row is the one most often ignored. Every extra step between a tenant and a report delays the report, and a delayed report is usually a bigger repair.

A worked example: no heat on a cold night

Here is how the process plays out for a no-heat request in a multi-unit building, described as a typical flow rather than a measured result.

1. The tenant texts that the apartment is cold.
2. The agent first asks whether anyone is at risk, such as infants, elderly residents or anyone unwell, and whether the cold is severe.
3. It asks whether the thermostat is on and set above the room temperature, and whether the tenant has checked the breaker.
4. The tenant finds the thermostat batteries are dead and replaces them. The heat comes back. The ticket closes with a record of the cause and the fix. No vendor was sent.
5. In a different case, the thermostat is fine and neighbours also report no heat. The agent flags a possible building-wide issue, escalates as urgent and notifies the manager, and the heating contractor is contacted with the details collected.

In both cases the tenant got a response within minutes of texting, and the manager’s information came from the conversation instead of from a callback.

Getting started without disrupting your team

You do not need to change everything at once. A practical rollout looks like this:

1. Pick a pilot. Start with one building or a handful of properties where maintenance calls are frequent.
2. Write down your emergency definitions. Include your province’s expectations and your own after-hours rules.
3. List your approved vendors by trade. Dispatch is only as good as the vendor list behind it.
4. Tell tenants one number to text. Put it on move-in packages, in the lobby and in your emails.
5. Review the first month of records. Look at which issues were solved by the tenant, which needed vendors and which repeat.

Use our maintenance cost calculator to estimate where your own maintenance spend sits before you start, so you have a baseline of your own to compare against.

Where GoLando fits and what it costs

GoLando is an AI-powered maintenance coordination platform for landlords and property managers. Tenants text; the agent troubleshoots, detects emergencies and coordinates repairs; and a central dashboard shows requests, vendor activity, maintenance history, expenses and performance metrics. It is built for independent landlords as well as portfolios of hundreds or thousands of units, so teams can grow without growing maintenance headcount in step. More detail is on our page for property management companies, and our vendor dispatch page explains how repairs are assigned.

Published plans, billed monthly or yearly:

All prices are in Canadian dollars. Jobs sent through the optional GoLando Vendor Network carry a network fee of 5 to 10%, which vendors pay, not tenants. Full details are on the pricing page.