Maintenance triage, working example for Bottom Line Property Management

The three tickets in the queue below are illustrative, invented sample requests, not real tenant data. The first is modeled on the pattern described in the January 2026 BBB complaint, a leak dispatched to repair workers repeatedly before its source was identified, not a copy of that complaint. The unit numbers, tenant names, and technician names are mine, invented so no real tenant appears here.

Anything in [square brackets] is a number or a decision I refused to invent.

Try the intake step yourself

This is what a tenant fills out before a ticket is ever logged. Fill it in and submit to see how it gets triaged below. (Illustrative - nothing here is saved anywhere but this browser tab.)

What the system pulled out

Extracted, live from your answers

The queue this morning

Sample requests, sorted by how likely each is to turn into a repeat dispatch or a tenant showing up at the office, not by arrival time.

1Needs a person's judgment before dispatch, held for review

1Routes automatically, but flagged as a repeat visit

1Clear symptom and location, safe to route straight to a trade

Held, needs a person before dispatch Rule 1 fired Rule 2 fired

What arrived

Tenant

Ceiling still leaking after two visits

This is the third time I'm reporting [BLPM-4471], unit [3B]. Two different repair guys already came out and neither one fixed it, the ceiling is still staining and now it's spreading toward the closet. I don't know if it's my unit or the one upstairs.

What the system pulled out

Extracted

Unit / location: [3B], ceiling, spreading toward closet
Symptom: Water staining, worsening, source not visually confirmed
Prior dispatches: 2 technicians, neither resolved it
Decision required: Yes, whether the source is this unit's plumbing or the unit above needs someone to check both before a third technician is sent
Escalation risk: Third repeat visit, tenant already noting confusion over which unit is at fault

Drafted note, waiting for a person to route

Office voice

Hi [tenant name], Two visits without a fix on the same leak is on us, thank you for flagging it a third time. Before I send anyone else out, I'm having [maintenance lead] check whether this is coming from your unit or [unit above, e.g. 4B], so we send the right trade the first time instead of guessing again. You'll hear back by [follow-up date]. [office rep] Bottom Line Property Management

Why this doesn't get auto-routed to a trade. Two prior dispatches already failed on this same ticket, that's exactly the pattern from the January 2026 BBB complaint, technicians sent out repeatedly before the source was identified. The system's job here is to stop the pattern by holding the ticket for a person to check both units before a third truck roll, not to guess which trade to send.

Routed automatically Rule 3 fired Repeat-contact flag

What arrived

Tenant

Disposal still won't reset

My garbage disposal in [BLPM-4488], unit [7A] kitchen, still won't turn on. I already tried the red reset button underneath like the last note said, it didn't help.

What the system pulled out

Extracted

Unit / location: [7A], kitchen, garbage disposal
Symptom: Will not power on
Tenant already tried: Manual reset button, no effect
Decision required: No, appliance trade dispatch is the standard next step once a reset fails

Routed to trade, PropertyWare ticket opened

Auto-routed

Hi [tenant name], Since the reset button didn't fix it, this needs a look in person. I've opened [BLPM-4488] in PropertyWare and routed it to [appliance trade] directly, no need to re-describe it when they arrive, they'll see the reset attempt already noted. Bottom Line Property Management

Why this one still routes on its own. A single symptom, a single confirmed unit, and one failed troubleshooting step already ruled out is enough detail to send the right trade the first time. The system logs that the tenant already tried the reset step so the technician doesn't repeat it.

Routed automatically Rule 3 fired

What arrived

Tenant

Faucet won't stop dripping

The bathroom faucet in [BLPM-4502], unit [12C] keeps dripping even when it's fully off. Not urgent, just wanted it on the list.

What the system pulled out

Extracted

Unit / location: [12C], bathroom faucet
Symptom: Constant drip, does not stop when off
Urgency: Tenant-flagged as non-urgent
Decision required: No, clear single-fixture symptom, standard plumbing dispatch

Routed to trade, PropertyWare ticket opened

Auto-routed

Hi [tenant name], Got it, [BLPM-4502] is logged in PropertyWare and routed to [plumbing trade] as a standard, non-urgent repair. You'll get a scheduling text directly from them. Bottom Line Property Management

Why this is the easy case. One fixture, one clear symptom, one location, nothing ambiguous. This is the shape of request that's cheapest to get right, and the one where a missing detail is least likely, which is exactly why it's safe to route without a person re-reading it first.

The rules underneath

These are the part worth arguing with.

WhenA ticket has already had one prior dispatch that didn't resolve it, especially anything involving water, shared walls, or a floor/unit above or below.

ThenIt's held for a person to check adjacent units or systems before a third technician is sent, and the queue label counts the dispatch number so nobody has to reread the history to know.

The January 2026 BBB complaint describes exactly this: repeated technician visits before anyone checked whether the source was a different unit entirely. Counting prior dispatches is what catches that before it becomes a third failed visit, or a complaint.

WhenThe intake form is missing a clear location, a clear symptom, or urgency isn't answered.

ThenThe system asks one follow-up question before a ticket is created at all, rather than logging a vague ticket and letting a technician discover the gap on-site.

Indeed reviews from your own maintenance staff describe the department as disorganized, with tenants showing up in person. A ticket that's missing the unit number or the actual symptom is the raw material for that disorganization; catching it at intake is cheaper than catching it on a truck.

WhenA request has one clear symptom, one clear unit and fixture, and no prior failed dispatch attached.

ThenThe system opens the PropertyWare ticket and routes it to the matching trade immediately, no person needs to re-triage it.

Most requests are this simple. Automating the clean cases is what frees a person's attention for the repeat leak and the missing-detail ticket, the two shapes of request that actually generate complaints.

What this demo can't do

The parts a proposal would normally leave out.

The PropertyWare integration is the product. A real version needs write access to PropertyWare to actually open a ticket and read access to see whether a unit has an open or recently-closed ticket already. Without that connection, this collapses into a nicer-looking form.

This is built around one specific, documented gap. One BBB complaint and a handful of Indeed reviews are the evidence, not a claim that most maintenance requests go wrong. Most presumably get handled fine; this targets the pattern where they don't.

Which trades exist, how they're dispatched, and your actual escalation thresholds are your call. The "when" conditions above are a starting guess, worth a short conversation before this gets built for real.

This only structures and routes, it never decides whether a leak is this unit's responsibility or the one above's. That determination still needs someone to physically check. The system's job is making sure that check happens before the third technician, not after.