AI maintenance triage reads each tenant request, works out what the problem is and how urgent it is, tries to resolve it with the tenant, and only then sends it to a vendor. For a property management team, the value is simple: fewer requests reach a person, the ones that do arrive sorted and complete, and emergencies are never left sitting in a queue. GoLando does this entirely by text message, so tenants need no app, portal or phone call, and your team keeps the property management software it already uses.
This guide explains what triage actually involves, where AI helps most, what Canadian landlords should keep under human control, and how to measure whether it is working.
TL;DR
- Triage means sorting every request by urgency, issue type and next action. AI does the sorting at the moment the tenant reports, including at 2 a.m.
- The biggest gains come from three steps: collecting complete details up front, troubleshooting simple issues before dispatch, and escalating real emergencies immediately.
- Keep emergency policy, access, responsibility and tenancy decisions with your team, and keep records of every request.
- Measure time to first response, time to resolution, repeat visits and after-hours calls for a month before and a month after you start.
- GoLando handles intake, troubleshooting, emergency detection and vendor dispatch by SMS and works alongside your existing software, including Buildium.
What maintenance triage means in practice
Triage is the decision made on every incoming request: how urgent is this, what exactly is wrong, who should deal with it and by when. In a small portfolio the owner makes that call from memory. At a few hundred units it becomes a daily job for a coordinator, and at several thousand it becomes a team, a call line and an after-hours rota.
A manual process usually breaks in the same places:
- Incomplete requests. “Heat not working” tells you almost nothing. Is it one unit or the whole floor? Is the thermostat on? Is there a smell of gas? Each missing answer costs a round of back-and-forth.
- Inconsistent urgency. Two coordinators rate the same leak differently, or a message sent on Friday evening is read on Monday.
- Unnecessary dispatches. A tripped breaker or a reset button becomes a paid service call.
- Poor records. Phone conversations leave no trail, which matters when a tenant later disputes how quickly you acted.
AI triage addresses these at the point of intake. According to a Canadian workflow guide from AIforBC, AI can organize requests by property and issue type, flag possible emergency language, spot missing details and draft an acknowledgement and work-order summary. That is a sound description of the job: structure the request, so the people and vendors downstream can act on it.
How AI triage handles a request from first text to closed job
Here is the sequence, using a realistic example: a tenant in a Halifax apartment texts at 9:40 p.m. that there is water coming from under the kitchen sink.
1. Intake by text
The tenant sends a message to a single number. There is nothing to install and no login to remember. That matters more than it sounds: requests that are hard to submit tend to arrive as phone calls, emails to the wrong person or a note under the office door. Our page on tenant maintenance requests by text message describes how the tenant side works.
2. Classification and emergency check
The AI reads the message and places it in a category (plumbing, heating, electrical, appliance, pest, access and so on) and checks it against emergency signals. Water, no heat in winter, electrical sparking, smoke and gas smells are the obvious ones. Anything that looks like an emergency is escalated at once instead of waiting for a morning queue.
In our example, the AI asks follow-up questions: is the water actively flowing, can the tenant reach the shut-off valve under the sink, and is any water near electrical outlets? Answers decide whether this is a “shut off the valve and wait for a plumber tomorrow” case or an overnight dispatch.
3. Troubleshooting
Many requests do not need a tradesperson. A dishwasher that will not start, a bathroom fan that has gone quiet or a heater that is off because of a tripped breaker can often be resolved with two or three guided steps. Doing this before dispatch reduces unnecessary service calls, which is where a lot of maintenance spend leaks away. We cover the approach in more detail in our guide to AI repair troubleshooting for rental properties.
Troubleshooting has to be bounded. The AI should never ask a tenant to open a panel, work near gas or do anything a reasonable person would leave to a licensed trade. Safety first, savings second.
4. Dispatch to an approved vendor
When a professional is needed, the request goes out with the details already captured: unit, issue, photos if sent, what the tenant has tried and the urgency level. GoLando coordinates with approved service providers, either your own in-house or preferred trades or vendors from the GoLando Vendor Network. See automated maintenance vendor dispatch for how that step works.
5. Scheduling, follow-up and closure
The job is not finished when the vendor is booked. Someone has to confirm the appointment with the tenant, check that the vendor attended, and ask the tenant whether the problem is fixed. In a manual process, this last step is the first one dropped. Automating it gives you a closed-loop record for every request.

