The ticket said the unit wasn't cooling. The truck came back with a diagnosis and no repair, because the fix turned out to be a compressor for a 2009 R-22 system and nobody knew that until the tech read the data plate on site. Two trips are now required, and only one of them has happened.
What a roll costs at this radius
Out here, the drive is not a rounding error. Lubbock to Levelland is about thirty miles each way; Brownfield, Post, and Plainview are farther still. A run to Levelland and back is an hour of windshield time before anyone touches a tool, and that hour costs a loaded tech wage, fuel, wear on the truck, and — in season — the billable call you could not take because the truck was out on US-114. Do the arithmetic with your own numbers, because nobody else's apply: trips last month that ended in "we'll have to come back," times round-trip minutes, times what an hour of that truck is worth to you in July. Your dispatch log already holds every input.
The data plate answers most of it before anyone drives
Nearly every machine you service carries a plate that says exactly what it is. The condenser nameplate gives model and serial, and those give tonnage, refrigerant type, and age — which is how you learn it is an R-22 system from your desk instead of from a ladder. The sticker inside an appliance door gives the precise model, which decides the part. A water heater's rating plate settles gas versus electric and capacity from the customer's garage. A garage-door call is a different job depending on whether the photo shows a torsion spring or an extension spring, and the customer can photograph either one in ten seconds.
The intake system's whole job is to get that photo into the ticket before dispatch. Mechanically it is modest: after the call or web form, a text goes to the customer with two or three requests — a photo of the plate, a photo of the problem area — and the replies attach to the job record where the dispatcher and the tech both see them. No app to install, nothing to explain twice. With a model number in hand, someone can phone the supply house on the loop and confirm the part is on the shelf before the truck moves. Now the truck leaves carrying the fix, or it does not leave at all until the part arrives — which is a calendar adjustment, not a sixty-mile lesson.
The service-area screen comes first
The first thing intake establishes is not what broke. It is where the customer is. An address or ZIP collected up front, checked against the radius you actually serve, ends the out-of-area conversation before it books itself onto your board. The courteous version quotes a trip charge for the far edge of the map instead of letting dispatch discover, Tuesday morning, that the job is past Tahoka. There is no intelligence in this step — it is a lookup and a branch. It simply has to run before the calendar gets touched, and in most shops it runs after, or never.
Symptoms, structured, from the customer's own words
After location and photos, intake collects the handful of answers that change the dispatch decision: is the unit running at all, is the breaker tripped, what sound is it making, when did it start, what does the thermostat read. The point is not diagnosis — the point is that "not cooling" splits into a dozen different first moves, and four questions separate most of them. The flow also needs a branch that recognizes urgency: a no-cool call in a Lubbock August with an elderly occupant in the house should be offered an immediate call path, not a fifth form field. An intake that cannot tell triage from paperwork will eventually embarrass you.
The second trip is the one that stings
The first visit was always going to happen; someone has to put hands on the equipment eventually. The roll that hurts is the return: diagnose Tuesday, order Wednesday, drive the same thirty miles Friday to install a part whose number was printed on a plate the customer walks past every day. First-visit completion — jobs closed in one trip, divided by all jobs — is the figure this entire page is about. It is also a figure you can compute tonight from last month's tickets, before deciding whether any of this is worth building.
What intake cannot do
Some units hide their plates — attic air handlers, package units on flat roofs — and some customers send a blurry photo of the wrong sticker. The flow needs a graceful "couldn't get it" path that books the call anyway, because losing the lead costs more than the extra trip. Some jobs genuinely require gauges on the system before any part can be named; a photo narrows the range, it does not diagnose. And every added question costs completions. An intake longer than the dispatch decision requires will bleed away the very leads it was built to qualify — cap it at what changes who drives where, carrying what. Finally, none of this helps a true emergency; someone with a burst line needs a phone call now, and the system's job is to get out of the way and connect one.
Where to start
Pull last month's tickets and count two things: jobs that needed a second trip for parts, and calls that turned out to be outside your radius. Multiply the wasted drive time by what a truck hour costs you. That number is the size of this problem in your shop, in your own figures, and it is the only number worth acting on.