Pylon vs Plain: A Runbook for Property Manager Support

A tenant reporting no heat in winter or an active water leak needs a response measured in minutes, not a place in a general queue behind routine maintenance requests. Build a distinct emergency category from day one, with a routing rule that gets it in front of whoever can dispatch a vendor immediately, regardless of which channel the tenant used to report it, a portal, a phone call, or a text. This is the request type worth over-building rather than under-building, since the cost of a missed emergency, both in tenant relations and in potential property damage, is far higher than the cost of a slightly over-cautious routing rule.

A tenant who reports an emergency and hears nothing for hours will usually escalate on their own, calling a second number, emailing the property owner directly, or posting publicly, none of which reflect well on your management company even if the underlying repair gets handled reasonably. A fast acknowledgment, even before the actual fix is scheduled, does most of the relationship work here.

A property owner asking for an updated statement or a question about a specific line item on last month's report is an accounting and reporting question, not a maintenance one, even though it might arrive through the same general inbox. Route these to whoever owns owner relations or accounting directly, and keep them out of the same queue a maintenance coordinator is triaging, since mixing the two means either the owner's question waits behind a maintenance emergency or a genuine maintenance issue gets deprioritized behind a routine reporting question.

A vendor updating you on a repair's status, whether they're on site, what they found, when they'll finish, needs a way back into the same ticket a tenant or owner is watching, without giving the vendor full access to your internal systems. Whichever tool you choose, confirm it supports a vendor-facing update path, whether that's a simple reply-by-email option or a limited portal view, so a vendor's status update doesn't require your team to manually relay information between two separate systems.

A maintenance request isn't actually closed when the vendor finishes the repair, it's closed when the invoice is reconciled and, if it's a tenant-caused issue, billed back correctly. Build your queue to track the full lifecycle, not just the report-to-dispatch portion, since a maintenance request that gets marked resolved the moment a vendor is scheduled tends to lose track of whether the invoice ever actually got processed or the tenant charge-back ever got applied.

This gap is easy to miss because the tenant's experience of the request genuinely does end once the repair is done. The property owner's experience doesn't end until the cost shows up correctly, or doesn't, on their statement, which means the request needs to stay open in your system well past the point where it feels finished to everyone else involved.

A tenant asking about a lease renewal date or a specific clause needs a straightforward path to whoever handles leasing, without being funneled through the same maintenance triage a leaking faucet would go through. This is usually lower volume than maintenance, so it doesn't need the same real-time urgency, but it does need a distinct category so a leasing question doesn't sit behind a queue of maintenance tickets it has nothing to do with.

A support setup that works fine on a quiet spring week can fall apart during a heat wave or a hard freeze, when emergency maintenance requests spike across every property at once. Once you've configured either tool, walk through your worst recent month, the week multiple units lost heat during a cold snap, for instance, and check whether the emergency routing would have actually held up under that volume, not just in the calm week you happened to be testing it.

Run this replay against a bad month:

1. Pick your worst recent month, such as the week several units lost heat during a cold snap, and list the emergency requests that arrived.
2. Check whether the emergency category would have reached whoever can dispatch a vendor immediately, whichever channel the tenant used.
3. Confirm owner reporting questions stayed out of the maintenance coordinator's triage queue during the spike.
4. Verify each maintenance request could be followed from the first report through the vendor invoice to any tenant charge-back.
5. Adjust routing rules wherever the replay showed a delay, then repeat the test after the next seasonal spike.