Your maintenance ticket disappeared. The question is whether you can prove why.
A tenant reports mold in the bathroom. Someone acknowledges it. Six months later, the tenant is gone, the staff member who acknowledged it has moved on, and when the question finally comes up — at a Residential Tenancies Branch hearing, in a Google review, in a phone call from a lawyer — nobody in the office can say with certainty what was promised, when, or why it stalled.
This isn't a story about one bad company. It's the default failure mode of any property management operation that relies on people remembering things across staff turnover, competing priorities, and months of elapsed time. The request was real. The acknowledgment was real. What's missing is a record that survives the people who made it.
That's the problem I build for. Not a phone system. Not a chatbot. A layer that makes sure a promise made to a tenant — or a deadline set by law — doesn't quietly evaporate.
01 The pattern, not the anecdote
This pattern shows up across the industry, not just locally. A few things come up often enough, across different companies and different tenants, that they're worth naming as a pattern:
- A maintenance request is submitted — by phone, by email, through a portal — and then nothing happens for weeks or months, even after follow-up.
- A fix is promised verbally or in writing, and later the company has no record of ever receiving the original request, even though the tenant does.
- A health or safety issue (mold, pests, a heating failure) gets addressed only under pressure — an escalated complaint, a public review, formal follow-up — and quietly deprioritized again once the pressure lifts.
- A legally-timed obligation, like returning a damage deposit, slips past its deadline because nobody was tracking the date.
- Staff turnover breaks the thread entirely: a new portfolio manager inherits a file with no memory of what was promised to whom.
None of this requires a dishonest company. It requires an ordinary one, understaffed, running on inboxes and sticky notes, where the failure mode isn't malice — it's that nothing outlives the person who wrote it down.
Manitoba gives tenants a real venue for this: if a landlord doesn't act after a written repair request, a tenant can file for a binding repair order with the Residential Tenancies Branch. That process exists precisely because "we forgot" or "we don't have a record of that" is common enough to need a government remedy. For a property management company, that's not just a service failure — it's exposure. Property managers in Manitoba operate under The Real Estate Services Act, registered through the Manitoba Financial Services Agency, and the registrar can levy penalties up to $500,000 for misconduct. Being unable to produce a clear record of what was promised and when isn't a good position to be in, whether the audience is a tenant, a regulator, or a courtroom.
02 What's already out there — and where it stops
There's no shortage of AI tools aimed at property management right now, and I want to be upfront about that rather than pretend otherwise. Several companies offer voice AI that answers the phone 24/7 and triages maintenance calls. Others plug directly into platforms like AppFolio, Buildium, or Yardi and route work orders automatically. A few explicitly market Canadian-hosted data as a selling point.
I'm not building another version of that. Those tools solve "did someone answer the phone." They generally don't solve "can we prove, six months later, what we promised and whether we followed through" — because that's a different problem: not intake, but accountability over time. A phone system that answers a call and creates a ticket doesn't automatically ensure that ticket gets revisited if it stalls, that a promised fix is tracked to completion, or that a health-and-safety issue can't be quietly closed without someone taking responsibility for that decision.
And I'll say clearly: hosting data in Canada is a preference many clients reasonably want, not a legal requirement under Canadian federal privacy law for this kind of data. I won't oversell it as compliance. What Manitoba law does require is registration and conduct standards for anyone providing property management services to a third party — and that's the piece worth building around.
03 What I actually build
The system sits alongside whatever intake channel you already use — phone, email, a portal, doesn't matter. It doesn't replace your front desk or your existing software. It adds a layer underneath:
Every commitment gets a record that outlives the person who made it. When a repair is promised, or a timeline is given, the system logs it against the unit and the tenant, with the date and who said what. If the person who made that promise leaves the company next month, the record doesn't leave with them.
Nothing stalls silently. If a ticket sits open past its expected resolution window, it surfaces again — to a supervisor, not just back to the original assignee's inbox. A problem doesn't get to quietly age out because everyone's attention moved elsewhere.
Health-and-safety issues can't be closed without a reason on record. Pests, mold, heating failures — these get flagged so that closing the ticket requires someone to state why it's resolved, not just mark it done. If the same issue reopens, that's visible too, instead of looking like a fresh, unrelated complaint each time.
Legally-timed obligations get tracked automatically. Damage deposit return windows, notice periods for rent increases under the Residential Tenancies Act — these get a countdown, not a date somebody has to remember to check.
Every judgment carries its source. If a ticket was marked resolved, low-priority, or "tenant responsibility," there's a record of who made that call and on what basis. If it's ever questioned — by a tenant, by the RTB, by a regulator — you're not reconstructing the story from memory.
None of this replaces a person's judgment. A human still decides what's urgent, what's resolved, and what gets escalated. The system's job is narrower: make sure that judgment leaves a trail, and make sure nothing falls through simply because time passed and staff changed.
04 What this doesn't fix
I want to be honest about the edges of this, because overselling it would undercut the whole point.
This doesn't fix billing disputes, prorated rent calculations, or utility charge disagreements — those are accounting problems, and belong in your accounting system, not here.
This doesn't fix a company that doesn't want to follow through. A record of a broken promise is still a broken promise. What it does is make that record impossible to lose or "not have," which changes the incentives — but it can't manufacture goodwill that isn't there. If the underlying problem is that leadership doesn't prioritize follow-through, this system will make that visible, not force it to change.
This isn't a phone-answering service. If your main pain point is that nobody picks up the after-hours line, there are several established tools built specifically for that, and I'd point you to them rather than pretend this solves it.
05 If I'm not around
The code and the data are yours. Nothing is locked behind a system only I can touch — you can export it or hand it to another developer at any time. Full documentation comes at handoff. Every entry in the system carries its source, so if something breaks or looks wrong, anyone with basic technical skill can trace it rather than take my word for it.