AI for automotive and dealerships
Fixed ops pays the bills, and unanswered phones leak it away. Every call answered, every lead worked. 5x ROI in 30 days, or we work free.
- Dealership groups
- Service departments
- Parts counters
- Collision centres
Proof, honestly
No published dealership case study yet, and we say so. Founding clients get priority scheduling, direct founder involvement, and a co-published case study once the numbers are real. The 5x ROI guarantee applies from day one.
We guarantee 5x ROI inside 30 days of deployment, in writing, measured against a baseline you sign before we build. If the system misses the bar, we keep working for free until it clears.
The service line rings out.
Advisors are with customers and the BDC is underwater. The average US dealership wrote 16,252 repair orders in 2025 at $494 per customer RO (NADA Data 2025, US averages). The caller who rings out takes their next RO to the chain store down the road.
After-hours leads go stale.
The internet lead that arrived at 9pm gets a reply at 10am. The buyer moved on before breakfast.
You hear about bad visits in the survey.
CSI problems surface weeks later, after the damage is done and the OEM has counted it.
Declined work dies with the RO.
The June MPI measured the rear brakes at 4 millimetres and the customer said not today. Nobody called in October. The chain store beside their office got the job.
The special order arrived. Nobody called.
The part sits in the bin aging toward the obsolescence write-off while the RO stays open and the customer assumes it never came in.
Every caller starts from zero.
The store holds the VIN, four years of ROs and the last advisor's notes, and the caller still gets asked what car they drive.
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
Teams we build for
- Hoyes Michalos
- Nurse Next Door
- Fedi
- UBC Sauder
- Merchant House Capital
- Picton Mahoney
- Campbell Froh May & Rice LLP
- Barnakl
- Hungerford
- Breez
A service advisor's Thursday on the drive
The 7:10 rush is faces, not phones
humanThe drive is four deep. She does the walkarounds, writes up the waiters, gets the loaner keys sorted. The phone rings behind her the whole time and for the first time in her career that is not her problem.
The overflow books itself into real slots
Callers the advisors cannot take are answered, matched to their customer record, and booked into the slots the shop actually set in Xtime or myKaarma, drop-off or waiter, with the op code the concern maps to. The agent says what it is and that the call is recorded, up front, every time.
The grinding noise is already on file
A customer calls about a grinding noise. The history shows rear brakes measured at 4 millimetres on the June MPI and declined. The agent books the inspection and puts the June measurement on the RO notes. It reports what the shop wrote down. It diagnoses nothing.
She prices the timing chain job herself
humanA caller asked what a timing chain replacement runs. The agent took the question and parked a callback proposal with the vehicle's history attached. She builds the estimate from the menu and the labour guide, and the number goes out under her name. Nothing was quoted until she approved it. That gate is the build, not a courtesy.
Status calls never reach the bays
Is-my-car-ready answered from the RO status without a tech putting down a wrench or an advisor leaving a write-up. Promised times that slip trigger a call out before the customer calls in.
June's declined work comes back due
The declined items on closed ROs are watched against mileage and season. The rear-brake reminders queue for customers whose consent is on the ledger, and only those. The database refuses the rest.
The sour call gets a same-day callback
humanA pickup call flagged for CSI risk, a customer back twice for the same leak. She and the service manager hear the recording and call before five, weeks before any OEM survey would have told them. The save is human. The system only made it possible to attempt.
Tomorrow's no-shows shrink tonight
Confirmations go out for tomorrow's appointments. The 8am that cannot make it reschedules by text, and the slot reopens for the next overflow caller instead of dying on the schedule.
Built around your rules
| Regime | What it demands here | How the system complies |
|---|---|---|
| PIPEDA | Customer and vehicle personal information, the VIN-linked service history included, collected and used under Canadian privacy law. | Records stay in dealership-controlled systems, scoped at the database layer, under no-training API terms. Nothing personal leaves your own instance to make a model smarter. |
| CASL | Service reminders and marketing messages need consent, sender identification and a working unsubscribe. | Outreach runs on a tracked consent ledger enforced in the data layer. An agent cannot message an opted-out customer, because the database refuses. |
| BC Motor Dealer Act and the VSA | Licensed dealers carry advertising and disclosure duties under BC's motor dealer regime, administered by the Vehicle Sales Authority. | AI-drafted marketing passes human review against your obligations before it ships. The system drafts. A licensee approves. |
| Call recording disclosure | A commercial organization recording calls says so at the start of the call, under PIPEDA guidance. | Voice agents identify themselves as automated and disclose recording up front, on every call, inbound and outbound. No exceptions are configurable. |
| OMVIC and AMVIC | Dealer conduct and advertising rules under the Ontario and Alberta regulators, all-in price advertising included. | Built to respect them where the group operates. Drafts carry the required disclosures and a registrant approves before anything publishes. |
| Motor Vehicle Safety Act recall campaigns | Recall outreach must state a vehicle's actual recall status. A wrong recall claim is a safety, trust and liability problem. | Recall status is read per VIN from the manufacturer campaign and the Transport Canada lookup, never inferred by a model, and the outreach names the campaign it cites. |
The regimes that govern automotive, what each demands, and how the system complies
Regime
- PIPEDA
What it demands here
Customer and vehicle personal information, the VIN-linked service history included, collected and used under Canadian privacy law.
How the system complies
Records stay in dealership-controlled systems, scoped at the database layer, under no-training API terms. Nothing personal leaves your own instance to make a model smarter.
- CASL
What it demands here
Service reminders and marketing messages need consent, sender identification and a working unsubscribe.
How the system complies
Outreach runs on a tracked consent ledger enforced in the data layer. An agent cannot message an opted-out customer, because the database refuses.
- BC Motor Dealer Act and the VSA
What it demands here
Licensed dealers carry advertising and disclosure duties under BC's motor dealer regime, administered by the Vehicle Sales Authority.
How the system complies
AI-drafted marketing passes human review against your obligations before it ships. The system drafts. A licensee approves.
- Call recording disclosure
What it demands here
A commercial organization recording calls says so at the start of the call, under PIPEDA guidance.
How the system complies
Voice agents identify themselves as automated and disclose recording up front, on every call, inbound and outbound. No exceptions are configurable.
- OMVIC and AMVIC
What it demands here
Dealer conduct and advertising rules under the Ontario and Alberta regulators, all-in price advertising included.
How the system complies
Built to respect them where the group operates. Drafts carry the required disclosures and a registrant approves before anything publishes.
- Motor Vehicle Safety Act recall campaigns
What it demands here
Recall outreach must state a vehicle's actual recall status. A wrong recall claim is a safety, trust and liability problem.
How the system complies
Recall status is read per VIN from the manufacturer campaign and the Transport Canada lookup, never inferred by a model, and the outreach names the campaign it cites.
Customer and vehicle data stays inside dealership-controlled systems, recordings are disclosed, and outreach runs on tracked CASL consent.
How we build it for automotive and dealerships
Answer the phone that currently goes to voicemail.
Missed calls are measurable before the build starts, which makes the baseline honest. This is the fastest payback in the shop.
Grade on your own recorded calls.
Booking accuracy and misroute rate are measured end to end, transcription included, before any customer reaches the system.
Add retention work once booking is reliable.
Service follow-up and CSI risk flagging reuse the same records. They come after the shop trusts the phone.
What we will not automate
Quoting work and anything that commits the shop. Consent state is enforced in the data layer so an agent cannot contact someone who asked not to be.
The hard questions
Free · 3-5 days
Know your number in five days.
We map your operations, find the highest-ROI automations, and hand you a ranked plan with the payback math attached. Yours to keep, whoever builds it.
Prefer to talk first? Book 15 minutes with our team. No pitch deck.