Custom AI Workflow Agent for Body Shops

The Car Is Not the Bottleneck. The Paperwork Is.

Walk a collision shop's lot on any Tuesday and count the cars that are not being worked on. Most of them are not waiting on a technician. They are waiting on an approval, a part, or a signature — a supplement sitting in an adjuster's queue, an OEM panel with no confirmed ship date, a calibration that has to be sublet and scheduled. The labor is not the constraint; the file is. Which means a collision repair workflow that only tracks physical work is measuring the wrong thing, and the automation that matters is not in the bay. It is in the twenty small administrative loops that decide how long a car sits between the moments when somebody actually touches it.

Supplement Approval Is Where Cycle Time Goes to Die

Teardown reveals what the photos could not: a bent rail, a cracked mount, a radiator support that has to come out. The shop writes a supplement, sends it to the adjuster, and then — waits. That wait is unbounded. It can be a day. It can be nine days, if the supplement lands with an adjuster carrying two hundred files and nobody follows up. During every one of those days the car occupies a bay, the customer burns rental days, and the shop's cycle time degrades without a single hour of productive labor being consumed. A workflow agent's most valuable job is to make supplement approval a tracked object rather than an email somebody sent. It knows when the supplement went out, whose desk it is on, how long it has been there, what the shop's average approval time is with that carrier, and when it has gone past that average — and it chases it, on a schedule, with the documentation attached, so a human does not have to remember which of eleven open files is overdue.

Documentation Is What Gets a Line Item Paid

Insurers do not pay for work; they pay for documented work. A calibration performed without the pre-scan, post-scan and manufacturer procedure attached to the file is a $600 line item waiting to be denied. Blend time on an adjacent panel that is not photographed and justified gets negotiated away. A supplement written as three lines of prose gets a phone call and a delay; the same supplement written with photographs, the OEM repair procedure, and the part numbers gets approved. This is where a shop quietly loses thousands of dollars a month, and it loses them not to a hard-nosed adjuster but to its own incomplete paperwork. An agent that enforces the documentation checklist before a supplement leaves the building — pre-scan attached, photos labeled, procedure cited, part numbers matched — is worth more than any efficiency it adds anywhere else in the collision repair workflow.

Parts Sourcing and the Back-Order Nobody Noticed

A part is ordered on the 3rd with an expected date of the 11th. On the 11th it does not arrive, and the shop finds out because a technician goes looking for it. That gap — between the moment a part quietly slipped and the moment somebody noticed — is pure lost cycle time, and it happens constantly because nobody is watching a dozen orders across four suppliers. A workflow agent watches. It reconciles expected arrival dates against reality every morning, flags the ones that have slipped, and escalates before the delay compounds. When an OEM part is going to be four weeks out, that is a decision the shop needs to make on day one — source aftermarket, find a recycled part, or call the customer and reset the date — and not on day twenty-two when the promise has already been broken.

Every Repair Now Has a Compliance Trail

ADAS calibration is not a service the shop chooses to offer. On a car with a forward camera behind the windshield or radar behind the bumper, it is a safety obligation with liability attached, and the record of having done it correctly matters as much as the calibration itself. That means a scan before the work, a scan after it, the specific manufacturer procedure followed and cited, and a certificate on the file. If that car is ever in another accident and the question is whether its automatic emergency braking was calibrated to spec, the shop's file is the answer. Building that trail by hand across every vehicle is tedious enough that it gets skipped, which is exactly why it should be a workflow the agent owns rather than a habit a busy technician is trusted to maintain.

The Numbers a Shop Should Be Watching and Usually Is Not

Cycle time by stage. Touch time versus calendar time — the ratio of hours actually worked to days the car was in the building, which in most shops is uncomfortable to look at. Supplement approval turnaround by carrier, because knowing that one insurer averages two days and another averages eight changes how you schedule against them. Estimate-to-booking conversion. Comeback rate by technician. Average repair order value against the $4,500 national mean. None of these require a new system so much as they require somebody to actually assemble them from the estimating platform, the management system and the parts orders, weekly, without fail. That assembly is a job nobody in the shop has time for and an agent can do overnight.

The Handoffs Between Systems Are Where Files Die

A collision shop runs an estimating platform, a management system, an accounting package, a parts ordering portal, and a calibration provider's scheduler, and in most shops the connective tissue between them is a person retyping things. A vehicle that exists in the estimating system does not exist in the parts portal until somebody puts it there. A calibration that was completed does not appear on the invoice until somebody adds it — and when they forget, the shop has performed $900 of work for free. The workflow agent's least glamorous and most reliably profitable function is to close those gaps: reconcile what was authorized against what was billed, catch the calibration that was done and never invoiced, and flag the supplement that was approved but never added to the final. The customer support agent draws on this same file when it tells a customer where their car is, which only works if the file is true.

Working Downstream of an Adjuster

There is a structural fact about this trade that shapes every workflow in it: the shop does not control its own revenue approval. An insurance agency's operations are about writing and servicing policies — their systems answer to their own underwriting, and the decisions get made inside the building. A collision shop lives on the other end of that relationship, waiting on somebody else's queue for permission to continue work it has already started. AI agents for insurance agencies shows the same claim from the side that holds the authority, and it is a useful thing for a shop owner to understand about the desk their supplements land on.

Common Questions

Does this replace the shop's estimating or management system?

No. It sits between them. The estimating platform writes the estimate and the management system tracks the repair order; the agent handles the loops neither of them close — chasing an approval that has gone quiet, catching a part whose date slipped, and reconciling work performed against work billed.

Can it actually chase an adjuster for a supplement approval?

It can follow up on a schedule with the documentation attached, escalate when a file passes that carrier's normal turnaround, and keep a record of every touch. It does not negotiate the line items — a human estimator does that. It makes sure the human is negotiating rather than remembering.