Why emergencies need a clear policy, not just a fast response
In Canada, maintenance speed is not only a customer service question. It is a legal one, and the rules differ by province.
In Ontario, the Landlord and Tenant Board looks at what is a “reasonable time” to fix a problem. A property manager’s summary of the Ontario standard explains that vital services such as water, fuel, electricity, gas and heat (from September 1 to June 15) need the most immediate attention, that health and safety risks such as major leaks and non-working smoke detectors are urgent, and that landlords should acknowledge requests within 24 hours and document every step. Other provinces, including Nova Scotia, New Brunswick and Newfoundland and Labrador, have their own tenancy rules and time expectations, so confirm the standard for each province you operate in.
The practical conclusion is the same everywhere: you need a written emergency definition, an acknowledgement that goes out quickly, and a record of what happened. AI triage is well suited to the second and third. The first is yours to set.
What to keep with your team
AIforBC’s guidance is that a person should confirm emergency status and keep decisions about tenancy rules, responsibility, access, vendor assignment, timing and the official record. We agree with that framing, and it is how we suggest property managers set up any triage workflow:
- Write your emergency list (leaks, no heat, electrical hazards, broken exterior locks, fire and carbon monoxide alarms, flooding, sewage) and make sure your triage tool treats it as the minimum.
- Decide who is the escalation contact after hours, and what happens if that person does not answer.
- Decide who is responsible for what: tenant-caused damage, landlord repairs and condo-corporation items are different conversations.
- Keep the original tenant messages, not only a summary of them.
Safety-related requests also reach you in less obvious forms. A tenant asking about a loose stair rail, or about childproofing rental stairs, is raising a safety matter that deserves a real answer and a recorded follow-up, not a generic reply. Good triage categories include a safety and hazard class for exactly this reason.
Privacy and oversight for Canadian operators
Tenant messages contain names, unit numbers, schedules and sometimes details about health or family circumstances. Before adopting any AI tool, review how data is used, who can access it, where it is stored and how long it is retained. AIforBC recommends testing a small sample of historical requests while keeping the originals, then tracking corrections, missed facts and escalations. That is a sensible pilot design for any provider.
The Condominium Management Association of Ontario’s magazine makes a related point in its Summer 2025 issue: AI should complement human oversight rather than replace it, and AI-generated communications deserve review. Treat that as a design principle. The AI handles volume and speed. People set the rules and handle the exceptions.
Fitting triage into the software you already run
Most property management companies have already invested in a system of record for leases, accounting and work orders. Replacing it to get better maintenance intake is rarely worth the disruption, and it is not what triage needs.
The more useful question is how requests and updates move between systems. A property manager’s overview of AI triage notes that integrations through APIs can pass resident information, requests, work orders and updates between systems, though its examples are U.S. platforms. For Canadian operators the question to ask of any provider is concrete: which of my systems does it connect to today, and what does my team still enter by hand?
GoLando integrates with Buildium and is built to complement existing platforms rather than replace them, so your established workflows stay in place while the maintenance communication and coordination layer is automated. Our guide to connecting maintenance to your property software walks through how that works.
Rolling out across multiple buildings
For regional operators with properties in, say, Halifax, Moncton and Charlottetown, we suggest a staged rollout:
- Start with one building or one small group of buildings, ideally one with a steady volume of requests.
- Run the AI alongside your current process for a few weeks and compare how requests were classified.
- Adjust your emergency list and vendor preferences based on what you see.
- Add buildings in groups, so each new property inherits settings that already work.
Starting with after-hours intake is a practical first step. It addresses the gap with the clearest cost: the late-night call that wakes a manager, and the weekend message that sits unread. Our guide to handling after-hours maintenance goes through the options.
What to measure
Triage is only worth keeping if the numbers move. Be careful with promises here: the AIforBC guide describes a workflow, not proven ROI, so the proof has to come from your own portfolio. Pick a small set of measures and record them for one month before starting and one month after.
| Measure | What it tells you | How to capture it |
|---|---|---|
| Time to first response | How quickly a tenant knows the request was received | Request timestamp to first reply |
| Time to resolution | Whether the whole chain is faster | Request timestamp to tenant-confirmed completion |
| Requests resolved without a vendor | Whether troubleshooting prevents unnecessary calls | Closed jobs with no dispatch |
| First-visit fix rate | Whether requests reach vendors with the right information | Vendor visits that closed the job |
| Repeat requests per unit | Whether fixes hold | Same unit, same issue within 60 days |
| After-hours contacts to staff | Interruptions to your team | Calls or messages handled by people outside office hours |
| Spend per unit | Whether cost is moving | Maintenance expense divided by units |
A property manager’s guidance on vendor scorecards recommends tracking technician arrival, first-visit fixes, response-window compliance and tenant completion confirmation. These are good vendor-side measures to add once your own response numbers are stable.
GoLando’s dashboard shows maintenance requests, vendor activity, property maintenance history, expenses and performance metrics in one place, which gives you the portfolio view without compiling it from separate spreadsheets.
A worked example of the headcount question
Imagine a 600-unit portfolio with two maintenance coordinators. Growth to 900 units would normally mean a third hire. The better question is how much of the coordinators’ week is spent on work that does not need judgment: asking tenants for details, booking appointments, chasing vendors for updates and logging closures. If a large share of the week goes to those tasks, automating them is what lets the same two people carry a larger portfolio. We make no claim about what share your team will save. Measure your own week first, using the table above.
What good triage looks like in a vendor-facing process
Tenants are one side of the conversation. Vendors are the other, and a poorly briefed vendor is the most common cause of a second visit.
A good dispatch message includes the unit and building, the access arrangement, a plain description of the problem, what the tenant already tried, photos where available and the urgency level. The vendor then arrives with the right parts and expectations. Whether you use your own trades or the GoLando Vendor Network, the same discipline applies. Jobs distributed through the network carry a network fee of 5 to 10%, described on our vendor page. Tenants and vendors never pay to use the platform.

