Short answer: the part is often the bottleneck, not the technician. AI can watch the RO, the manufacturer note, and the last promise to the customer, then draft the update. It should never tell anyone the car is ready, the part is in, or the loaner is theirs.
The fixed-ops piece covers lists and drafts in the lane. This is the hold: the vehicle is in the way, the customer is calling, and the only new information is in a vendor email nobody has opened.
Where the day actually goes
An advisor has twenty open ROs. Four of them are waiting on a part. One of those four had a delivery date yesterday. The manufacturer changed it in a portal message. The customer was told "Thursday." It is Thursday. The advisor finds out when the customer is already in the driveway.
That is not a chatbot problem. That is a "the status lives in three places" problem: the DMS, the parts counter, and an inbox. Unsupervised tools fail here in a specific way. They invent a ready time from a stale RO, or they send a cheerful text that the parts department would not sign.
What AI may do
- Pull the open ROs that have been on parts-hold longer than your rule.
- Put the last manufacturer or warehouse message next to the last thing the customer was told.
- Draft the advisor's callback: what changed, what you can honestly say, what you should not say yet.
- Remind the advisor before the promised day, not after the customer is in the lane.
What it must never do
- Promise a ready time. ETA from a warehouse is not a promise from your store.
- Tell the customer the part is in because a status code looked like "received." Received at the warehouse, received at the store, and installed are three facts.
- Release a loaner or a wait-line commitment. Those have names attached on purpose.
- Speak for the manufacturer. If the OEM note is ambiguous, a person reads it.
The questions to ask before you connect anything
Customer data in a DMS is already a Safeguards problem. Add these:
- Can it send a customer text without an advisor? (You want no.)
- Which status does it treat as "part in" — and can you see the source line?
- Does it read manufacturer and vendor mail, or only the RO screen?
- Who owns the draft history if you turn the tool off?
Software names like CDK, Reynolds, and Xtime are how stores already work. They are not a claim of a working connector. Access is confirmed during scoping.
A realistic first step
Take five current parts-holds. Have the tool reconstruct each one for the advisor. Count how many times the draft would have promised a day you could not keep. That number is the whole evaluation.
If you want a setup that tracks the hold and leaves the call to your advisors — talk with us. If a better parts meeting and a shared list are enough, we will say so.
Related: AI for dealership fixed operations · our approach for dealerships.