How do I sort tenant calls so repairs, rent and leasing each reach the right person?

This page may contain affiliate links from which Blur Studio earns commissions.

Property management phone calls genuinely split into a handful of distinct types, and most of the friction tenants and staff both feel comes from every call starting in the same place before someone works out which bucket it actually belongs in. A menu fixes that for the routine cases, but not for the one case where speed actually matters most.

A business phone system such as KrispCall is one way to build that menu, with a multi-option phone tree that lets tenants sort themselves into repairs, rent or leasing before anyone picks up. It is one option among a few, and the plan tier and the emergency path matter more than which specific vendor you use, both covered below.

The three buckets most tenant calls fall into

Repairs and maintenance, rent and billing questions, and leasing inquiries from prospective tenants cover the large majority of calls a property management office gets. Each genuinely needs a different person or team, and letting a caller self-select at the start, rather than your front desk manually asking and transferring every single call, saves real time on both sides.

Setting up the menu

On KrispCall, a multi-option phone menu (called Phone Trees in its plan documentation) is part of the Advance plan at $40 a user a month, the same tier that includes ring strategies and call monitoring. The cheaper $15 Starter plan only offers a basic recorded greeting, not an actual branching menu, so if you're trying to build "press 1 for repairs" on Starter, that's the ceiling you're hitting.

Keep the menu to the three real categories, plus a path for anything that doesn't fit (a general option, or "press 0," routed to a live person rather than leaving callers with no fallback). The general method for any business is in setting up a phone menu so customers reach the right person.

The emergency exception a menu can't handle

This is the part worth being genuinely careful about. A water leak, a gas smell, a lockout in freezing weather, these can't wait for a tenant to navigate a menu, leave a message, and wait for a callback the next business day. A static phone tree, by itself, treats every "repairs" call the same whether it's a dripping faucet or a flooded unit. You need a separate, live path specifically for anything genuinely urgent, either a dedicated emergency line that always rings through to a real person or an answering service, not folded into the same menu option as routine maintenance requests.

Say so explicitly in the menu itself: "if this is a genuine emergency, press 9 now to be connected immediately" as a clearly separate option from "press 1 for a routine repair request," so tenants with a real emergency don't sit through the rest of the menu first. An AI receptionist can also sort these calls overnight, as described in AI receptionist for property management after hours maintenance calls.

Step by step

1. List your actual call types and roughly what proportion of calls each represents, so the menu reflects real volume, not a guess.
2. Assign a person or team to each category, including who covers the genuine emergency path, and confirm that's a live answer, not a voicemail box.
3. Build the menu with the emergency path given clear, early priority, not buried as a sub-option under general repairs.
4. Add a live fallback for anything that doesn't fit, so no caller is left with no way forward.
5. Test it, including the emergency path specifically, to confirm it actually reaches a live person and not a dead end.

What I'd actually tell a property manager

The single most common mistake I'd flag here isn't getting the menu options wrong, it's treating the emergency path as just another menu branch instead of a genuinely different, higher-priority system. A tenant with a burst pipe calling at 11pm and getting the same generic after-hours voicemail as someone asking about a lease renewal is a real liability and reputation problem, not just an inconvenience. If you can't staff a live emergency line yourself around the clock, a human answering service for just that one path is worth the cost; it's cheap relative to the damage (and liability) a delayed emergency response can cause.

A worked example: a mid-size property manager handling a winter freeze

Say a property manager overseeing 40 units gets hit with a cold snap that causes three separate pipe-freeze calls in one night, all coming in after normal office hours. Before setting up a dedicated emergency path, all three calls would have gone to the same general after-hours voicemail as a routine lease-renewal question, with no way to tell which message needed attention in the next ten minutes versus the next business day. With a clearly separated emergency option connecting straight to an answering service staffed around the clock, all three calls get a live response that night, and the answering service can immediately triage which ones need an emergency plumber dispatched now versus which can be contained (shutting off a valve, for instance) until morning. The cost of that answering service for one night is trivial against the cost of a flooded unit that sat undiscovered until a tenant's own voicemail got checked the next business day.

Common mistakes with property management call routing

• Treating "repairs" as one undifferentiated menu option. A dripping faucet and a flooded unit are both technically maintenance issues, but routing them identically means the urgent one waits exactly as long as the routine one, which is precisely the gap a genuine emergency path is meant to close.
• Assuming tenants will remember to call a separate emergency number. Most tenants only have the one number they've always used; the emergency path needs to be reachable from that same number, through the menu, not a second number nobody thinks to use under stress.
• Setting up the emergency path once and never testing it again. Staff turnover, an answering service contract lapsing, a forwarding setting that silently reverts, any of these can quietly break the one path that absolutely cannot fail. Periodic real-call testing, not just a one-time setup, is what actually keeps it reliable.

When a simpler setup is still the right call

For a very small landlord with a handful of units and a personal relationship with each tenant, a full menu system can feel like overkill, and it often is. If tenants already have your direct cell number and call it for everything, adding a formal phone tree doesn't necessarily improve anything and might just add friction to a relationship that already works. The menu and emergency-routing setup earns its place specifically once volume and unit count grow past what one person can personally track and prioritize by memory, not as a default for every property owner regardless of scale. Texting tenants about routine notices, covered in how to text tenants about maintenance and rent, can cut call volume further.

How I'd approach this

If you manage enough units that tenant calls, maintenance requests and leasing inquiries would benefit from being logged automatically against the right property and unit rather than handled purely by phone, that's worth connecting your phone system to whatever property management software you already run. I build that kind of integration for property management clients, and the emergency-routing piece specifically is something I'd always build as a separate, higher-priority path, never folded into the general menu.