Dealer groups, workshops, and OEM networks
AI worker teams for service booking and workshop capacity
Workshop capacity is perishable inventory. An empty bay cannot be sold tomorrow — so the operational job is filling it against real duration and skill constraints, not simply making more reminder calls.
Our view
Where we think the real opportunity is
Aftersales is where dealer profitability actually lives, and it is run with a scheduling tool and a telephone. The failure has two halves. First, outreach happens when someone has time rather than when service is due, so a data-rich trigger sitting in the DMS goes unused. Second, and less discussed, bookings are made without matching job type to duration and technician skill — so the diary looks full, the day overruns, and the following week absorbs the damage. Automation that only makes more reminder calls would worsen the second problem while improving the first. That is why this blueprint treats capacity compatibility as a hard constraint rather than a preference, and instruments booked duration against actual job time. Warranty, recall, and safety are handled the other way entirely: recognised and routed to a certified advisor, never handled.
Operating reality
How demand actually behaves here
Volume has a shape, and the shape is what breaks teams. This is what we assume about your operation before we design anything.
Service-due data exists but is not acted on in time
Mileage, interval, and recall data sit in the DMS, while outreach happens in batches when the advisor desk is quiet — which is rarely when the service is actually due.
Advisors are on the phone instead of in the lane
The person best placed to sell additional work is answering status calls, which costs both the conversation and the upsell.
Mis-scoped bookings break the schedule
A job booked without the right duration or technician skill overruns, and the overrun cascades into the following days.
Recalls and warranty carry legal weight
These conversations have manufacturer and regulatory consequences, which puts them firmly outside routine booking handling.
Where the hours go
The cost we would try to move first
Almost every operation spends its most expensive time on its least valuable work. Naming that precisely is what makes a pilot measurable rather than impressive.
Unsold bay hours
Idle workshop capacity is unrecoverable revenue, and it is the number this blueprint is ultimately judged against.
Advisor time on reminders and status
High-value staff performing outbound reminder calls and answering "is my car ready" is a persistent misallocation.
Rework from mis-scoped jobs
Overruns, rescheduled customers, and technician downtime all originate in a booking that did not match the work.
Incomplete recall campaigns
Unreached vehicles carry manufacturer obligations and, in some cases, safety exposure, and completion rates depend on persistent contact.
The trust envelope
What constrains the design, and what never gets automated
We design to the boundary first. A control added after launch is a control nobody believes — and in this sector the boundary is not negotiable.
Sector constraints
Certified-advisor routing on warranty, recall, and safety
These are recognised and handed over immediately, with vehicle and conversation context attached. They are not within worker scope at any trust level.
Capacity compatibility rules
Only slots matching the job's required duration and technician skill may be offered, because an unfillable booking is worse than none.
Cost approval before additional work
Any work or cost above the agreed estimate requires advisor authorisation, and the worker can flag but never approve.
Consent and frequency on outreach
Service reminders are marketing-adjacent contact and must respect recorded consent and frequency caps per channel.
Stays human, permanently
These are structural boundaries, not trust levels waiting to be relaxed.
Warranty and recall handling
Manufacturer and regulatory obligations make these certified-advisor conversations from the first turn.
Safety judgement
Any indication that a vehicle is unsafe to drive requires a qualified person, immediately.
Additional-work authorisation
Approving extra cost mid-service is a commercial conversation with the customer that an advisor owns.
Where to start
Sequencing matters more than scope
The first blueprint should be the one whose success criteria your team already agrees on. Each step below links to the blueprint that implements it.
Start
Inbound booking and status at one site
Handle inbound booking and "is my car ready" against live workshop capacity at a single site. Capacity compatibility is enforced from day one, because a full-but-broken diary is not a win.
Read the blueprintThen
Service-due outreach triggered by data
Replace batch reminder campaigns with consent-bound outreach triggered by actual service-due and recall data, on the channel each customer answers.
Read the blueprintNext
Multi-site, proactive status, and technical triage
Extend across sites with proactive in-service updates and advisor routing for authorisations, then reuse the pattern for technical support triage.
Read the blueprint
Systems we would expect to read and write
- Dealer management system
- Workshop scheduling and capacity planning
- Vehicle and service history
- Recall and campaign data
- CRM and messaging or telephony numbers
Blueprints that apply
3 operating blueprints for Automotive
Each one carries the full team, process, and control detail — the mechanics this page deliberately does not repeat.
Access & scheduling
Fill workshop capacity without an advisor on the phone all day
Service booking & workshop capacity
Read the blueprintMoney & regulated intake
Turn first notice of loss into a complete, correctly routed claim
First notice of loss
Read the blueprintService & resolution
Move from reported symptom to the right field visit, first time
Technical support & field dispatch
Read the blueprint
Push back on this
Objections we actually hear in Automotive
Answered as we would answer them in the room, including the cases where the right answer is that this is not for you.
- Our DMS is closed and the vendor will not help us integrate.
- This is the most common practical blocker in the sector, and it determines what is possible. Where a DMS exposes no usable interface, the blueprint can still run outreach and booking capture and hand structured bookings to your team for entry — real value, less of it. We would rather scope to that honestly than promise live capacity matching against a system we cannot read.
- Customers have a relationship with their service advisor.
- And this is designed to protect it. What moves is reminder calls, status questions, and booking logistics; what stays is the advisor conversation in the lane, plus every warranty, recall, and safety discussion. The advisor should end up with more time for the customers actually in front of them, not fewer conversations.
- Would this just fill the diary with the wrong jobs?
- That is the failure mode we designed against, and it is why capacity compatibility is a hard constraint rather than a preference. Booked duration is measured against actual job time from the start, so a mismatch shows up as a tunable signal in week one instead of as a broken schedule in month three. If your workshop scheduling data is not accurate enough to support that, fix it before automating outreach.
Other sectors
How the argument changes elsewhere
Next step
Argue with this in a working session.
Bring your own numbers. We will map your version of the operating reality, agree what must stay human, and scope the first blueprint against a measurable win — or tell you it is not worth doing yet.