Elevator callbacks are one of the clearest signals an elevator service company produces. Tracked as a formal maintenance KPI, callback frequency shows whether your preventive maintenance program is working, where routes are stretched too thin, and which units need a modernization conversation. Your building owners notice callbacks long before you put them on a scorecard, so it pays to measure them as carefully as they do.
What counts as an elevator callback?
A callback is an unplanned service visit triggered by a malfunction, an entrapment or a customer complaint. It is separate from a scheduled maintenance visit. Callbacks come from mechanical failures, door problems, controller faults and misuse. Some are billable and many are not, but all of them take labor, truck time and a slot on the schedule.
To make elevator callbacks useful as a KPI, split them by type. The most useful cuts are total callbacks, billable versus non-billable callbacks, and repeat callbacks on the same unit. Elevator Strategic Hub lists billable versus non-billable callbacks among the KPIs an elevator company should track, and recommends reviewing the scorecard every week, “not monthly, not quarterly.”
The callback benchmark building owners hear
The number most often quoted is about four callbacks per elevator per year. A Mitsubishi Electric guest post on BOMA on the Frontline, written for building owners and managers, calls four “the current industry average” and encourages owners to choose providers who keep callbacks to one or less per unit per year. That is the number many of your clients are reading.
A consultant writing in Elevator World gives more field detail. On his own routes he averaged 1.5 callbacks per unit per year on hydraulic elevators and 2.5 on traction elevators. He describes 4 per unit per year as the typical industry average, and 6 for high-use units such as hospitals, dormitories and care homes, not counting misuse, vandalism, water intrusion or power outages. He also notes that a typical route mechanic handles 70 to 90 units, and that adding 40 to 50 more pushes the mechanic into answering callbacks instead of doing maintenance, which snowballs into more callbacks.
Why elevator callbacks are the right KPI to watch
Uptime, mean time between failures, first-time fix rate and response time all matter. Callback rate has a practical advantage. It comes straight from dispatch and work order data you already collect, and it ties directly to customer satisfaction and contract renewals.
When callbacks rise on a route or a unit, the data points to a question you can act on. Was the last maintenance visit completed in full? Was a known wear part skipped? Did the route change hands? Reviewed every week, callback data shows the health of the whole service operation as well as single units.
There is a cost side too. Every callback uses field labor, vehicle time and dispatch attention. On full-maintenance contracts those hours often cannot be billed, and they push out the planned visits that prevent the next callback.
How to calculate callbacks per unit per year
Divide total callbacks over 12 months by the number of units under contract. Then run the same calculation at four levels, because each one answers a different question:
- Company: how you compare with the 4-per-unit benchmark your clients hear.
- Route: whether the route structure and unit count are sustainable.
- Technician: where training or maintenance quality needs attention before clients complain.
- Unit: which equipment may need a repair or modernization proposal for the building owner.
Reviewing these numbers weekly gives you time to step in before one problem unit puts a whole contract at risk.
What high callback rates signal to clients
Building owners feel callbacks in ways that never show up on your side of the relationship. Their staff field tenant complaints, coordinate with your dispatcher and absorb the frustration. The BOMA guest post makes the point that tenants who never file a complaint may still hurt a building’s reputation by sharing their frustration with colleagues and friends.
Providers with consistently low callback rates can give each property planned attention instead of reacting to emergencies. That shows up as more thorough visits and better equipment outcomes, and it builds owner confidence that is hard for a competitor to displace at renewal time.
Is your callback data accurate?
A callback KPI is only as good as the records behind it. If callbacks are logged inconsistently, categorized differently by each dispatcher or closed without a cause, the number becomes noise. A technician who closes a callback without noting whether it was a door, a mechanical fault or misuse leaves nothing to spot the pattern that would prevent the next one.
Reliable tracking needs standard work order types, a short list of cause categories, and service history tied to each unit and route. In TS Cloud, callbacks can be tagged by type and cause and reported by unit, route and technician, and mechanics can see a unit’s service history in the mobile app before a visit. For practical steps on bringing the number down, see our guide on how to reduce elevator service callbacks, and our checklist for elevator dispatch software.
Treat callbacks the way your clients already do
Your best building owners already watch callback frequency, even if they never call it a KPI. They notice when the same elevator needs service three times in a quarter, when response times stretch during a busy week, and when a reliable unit starts acting up after a route change. If you are not watching it as closely, you start every renewal conversation behind.
Frequently asked questions
What counts as an elevator callback?
An elevator callback is an unplanned service visit triggered by a malfunction, an entrapment or a customer complaint, as opposed to a scheduled maintenance visit. Tracking billable, non-billable and repeat callbacks separately makes the number more useful.
What is a good elevator callback rate?
About four callbacks per elevator per year is widely cited as the industry average. A consultant writing in Elevator World reported 1.5 per unit per year on hydraulic routes and 2.5 on traction routes, and a Mitsubishi Electric guest post for building owners recommends providers who keep callbacks to one or less per unit per year.
How do you calculate callbacks per unit per year?
Divide the total number of callbacks over 12 months by the number of units under contract. Run the same calculation for the whole company, each route, each technician and each unit.
How often should callback data be reviewed?
Weekly. Elevator Strategic Hub recommends reviewing elevator company KPIs every week rather than monthly or quarterly, so problems on a route or unit surface while there is still time to fix them.
See TS Cloud in a demo
TS Cloud is the cloud ERP and field service platform from Total Service, built for independent elevator contractors, and for HVAC and specialty contractors. Book a free 30-minute demo to see callback tracking by unit, route and technician, and how your service work, units and technicians come together in one system.