Elevator service
Elevator service software built around how you already work.
Maintenance contracts by unit, entrapments and callbacks against a response time, annual inspections and safety tests, and a logbook for every car. Set up around how your company already runs it.
The short answer
What software does a elevator service business need?
An elevator service company needs software that tracks every unit as an asset, books contract maintenance visits per unit, logs entrapments and callbacks with response times, and keeps the inspection, test and certificate history the building owner and the inspector ask for. Fieldproxy is set up around your own contracts, checklists and stages, with a technician app that works offline in machine rooms and pits.
How the job runs
A elevator service job, start to finish.
The stages your software has to follow, in the order the work actually happens.
- 1
Contract and units
A building signs a maintenance contract covering specific units: passenger cars, freight cars, escalators, platform lifts. Each unit has its own visit frequency, monthly or quarterly, and its own equipment details. - 2
Routine maintenance visit
The mechanic works the unit's checklist: machine room, controller, car top, pit, doors and safety devices. Findings and readings go into that unit's logbook, not a shared notes field. - 3
Entrapment or callback
A call comes in from the building or the emergency line. It is logged with the time, whether passengers are trapped, and the unit. The clock runs until a mechanic is on site, and the cause and fix are recorded against the unit. - 4
Inspection and safety tests
Annual inspections and periodic load or safety tests are booked ahead of the due date, witnessed where required, and the results and certificate are stored on the unit. - 5
Repair and modernization quotes
Worn parts and deficiencies found on visits or inspections become repair quotes, and aging equipment becomes a modernization proposal, each tied to the unit and the building.
What to record
The checklist for every job.
Whatever system you run on, these are the fields, readings and photos worth capturing every time. Use it as your checklist.
Per unit (the asset record)
- Unit ID, building and car or escalator number
- State or authority registration number
- Type: traction, hydraulic, MRL, escalator, platform lift
- Manufacturer, controller model, year installed
- Capacity, speed and number of stops
- Contract coverage and visit frequency
- Certificate expiry date and last inspection date
- QR code on the controller or machine room door
Each maintenance visit (logbook entry)
- Mechanic name, arrival and departure time with GPS check-in
- Checklist: machine room, controller, car top, pit, door operator, door gibs and tracks
- Safety devices tested: door edges and sensors, emergency stop, alarm bell, emergency phone, emergency lighting
- Hydraulic units: oil level, oil temperature, leaks at the jack and fittings
- Ropes or belts condition noted, brake inspected
- Leveling accuracy at each floor
- Photos of deficiencies found
- Parts used and follow-up work needed
- Building contact signature
Callbacks, entrapments and tests
- Time reported, time dispatched, time on site, time released
- Passengers trapped (yes or no) and how they were released
- Reported symptom, cause found, action taken
- Shutdown or returned to service, with time
- Test type, load used, results and witness name
- Inspector name, result, deficiencies listed and correction due date
Where generic software breaks
Why template tools don't fit.
Most field service software is built for a generic service call. Elevator service companies run a different job.
- The job belongs to the building, but the history belongs to the unit. Generic software logs a visit to a customer address, so car 3's callbacks get mixed with car 1's and nobody can see which unit keeps failing.
- Monthly and quarterly visits differ by unit within the same contract. Simple repeat jobs book the whole building on one schedule, and units quietly drift past their visit frequency.
- Entrapments need a response time tracked from the moment of the call, with trapped versus not trapped treated differently. A normal job with a scheduled date has no clock and no way to show the building how fast you came.
- Inspection deficiencies have correction deadlines. In a spreadsheet they sit in the inspector's report until the next inspection finds them again.
How it's set up in Fieldproxy
Your process, set up as it runs.
We map how you run on a 30-minute call and configure it within 48 hours. These are the pieces it is built from.
Every unit as an asset with a QR code
Contract plans that book visits per unit
Your stages for callbacks and entrapments
Inspections, deficiencies and reports for the building
AI for elevator service companies
AI that does the admin, inside your workflow.
The AI agents work on your real jobs and customers, and you confirm anything that matters before it happens.
Takes the callback
Builds the route around the routine visits
Chases the paperwork
From $649 a month, one price per company, unlimited users.
Every AI agent included, AI credits charged separately. Live in days: the average migration takes about 10 days.
Questions
Elevator service software, answered.
What software do elevator service companies use?
Elevator service companies need field service software that treats each car or escalator as an asset, books contract maintenance visits per unit, tracks entrapments and callbacks with response times, and stores inspection results and certificates per unit. Fieldproxy is set up around your own contracts, checklists and stages, with a technician app on Android and iOS that works offline.
Can I keep a separate logbook for every elevator in a building?
Yes. Every unit is its own asset with a QR code, and every maintenance visit, callback, test and inspection is recorded against that unit. You can open one car's full history or see every unit in a building together.
Can it track entrapment response times?
Yes. Callbacks record the time reported, dispatched, on site and released, with a required field for whether passengers were trapped. Those times are reportable per building and per unit, so you can show a building owner how quickly you responded.
How much does Fieldproxy cost for an elevator company?
Fieldproxy is $649 per month per company with unlimited users, so every mechanic, dispatcher and office user is included. AI credits are charged separately, and every AI agent is included.
How hard is it to switch from our current system?
It starts with a 30-minute call about how your contracts, units and callbacks work. Fieldproxy is configured to your process within 48 hours, and moving your buildings, units and history over takes about 10 days on average.
See it set up for your elevator service business.
A 30-minute call on how you run. We configure it within 48 hours and show it to you running, with the AI agents working on it.