Claude for Dealers / Learn / AI for the Service Department
Fixed Ops · Service and Parts
AI for the Dealership Service Department: 7 Fixed Ops Jobs Claude Can Take Today
Most dealer AI talk stops at sales and marketing. The service drive writes more words per day than any other department, and most of them get written in a hurry.
Tech notes, RO 48211: LF/RF pads 3mm, rotors lipped, cust states squeal cold AM. Cabin filter loaded. 61k mi. Write the customer text.
Hi Dana, your technician finished the inspection on your Pilot. Two things:
- Front brakes: pads are at 3mm. New pads are 10 to 12mm. This is the squeal you hear on cold mornings. We recommend replacing pads and resurfacing or replacing rotors today.
- Cabin air filter: clogged. Not urgent, but it affects A/C airflow.
I can send photos and the quote. Want me to call you?
Advisor review required before send
Service departments use Claude to turn technician notes into clear customer recommendations, write declined-service follow-up, summarize a vehicle's repair order history before the customer arrives, answer warranty and policy questions from your own documents, and build advisor scorecards from a DMS export. A human advisor reviews everything before a customer sees it. Claude does not diagnose vehicles and does not quote prices.
- Best first project: the multi-point inspection write-up
- Works from exports and pasted notes. No DMS integration required to start
- Every customer-facing message gets advisor review
- Claude never diagnoses, never quotes, never promises a completion time
- Plan needed: Claude Pro or higher per user
- Time to first working Skill: about one afternoon
Why fixed ops is the most overlooked AI opportunity in the store
An advisor with 18 open repair orders is a writer on deadline. Status texts, inspection explanations, declined-work notes, warranty stories, follow-up emails. The quality of that writing decides whether a customer approves the brake job or says "I'll think about it." It gets written between phone calls.
That is a language problem at volume under time pressure, which is the same reason the BDC pays back fast. The difference is that almost nobody is working on service yet.
The 7 jobs
| Job | What goes in | What comes out | Who reviews |
|---|---|---|---|
| 1. Inspection write-ups | Tech notes, measurements, mileage | Customer text or email in plain English, ranked by urgency | Advisor |
| 2. Declined-service follow-up | Declined lines, date, vehicle | 30, 60, and 90 day messages tied to the actual item | Advisor or BDC |
| 3. RO history summary | Exported RO history for the VIN | One paragraph: what was done, what was declined, what is due | Advisor |
| 4. Warranty story drafts | Tech notes: concern, cause, correction | Clean three C narrative in your format | Warranty admin |
| 5. Policy and warranty Q&A | Your policy docs and maintenance schedules as knowledge files | Answers with the source section quoted | Manager spot checks |
| 6. Advisor scorecards | DMS export: ROs, hours, lines, CSI | Weekly one-page scorecard per advisor | Service manager |
| 7. Recall and seasonal campaigns | Target list criteria, offer, dates | Email, text, and a phone script in one voice | Manager and compliance |
Start with job 1
The inspection write-up is the best first project because it happens dozens of times a day, the input already exists, and the before and after is obvious to everyone in the drive. Technicians write "LF pads 3mm." Customers need "your front pads have about a quarter of their life left, and here is what that means."
- 01Tech notesShorthand, measurements, photos noted
- 02Service SkillYour voice, your urgency rules, your hard limits
- 03Advisor reviewEdit, add the quote, confirm facts
- 04CustomerText or email they can act on
What goes in the service Skill
A Skill is a saved set of instructions Claude follows every time. If the term is new, read Projects, Skills, and Agents Explained first. A service write-up Skill needs five things:
- Your urgency ladder. Safety now, soon, monitor. Define each one with examples so Claude ranks items the way your shop foreman would.
- Plain-English translations. Give it reference points: new pad thickness, tread depth at replacement, what a loaded cabin filter does.
- Your voice. Short sentences. First names. No scare language. Paste three messages your best advisor wrote.
- Hard limits. No prices unless the advisor supplies them. No completion times. No diagnosis beyond what the technician wrote.
- The output format. Text length for SMS, a longer email version, and a one-line note for the RO.
Run your own declined-work numbers
We will not quote you an industry statistic. Pull your own. Export last month's ROs and count the lines marked declined. Then answer three questions.
If follow-up on declined work is close to zero today, a Skill that drafts every follow-up message from the declined line itself is found money. The advisor's job becomes review and send.
Guardrails for the service drive
- Translate tech notes into customer language
- Draft follow-up and status messages
- Summarize history you export
- Format warranty narratives from tech notes
- Build scorecards from your data
- Diagnose a vehicle
- Quote a price or a payment
- Promise a completion time or loaner
- Send anything without advisor review
- Receive card numbers, SSNs, or credit data
Put the right-hand column into the Skill as hard rules, word for word. The full framework is in AI Guardrails for Dealerships.
Build order for a service manager
Week one: inspection write-up Skill with two advisors. Week two: declined-service follow-up. Week three: RO history summary before appointments. Week four: weekly advisor scorecard from a DMS export, using the method in Build a Dealership Dashboard with Claude. Do not start with all seven.
Common questions
Can Claude diagnose a car?
No, and it should not try. Claude works from what your technician wrote. Its job is to explain the technician's findings clearly, not to add findings of its own. Write that limit into the Skill.
Does Claude integrate with CDK, Reynolds, Tekion, or my DMS?
You do not need an integration to start. Pasted notes and exported reports (CSV or PDF) cover all seven jobs on this page. If you want live connections later, read Claude Connectors and MCP for Dealerships and ask your DMS vendor what they support.
Is it safe to put customer information into Claude?
Keep it minimal. First name, vehicle, and the repair facts are enough for a write-up. Never enter Social Security numbers, credit information, or payment card data. For store-wide use, a Team or Enterprise plan gives you admin controls. See Which Claude Plan Does a Dealership Need.
Will advisors actually use it?
They use what saves them time in the first week. That is why the inspection write-up comes first. It removes typing they already hate. Start with your two most open-minded advisors and let the results recruit the rest.
How long does it take to set up?
A working inspection write-up Skill takes one afternoon if you have three good example messages and your urgency rules written down. Tuning it takes another two weeks of real use.
Build Your Fixed Ops Skills Live
Two hands-on build days with operators who run stores. We are back in Atlanta January 5, 6, and 7, 2027.
Register Now →