The call comes in at ten past eleven on a Sunday. A tenant in a first floor flat has water coming through the ceiling. The letting agent's mobile is off, the office line is on voicemail, and the tenant has already tried the emergency number on the fridge magnet from the previous managing agent. By the time anyone picks it up, the flat below has a ruined carpet and two very unhappy occupants.
That is the story property managers tell when they start looking at call handling. It is a real problem and worth solving. But it is only half of the problem, and fixating on it is how agencies end up buying a service that fails them on the other half.
Two completely different jobs on one phone number
A property management call answering service is being asked to do two things that have almost nothing in common.
The first is triage. A small number of calls describe a situation that genuinely cannot wait: escaping water, no heating in January, a suspected gas leak, a front door that will not lock. These need someone to ask the right questions in the right order, decide quickly, get a tradesperson moving, and tell the tenant what happens next. Speed matters more than polish. Getting the decision wrong in either direction costs real money.
The second is capture. The bulk of what comes down the line is not an emergency at all. It is a landlord asking when the rent statement lands. A tenant chasing a repair that was logged a fortnight ago. Someone querying a deposit deduction. A contractor confirming access. A prospective tenant asking whether the flat on the portal is still available. None of it needs a decision at midnight. All of it needs to be recorded accurately, attached to the right property and tenancy, and put in front of the right person so nothing falls through.
Those two jobs pull in opposite directions. Triage wants a short decision tree and permission to act. Capture wants patience, detail and clean data entry. Most providers sell a single generic script that splits the difference, which means it is too slow and cautious for the emergency and too shallow for the admin. You get a service that wakes your on-call plumber for a dripping tap and takes a message so vague that your property manager has to ring the tenant back on Monday morning to find out what they actually wanted.
If you are weighing up call handling for the first time, it is worth reading our broader guide to choosing an answering service for a small business alongside this, because the fundamentals apply. What follows is the part that is specific to managed property.
Write the emergency definition down, then hand it over
The single most useful thing a property manager can do before buying anything is to define, in writing, what constitutes an emergency across the portfolio.
Most agencies already have a version of this in their tenancy paperwork. Very few have translated it into something a call handler can act on. There is a difference between a clause that says "emergencies only outside office hours" and a decision tree that says: if the caller reports water ingress, establish whether it is contained, whether the stopcock has been located, whether it is affecting a neighbouring property, and whether there is any contact with electrics. The first is a legal position. The second is operational.
Your definition also needs to account for the stock you actually manage. A block with a shared boiler needs different escalation from a street of individual houses. A property with a vulnerable occupant on your records changes the threshold on loss of heating. HMOs bring fire safety questions that a standard flat does not. If a provider takes your brief without asking about any of this, you are getting a template.
Be equally explicit about what is not an emergency, because that is the list that protects your callout budget. Lost keys. A broken appliance that was not supplied by the landlord. A tap that drips. Noise from a neighbour. Each one gets a scripted, sympathetic response and a logged job for the next working day, not a call to a tradesperson at 2am.
The escalation chain is where services actually fail
Triage is the easy half. Escalation is where things quietly break.
A workable chain needs several things that a generic setup rarely has. It needs a current on-call rota, held somewhere the answering service can see it, with a clear owner for updating it when someone swaps a weekend. It needs trade categories, because ringing a general handyman about a gas appliance is a waste of two phone calls. It needs a defined fallback when the first contact does not pick up, and a second fallback after that, ending with a named person at the agency who will be woken up. And it needs a spend authority: an amount the on-call tradesperson can commit to without approval, above which somebody has to be asked.
It also needs to close the loop. A tenant who has been told "someone will be in touch" and hears nothing for two hours will ring again, then ring the landlord, then leave a review. A handler who says "Dave the plumber has confirmed he will be with you within the hour and here is the reference number for this job" has resolved most of the anxiety before the van arrives. Confirming attendance, rather than just placing the call, is the detail that separates a service that helps from a service that forwards your problem.
The routine calls need structure, not sympathy
For everything that is not an emergency, the job changes entirely. Here the value is in the quality of the record.
A useful log entry identifies the property and unit unambiguously, names the caller and their relationship to the tenancy, states what they want in terms your team can act on, notes anything time sensitive, and confirms what the caller was told to expect. A useless log entry says "tenant rang about repair, please call back".
The difference is worth thinking about in terms of double handling. Every vague message generates a return call, which generates another attempt when the tenant is at work, which generates a chase from the landlord asking why nothing has happened. Structured capture removes that whole cycle. It also means routine calls can be triaged by priority the next morning rather than in the order they happen to sit in an inbox.
Ask precisely how the information reaches you. Writing into your property management system through an integration is ideal. A consistent structured summary into a shared inbox or ticketing tool is workable. A transcript emailed as unformatted text is a message service pretending to be a workflow, and your team will end up rekeying everything.
Records matter more here than in most sectors
Property management is a documentation business. When a habitability complaint escalates, when a deposit dispute goes to adjudication, when a landlord queries an invoice for an emergency callout they never sanctioned, the question is always the same: what was reported, when, and what did you do about it?
That makes the call log an evidential asset rather than an administrative by-product. You want timestamps, the substance of what was reported, the escalation steps taken and who they were taken with, and the advice given to the tenant. You want it retained for as long as your compliance position requires and retrievable by property rather than by date. Ask any prospective provider where that record lives, who owns it, whether you can export it, and what happens to it if you leave. A service that cannot answer those questions is creating a gap in your files.
There is a data protection dimension too. Tenant contact details, vulnerability flags and access arrangements are all personal data. Whoever answers your calls is processing it on your behalf, which means the arrangement needs to be documented properly rather than agreed on a phone call.
Consistency at the front door
One overlooked benefit of getting this right is what it does to the growth side of the business. The same number that fields a leak at midnight often takes the enquiry from a landlord with four properties who is unhappy with their current agent. Those calls arrive without warning, frequently outside office hours, and they are lost easily. Handling them with the same structure you apply to repairs, capturing the portfolio size, the stock type and a callback window, turns a switchboard into part of the pipeline.
That is the logic behind treating call handling as a system rather than a safety net, and it is the same thinking that runs through Nimble Dingo's AI growth systems: the front door of the business should be consistent, whoever is calling and whenever they call.
Brief it properly or do not bother
The uncomfortible truth is that a property management call answering service is only as good as the brief behind it. Handed a clear emergency definition, a maintained rota, spend limits, fallbacks and a destination for structured notes, a competent provider will handle your out-of-hours load better than a duty phone passed round the office. Handed nothing, it will take messages, wake your contractors for the wrong reasons and generate work rather than absorbing it.
Start by writing the two scripts you actually need, one for triage and one for capture, and use them as the test when you speak to providers. If a supplier is not interested in the distinction, they are selling you the generic version.
If you want a second opinion on where your calls are leaking before you commit to anything, get in touch and we will walk through it with you.