HVAC · appliance repair · locksmith · fire and sprinkler · refrigeration
If it runs on trucks and checklists, it runs on this
There is no HVAC edition. The difference between an HVAC shop, a plumber, a locksmith and a courier is vocabulary, a few custom fields and a different set of checklists — and all three of those are data. Every one of them dispatches somebody to a place to do a defined thing and needs proof it happened.
From an HVAC company with rooftop PMs on agreements down to a one-van appliance repair shop, ServiceProof is the most modern way to scale a field service business. Dispatch, the field app, estimating, billing and the books are one platform that answers to an AI assistant you can talk to from the truck, and on the roof Wingman reads the checklist into the tech’s ear.
Custom fields, because every shop is different
“Backflow device serial” on a site is a plumbing field an HVAC shop never sees. “Refrigerant type” is the reverse. A locksmith wants a keyway and a fire shop wants a riser number.
Add the field to the record it belongs to, and it shows up in three places at once: in the checklist, in the token that fills your paperwork, and in your reporting.
- In real typed columns, so you can sort it, filter it by range and total it. A field you cannot reach from a spreadsheet is a field we are hiding from you.
- Attached to a real record — a site, a customer, a piece of equipment, a job. It extends the platform; it never replaces it, which is what keeps your data legible to everything else.
- And no platform behavior depends on one. Nothing we ship branches on the value of a field you invented, so your extension stays yours rather than quietly becoming our schema.
A changeout procedure, authored once. The fuel-type choice branches the run — which is how one procedure covers four installations.
Seasonal peaks are where consistency pays
The week the first freeze lands — or the first hundred-degree day — your least experienced people are doing your most work. That is the week the callbacks are made, and the week nobody has time to supervise anyone.
The checklist is how a second-year tech runs the job the way your best one does. Not a training course they will do in November. The steps, on the screen, on the job, in order.
- The readings get taken because the step asks for them.
- The photograph gets taken before the panel goes back on, not after.
- The part number gets recorded while the part is in his hand.
- And when he finds something he cannot fix today, the rule routes it to whoever prices work — with the evidence already attached.
What has to happen, and everything anybody knows about this building.
Run the rooftop PM with both hands on the unit
On a hot roof, nobody should be thumbing through a phone. Wingman reads the checklist into any Bluetooth earpiece and listens to the answer, so the tech keeps both hands on the unit and the phone stays in a pocket.
The PM comes off the service agreement with a window to move it in, and each unit on the roof asks for the readings its type calls for, such as suction, discharge and amps. The tech says “compressor’s shot on RTU 3, suction’s at 58, head pressure 310, unit’s iced up again, I’ve got the model and serial” — and a dozen steps fill at once, each one checked exactly as a typed answer would be.
A photo you can’t take with a gauge in each hand is remembered as owed rather than skipped, and the job won’t close until it has been taken. What the tech finds up there becomes a quote the same day, because a rule hands it to the estimator’s queue with the evidence already attached.
Say “hey wingman,” answer the step it reads to you, and say “over.” The phone stays in the pocket.
And Wingman knows the code. Ask it a plumbing code question and our engine answers from the code itself, with the state and county amendments applied, the math worked out and the section cited, on a phone with no signal. Plumbing comes first, and because experts teach it with a spreadsheet rather than a programmer, the same method extends to HVAC and the rest of the trades, one at a time.
Appliance repair · one owner, one van
Run a one-van shop from the driver’s seat
In a one-van appliance repair business you’re the dispatcher, the tech and the bookkeeper, so let the assistant take two of those jobs off your hands. Connect Claude, ChatGPT or Copilot to ServiceProof once, and between calls you run the business by talking to it from the van.
Say it from the van
- “What’s my next stop?”
- “Send the Johnson invoice.”
- “How much is outstanding?”
The whole platform, priced for one van
Booking, the field app, estimating, invoicing, getting paid and the books are one platform, and it is priced per tech, so a one-van shop pays for one: $75 per tech per month, or $0.25 a job workflow.
It acts as you, never as a robot account. It sees and does exactly what you could, with your permissions, and it checks with you before anything that can’t be undone. And when a second van comes along, the same platform grows with you and scales the crew you already have, with SOPs, field workflows and, ultimately, agents.
Make it your system, or start beside yours
Run the whole company here, from the board and the field app to estimating, invoicing, getting paid and the books. Or keep ServiceTitan, FieldEdge, HouseCall Pro or whatever the office already knows, start with the field proof and the office SOPs on one crew next week, and move the rest across whenever you’re ready.
Every trade on this page fits the same platform, because what changes from one to the next is the record a job has to leave behind.
Appliance repair
Model and serial off the plate, the part on the van or not, and a second visit that does not start from scratch.
Locksmith
Keyways, cores, master systems and who was authorized to ask. The record of what was changed is the whole liability story.
Fire and sprinkler
Inspections on a cadence somebody else enforces, with a due date you cannot miss and a report you have to hand over.
Refrigeration
Recurring service, logged readings, refrigerant tracked on the record rather than in a notebook in a van.