Every property management office has a version of the night phone: a cell that rotates between three people, a voicemail box someone checks at 7am, or a pager that outlived the company that made it. Whatever it is, it decides two things: whether a burst pipe gets a plumber at 2am, and whether your best coordinator quits by spring. Here is how to design it so both come out right.
Key takeaways
- Most after-hours maintenance calls are not emergencies. They need a unit number, a description, and a promise that someone will follow up in the morning.
- The emergency question is a rules question before it is a judgment question. Write the escalation list once and apply it identically on every call.
- An answering line that logs the routine calls and transfers only the rule-matched ones means your on-call person hears about real emergencies and nothing else.
- Human answering services price per call, which makes every tenant call after 5pm billable. AI answering starts at 39 dollars a month and answers three calls at once.
The night phone problem
The night phone fails in one of two directions. Either it is too quiet, meaning voicemail, and the leak under the kitchen sink runs until the downstairs tenant calls at 6am about the ceiling. Or it is too loud, meaning every dripping faucet and every "my neighbor is being noisy" wakes the coordinator whose week it is, and after four months of that they stop answering, which is the quiet failure wearing a different hat.
The fix is not a better person on the rotation. It is separating the calls before they reach a person, so the phone only rings for what actually needs a human at that hour. The call handling guide has a routing plan for the whole office, by call type and hour.
Three kinds of maintenance call
1. The true emergency
Active water, no heat in winter, no power to the unit, gas smell, sewage, a lockout, anything that threatens safety. A small share of night calls, and the only ones that should wake someone. What the on-call person needs is the unit, the issue, and a callback number before they say hello.
2. The urgent but not tonight
Fridge died, toilet will not flush but there is a second bathroom, AC out on a mild night. The tenant wants to know it was heard and when someone is coming. A logged work order with a morning follow-up promise solves it. Waking a coordinator does not make the part arrive sooner.
3. The routine
A dripping faucet, a burned-out hallway bulb, a question about the dryer. Most of the volume. Needs to be logged accurately and nothing else. This is the category that burns out a rotation when it reaches a human at 11pm.
Write the escalation list
You already know what escalates. You have just never written it down in a form that something other than a tired person can apply. Get it on one page:
- Transfer immediately: the emergency list above, plus anything the caller describes as a safety concern.
- Text the on-call person, no transfer: the urgent-but-not-tonight list, so they can decide in the morning or sooner if they choose.
- Log only: everything else, with a clear promise to the tenant of when they will hear back.
- Hours and people: who is on call on which nights, and which vendor line to transfer to for which building.
An AI answering line takes exactly this list and applies it on every call, at any hour, the same way for the first call and the fortieth. Rules you set, applied without being tired. The after-hours comparison covers the other options for the night shift, and the AI receptionist prompt guide has this list written as a playbook you can paste in.
What a logged call looks like
The same call, 11:20pm, as the tenant heard it
The tenant got an answer in one ring, was asked the right questions, and was told what happens next. Nobody woke up. The work order has everything the maintenance tech needs to schedule it without a callback. Compare that to a voicemail that says "hi, it's Maria, the sink thing again, call me."
Who answers: options and cost
| Option | Applies your escalation list | Logs routine calls without waking anyone | Answers 3 calls at once | Rough monthly cost |
|---|---|---|---|---|
| Voicemail | No | Logs nothing usable | n/a | $0, plus the ceiling repair |
| On-call rotation | From memory, at 2am | No, every call wakes them | No | Burnout and turnover |
| Human answering service | Yes, from your script | Yes | Depends on staffing | $300 for 30 calls to $2,100 for 300 |
| AI answering line (callflo.ai) | Yes, identically every call | Yes | Yes | $39 to $997 |
The per-call pricing of human services is the trap for property management specifically. A 200-unit portfolio produces maintenance calls every night, and each one is billable. AI answering meters minutes instead: callflo.ai Starter is 39 dollars a month on annual billing with 120 minutes, VIP is 697 dollars a month with 1,000 minutes and the whole thing built and run for you. A two-minute logged call is two minutes, not a 10-dollar call.
Setting it up in a week
- Write the escalation list on one page. Emergencies, urgent, routine, who is on call, which vendor for which building.
- Sign up and load the list. Paste your website, add the escalation list and your on-call numbers, and hear the agent answer a test call.
- Forward the office line after hours. Read every transcript the next morning. Adjust the list where a call landed in the wrong bucket.
- Count the week. Calls answered, work orders logged, emergencies transferred, and what would have sat on voicemail. No setup fee, no contract, and you do not pay unless you are satisfied.