An AI answering service for property management: what it costs
What rings a property management line, what an AI agent handles end to end, what it hands to a person, and what it costs next to per-minute services.
Published: 2026-08-25 · Author: Ahmed Heshmat · 9 min read
In short: An answering service for a property management company is really a triage service. The useful questions are which calls it can finish without a person, which calls it must hand to one, and what the pricing model does to your bill in a bad month. An AI agent finishes the calls that have written answers, files maintenance requests into your management software, and escalates real emergencies to your on-call person. Ours runs a setup fee, then about $1,000 a month, flat. Human services meter by the minute or by the call. On lines we run for a Toronto property management and brokerage operation, 0 of 277 calls in the production sample were missed, and 74 of them came in after hours.
Key takeaways
- A property management line is not an unbounded stream of problems. It is a short list of repeating call types, and that short list is the reason the work is automatable at all.
- The dividing line is written policy. An AI agent can finish any call your team currently answers from a documented answer. Any call that ends in a judgment about a person, a dollar amount, or a legal step gets handed to a person.
- After hours is not an edge case. In a 277-call production sample, 74 calls arrived outside office hours, and none of the 277 were missed.
- Human answering services bill by the minute or by the call, which means your worst month is also your most expensive one. Our voice agents are a setup fee, then about $1,000 a month, published.
- Evaluate every vendor, us included, on the same five questions: the escalation path, where the data lands, who owns the emergency policy, the price in writing, and the running cost separate from the fee.
What actually rings a property management line
This post is the long version of our property management answering service page: what the phone line actually contains, what software can finish, and what the honest bill looks like.
Before we put an agent on a line, we sit with the call log, because the composition of the line decides the build. Across the operations we work in, the same categories come up in roughly the same shape.
Maintenance. The largest category, and it splits three ways. A small number of genuine emergencies. A steady stream of routine repairs. And a long tail of status calls, which are tenants calling back because nobody told them what happened after the first call. Status calls are not really maintenance volume. They are a symptom of a silent ticket queue, and they fade when acknowledgement gets fast. We wrote about that mechanism in what AI actually does to tenant response times.
Leasing. Prospects calling on a listing. Is it still available, are pets allowed, what about parking, can I see it Thursday. These calls are worth real money and they have a short shelf life, because a prospect who reaches voicemail dials the next listing.
Rent and balances. How do I pay, what do I owe, did the e-transfer land, why is there a charge on my ledger. Nearly every one of these has a written answer somewhere in your operation.
Owner calls. Two kinds. A current owner who wants to know what is happening with their unit, and a prospective owner asking what management costs. The second one is a lead, and it deserves better than a voicemail box.
Vendor callbacks. A contractor confirming access, asking for a tenant's number, or closing out a job. Short calls, but the information has to attach to the right work order or it dies in somebody's text thread.
The awkward after-hours categories. Lockouts, noise complaints, parking disputes. These are policy calls, not technology calls. Whether you send a locksmith at 2am is a decision you make once, in writing, in daylight. The phone system's job is to apply that decision, not to improvise it.
What an AI agent finishes, and what it hands off
The clean way to think about the split: the agent finishes calls that have a written answer, and hands off calls that end in a judgment.
Finished end to end, on the lines we run:
- Maintenance intake. Identify the caller and the unit, ask the structured follow-up questions a good dispatcher would ask, refuse to file something too vague to act on, and create the work order in the management software with a callback number and access notes attached. The follow-up questions are where the value lives, and we have written about why in where AI actually lands in property management.
- Questions with written answers. Payment methods, office hours, application steps, whether you manage a given building. The least glamorous calls on the line, and the biggest clearable volume.
- Leasing capture. The listed facts of the unit, qualifying details taken down, a viewing booked where the calendar allows, and the lead created in the CRM instead of on a sticky note.
- Vendor coordination. Take the callback, attach it to the ticket, flag the office when the job needs a decision.
Handed off, by design:
- Real emergencies. A flood, no heat in a Toronto January, a gas smell, a break-in. The agent's job is to recognize the category fast, capture the address and the callback number, tell the caller what happens next, and put the on-call person on it. Recognition and escalation, not diagnosis.
- Judgment about people or money. Arrears conversations, disputes, lease decisions, anything whose next step is legal. In Ontario that boundary matters. We build the intake, drafting, and tracking around those workflows. The judgment and the legal steps stay with a person.
- Anyone who asks for a person. The agent hands off without arguing. An AI that traps callers in a loop is how trust in the whole system dies, and it is the failure everyone remembers from two decades of bad phone trees.
The rule underneath all of this is the one we keep coming back to: automate the intake, never the judgment.
The after-hours reality
Answering services exist because offices close and phones do not.
Here is the production sample we publish. Across 277 calls on lines we run for a Toronto property management and brokerage operation, 74 came in outside office hours. That is just over a quarter of the volume arriving when nobody is at a desk. And 0 of the 277 were missed. Not a low miss rate. Zero, because software has no second line, no lunch, and no end of shift. The full sample, the method, and the caveats about what we can and cannot claim from it are published in the impact study.
The after-hours slice is the part worth staring at, because those calls skew consequential. People call at 11pm because the problem cannot wait, or because their shift just ended and this is the first free minute they have had. Either way, what that caller needs in the moment is evidence that someone competent now owns the problem. A voicemail box is evidence of the opposite, and it is what most of those 74 calls would have reached.
What it costs, and what the pricing models actually mean
Two numbers matter here: ours, and the meter's.
Ours is published. Voice agents run a setup fee, then about $1,000 a month, and the full price list for everything else we do is in what AI consulting actually costs. The same honesty that post applies to us applies here: the fee is for our work, and the system runs on telephony and model usage that bill separately. Ask for both numbers in writing before you sign anything, from us or from anyone.
A human answering service prices differently, and the model is worth understanding before you compare quotes. There are two dominant shapes.
Per minute. You buy a monthly bundle of receptionist minutes and pay a published overage rate for everything beyond it. PATLive, one of the longest-running services in the category, structures its published rate card exactly this way: plans built around included minutes, an overage rate above the bundle, cheaper per minute as the tiers climb. The model is transparent. It also means the bill is a function of how long your callers talk, and a tenant with a leak at midnight talks.
Per call. A flat rate for each answered call, regardless of length. AnsweringServiceCost.com's property management breakdown puts typical per-call rates at $1.25 to $2.75, with emergency handling billed higher, at $3.00 to $6.00 per call. Predictable per interaction, and it quietly rewards the vendor for keeping calls short and taking a message rather than finishing the job.
Neither model is dishonest. But both meter the exact calls you most want handled. The burst-pipe weekend, the February cold snap, the marketing push that finally makes the leasing line ring: under a meter, each of those is your most expensive month. Under a flat monthly fee, a volume spike is our problem, and the incentive points the right way. We want calls finished, not billed.
There is a second difference that matters more than the rates. A traditional service answers with a person and delivers a message, usually by email or text, and someone on your team still reads it, retypes it, and files it the next morning. What you are buying from us is the finished action: the work order created, the lead in the CRM, the on-call person already contacted. The real comparison is not minutes against a flat fee. It is a message pad against an outcome.
How to evaluate one, ours included
These are the answering-service version of the questions in our pricing post. Ask them of every vendor. Ask them of us.
- Walk me through a call you cannot handle, step by step, at 2am. Who gets contacted, in what order, on what channel, and what happens if the first person does not pick up. A vendor with a real product answers in specifics. A vendor with a demo changes the subject.
- Where does the call end up? If the answer is a transcript in your inbox, you are buying a message pad with better grammar. The call should end as a record in the software your team already works from.
- Who writes the emergency policy, and what happens to a call that does not fit it? If the vendor says the AI figures it out, leave. It is your policy. The software's job is to apply it, and to fail loudly to a person when it cannot.
- What is the price, and when can I have it? In writing, before the demo impresses you. A vendor whose price only exists after a discovery call is telling you something about how the relationship will go.
- What is the monthly running cost, separate from your fee, and can my team turn the system off without calling you? The first half is the second bill that most proposals leave out. The second half is whether you own a system or rent a dependency.
Where this fits
If you are evaluating the category for a property management company, the property management answering service page lays out exactly what our version handles, hands off, and costs. It is the system described in this post. For how the phone work connects to everything else we build for operators, start with AI for property management, and for the version of this that is not specific to property management, voice agents is the parent page.
And if the honest answer for your operation is a small plan with a human service, or nothing at all for now, that is the answer you will get on a discovery call. We lose some deals that way. The ones we keep tend to work.
Frequently asked questions
What does an AI answering service for property management cost?
Ours is a setup fee, then about $1,000 a month, published alongside everything else we charge in what AI consulting actually costs. Two notes for comparison shopping: telephony and model usage bill separately from our fee, and human services meter per minute or per call, so quotes only become comparable once you know your call volume and your after-hours share.
Can it create work orders in Buildium or AppFolio?
Yes, and that is most of the point. The agent files the request directly into the system your team already works from, with the unit, the callback number, the structured details, and the urgency your policy assigns. We build and maintain those connections as part of the deployment. The specifics are on our Buildium automation and AppFolio automation pages.
What happens when a tenant calls with a real emergency?
The agent recognizes the category, captures the address and callback number, tells the caller what happens next, and contacts your on-call person. What counts as an emergency is your written policy, not the model's guess, and writing that policy down is part of the build. A call that does not fit the policy is handed to a person rather than resolved by a guess.
Is it worth it under 100 doors?
Sometimes no, and we will say so. If your line rings a handful of times a day and someone answers it, you do not have the problem this solves. Where small portfolios do see the value is after hours and leasing, because those are the calls the owner is currently taking personally at dinner, or missing entirely. If a small plan with a human service fits your volume better, that is the recommendation you will get on a discovery call.
Will this replace my front desk or my coordinators?
No, and we decline engagements where that is the goal. The agent takes the after-hours calls, the repeated questions, and the retyping. Your people keep the conversations that need judgment, which is the work they were hired for. AI should give people back their time, not take their jobs.
How is this different from a human answering service?
A human service answers with a person and delivers a message, and you pay by the minute or by the call. An AI agent finishes the scripted majority of calls and writes structured records into your management software, and you pay a flat monthly fee. Human services still make sense where every call is a genuine conversation. A property management line is mostly not that, which is why the economics favor software with a clean handoff to your own people.