Collision vertical
AI for collision claims, seen from the shop's seat.
Search this phrase and you land on injury lawyers, a consumer app that helps a driver argue with a carrier, and a Reddit thread about somebody leaning on a chatbot. Every result is written for the person who was hit. Nobody writes it for the shop holding the car. So this page takes the shop's seat: a claim that moves through seven stages, stalls in four predictable places, and ends as a receivable on your books.
The stage ledger
Seven stages, and the four that eat the week.
A collision claim is not one event. It is a run of handoffs between the customer, the insurer, the appraiser, your estimator, a parts supplier, a sublet vendor, and sometimes a rental desk. The shop sees all of them and controls only some of them. Below is each stage, the way it stalls, and the line between what software can prepare and what a person has to own.
| Stage | Where it stalls for the shop | What the AI layer can do | Who owns it |
|---|---|---|---|
| 1. First notice of loss and who is paying | The customer does not know their deductible, their coverage, or whether they are allowed to pick the shop. The file sits while nobody asks. | Hold the carrier, claim number, deductible, and payer on the job so the shop is not reconstructing it at the counter three weeks later. | The customer and the insurer. The shop records what it is told. |
| 2. DRP or non-DRP | The shop's role changes completely between a DRP file and a customer-pay or non-DRP file, and staff working from memory mix the two sets of rules. | Mark which path the job is on and which obligations travel with it, so the correct checklist runs instead of the one someone remembers. | Your DRP manager and the program agreement. |
| 3. The estimate and the appraisal | Photos are taken and the estimate is written, then it sits in the insurer's review with no visible clock on it. | Track how long the file has been in review and what is holding it, so an aging approval surfaces before the customer calls to ask. | Your estimator writes the estimate. The appraiser reviews it. |
| 4. The supplement cycle | Teardown finds damage nobody could see, a supplement goes in, and the approval takes days the shop cannot bill and cannot schedule around. | Raise the supplement the moment teardown finds the damage, keep the photos and the documentation attached, and flag a supplement that is close to a timing limit. | The estimator writes, justifies, and discusses every supplement line. |
| 5. The total-loss threshold | The repair crosses the threshold and a job you already invested teardown time in becomes a settlement conversation with a customer who is now angry at the wrong party. | Show the repair position against the vehicle value early, so the shop is not learning about it after the car is apart. | The customer and the insurer. A person at the shop delivers the news. |
| 6. Rental and loss of use | Rental days run out before the repair does, and the customer escalates to the shop about a problem the shop did not create and cannot approve. | Watch the rental authorization against the projected completion date and raise the mismatch while there is still time to act on it. | Any extension or loss-of-use discussion is a human conversation with the carrier. |
| 7. Getting paid | The shop's own receivable ages while the claim is open, and no single person owns chasing it. | Match the invoice to the claim, flag the missing document that is holding payment, and prepare the follow-up for review. | Your office or GM makes the call. Disputes stay with people. |
Two clocks
The insurer's clock and your clock do not agree.
The insurer measures the claim in days from report to settlement. You measure it in days the car occupies a bay, days a rental is burning, and days between finishing the repair and getting paid for it. Those two clocks only occasionally point the same direction, and the shop feels the difference in cycle time and in cash.
This is the narrow, honest job for an AI layer in claims handling. It cannot move an appraiser. It cannot approve anything. What it can do is make the time visible: a file that has not moved, a document that was never sent, a supplement whose clock is running, a rental that will expire before the car is done. Those are all things a person can fix in an hour if they know, and things that cost a week when nobody notices.
A useful test for any claim tool: ask it to list every open file where the shop is waiting on someone else, sorted by how long it has been waiting. If it cannot answer, it is a status screen, not a claims tool.
The line
What AI must never do inside a claim.
AI does not negotiate with an insurer. It does not decide fault. It does not sign a direction to pay, a repair authorization, or a release. It does not answer a coverage question, because coverage is a matter between the carrier and the policyholder, and the shop is not a party to it. It does not give legal advice, and it does not put a number in front of an appraiser and argue for it.
Every one of those is a person's job, and it stays a person's job. The human owns the estimate, the supplement, and the appraiser relationship. The system watches the clock, keeps the file complete, drafts the customer update so the customer is not left guessing, and puts the item in front of somebody who can act on it.
How estimating work is prepared and reviewed -> How the supplement cycle is tracked ->
See it on your open files
Bring a week of claims. We will show you the waiting.
We will walk your open collision jobs and point out every one that is parked on somebody else's desk.