Choosing a triage approach: the questions to ask
When you compare options, including other maintenance platforms such as Latchel, Property Meld and EliseAI, ask each of the following of any provider, and of yourself:
- Does the tenant need an app or portal, or can they simply text?
- Does it only record and route requests, or does it troubleshoot, detect emergencies and coordinate the repair?
- Can you use your own vendors, and is a vendor network available if you want one?
- Does it work with the software you already run, or does it ask you to change it?
- Is it built for Canadian operators and Canadian tenancy conditions?
GoLando is Canadian-owned and operated, with Canada as its initial market. It handles requests entirely by SMS, from intake and troubleshooting through dispatch and follow-up, and it complements your property management software instead of replacing it.
Getting started with GoLando
GoLando is a subscription service tiered by portfolio size. Plans are published at golando.ca/pricing:
| Plan | Monthly | Annual |
|---|---|---|
| Starter | 39 CAD | 390 CAD |
| Pro | 69 CAD | 690 CAD |
| Pro+ | 149 CAD | 1,490 CAD |
| Mogul | 249 CAD | 2,490 CAD |
| Scale | 449 CAD | 4,490 CAD |
| Enterprise | from 999 CAD | n/a |
Smaller landlords can begin on a lower tier, and larger property management companies running hundreds or thousands of units can look at Scale or Enterprise. Our page on AI maintenance coordination for rental properties explains what is included, and the property management companies page is the place to start if you manage a larger portfolio.
If you want to see how triage would work on your own requests, the pricing page lists each plan and the next step.
Our view on AI triage
Most maintenance software records a request. It does not do anything about it. Someone still has to read the message, ask the tenant what they meant, decide whether it is urgent, find a vendor, book the visit and check that the job was done. That chain of small tasks is where a coordinator’s day goes, and it grows in step with the number of units.
We built GoLando around the idea that the chain itself should be automated, not just tracked. A tenant texts. The AI asks the right questions, troubleshoots what can be troubleshot, recognises emergencies and coordinates the repair with an approved vendor. Your team sees the result in one dashboard and keeps the software it already uses.
We are also clear about where people stay in charge: your emergency definitions, your vendors, your policies and your records. Automation should carry the volume so that your team has time for the decisions that need judgment.
For a portfolio of a few hundred units or a few thousand, the question is not whether to have triage. Every operator already does, by hand. The question is whether it scales with your team or without it.
Ryan
FAQ
What is AI maintenance triage?
It is the automated sorting of tenant maintenance requests by issue type and urgency, followed by the next action: troubleshooting with the tenant, escalating an emergency or dispatching a vendor. It replaces the manual step where a coordinator reads each message and decides what happens next.
Does AI triage replace my property management software?
No. Triage handles the maintenance conversation and coordination, while your software remains your system of record for leases, accounting and portfolio management. GoLando integrates with Buildium and is designed to work alongside your existing platform.
Do tenants need to download an app?
No. With GoLando, tenants report issues by text message to a single number. There is no app, portal or phone call involved, which makes it easier for tenants to report problems early and gives your team a written record of each request.
How should we handle emergencies?
Write your own emergency list, covering leaks, no heat, electrical hazards, fire and carbon monoxide alarms, flooding and sewage, and set an after-hours escalation contact. Check the repair timelines in your province’s tenancy rules, since Ontario’s expectations differ from those elsewhere. GoLando detects emergencies and coordinates the response, while your team keeps ownership of policy.
How long before we can judge whether it works?
Record response time, resolution time, vendor dispatches and after-hours contacts for one month before you start, then compare the same figures after one month of use. A single building is enough for a first comparison.




