The recall list is a duty and an opportunity
Open recalls sit on customer vehicles because mailers get ignored and life moves on. The recall block works the manufacturer list campaign by campaign: three lines per advisor so the list clears in a morning, parts-on-hand verified before the call, and a loaner or shuttle answer ready because “how will I get home” is the real objection half the time. The call is honest scheduling support on top of the manufacturer’s notification process, which keeps the formal notice obligations where they belong.
The AI summary does the quiet service-drive work: the campaign booked, the transportation arranged, and the symptom mentioned in passing (“there’s a rattle over bumps”) captured as a diagnosis line for the repair order. A recall visit that also diagnoses the rattle is the customer relationship improving in one visit.
Declined work: the follow-up that respects the customer
Every service visit produces declined recommendations, and most of them decline for scheduling or money, not because the customer disagreed about the brake pads. The declined-work block calls the deferrals with the specifics on the row: the pads at 3mm from March, the seep that was not yet a drip. The call leads with the safety context in one sentence and the practical question (“do you want us to bundle it with the recall visit Saturday?”).
The summary records the outcome both ways. A rescheduled service is revenue recovered; a real refusal, logged, is the record that protects the store if the customer later disputes what they were told. The scare pitch has no place in either: the recording proves which kind of call your store makes.
Confirmations protect the schedule
A service no-show burns a lift slot nobody can rebook same-day. The confirmation block calls tomorrow’s appointments with the practical checks: still good for 8 AM, parts on hand, transportation needs, how long the wait is. The summary flags the shaky ones (“might need to push to next week; kid’s schedule”), and the reschedule disposition moves the slot while it can still be resold.
The recording settles the disputes that service drives generate: what time was promised, whether the loaner was confirmed, what the advisor said about cost before the authorization call. In a department that lives on trust and repeat visits, those receipts are cheap insurance.
Lapsed customers come back through the service lane
The customer whose last visit was fourteen months ago is a service opportunity before they are a sales opportunity: the vehicle is aging out of warranties, the maintenance menu has catch-up items, and the trade conversation starts in the service lane more often than the showroom. The lapsed block works within the FTC rule’s established business relationship (540 days from the last visit), with the service history as the opener: “your inspection is due, and your wiper motor was flagged in January”.
That call is also the trade-in sensor: the customer who says “honestly we’re thinking of replacing it next year” goes to the summary as a sales-lead referral, dispositioned separately so the BDC sees it. The service department becomes the store’s cheapest lead source, and the summaries are how the referral travels.
What the reporting shows by Friday
Recall completion rate, declined-work recovery, confirmation and no-show rates, lapsed-customer rebooking, and the symptom mentions that became repair-order lines. Those numbers describe the service drive’s health and its contribution to the store’s pipeline, captured during the calls instead of reconstructed at the service-manager meeting.
Waiters, droppers and the same-day schedule
Service scheduling fails on a hidden split: the customers who can wait and the ones whose car is their Tuesday. The confirmation block asks the question that sorts them (“do you need a ride, a loaner, or are you waiting here?”), and the AI summary files transportation needs as a field the counter can see before the customer arrives. A waiting customer with no ride arranged is the hour-long lobby experience that becomes a bad review; the same customer with the shuttle booked at confirmation is a routine visit.
The same block catches the half-day misestimates: the brake job booked as an oil change, the diagnostics that need the car all day. Caught on the confirmation call, the slot moves and the customer’s day survives. Caught at drop-off, it becomes the front-counter argument the recording would have prevented.
The maintenance menu as a calling script
The manufacturer’s mileage menu (30k, 60k, 90k) is a calling script nobody uses: every lapsed and declined-work customer has a due item, and the call that names it specifically (“your 60,000-mile service includes the spark plugs your engine is due for”) converts better than any “time for service” reminder. The AI summary ties each call to the menu item, the appointment and the customer’s own words about timing and budget.
Declined items get their own aging: the transmission service declined in February is re-offered in October with the seasonal context, and the refusal, if it comes again, is logged as a standing decline so the customer is not re-asked monthly. The reporting then shows menu penetration across the book: which services sell by phone, which only sell at the counter, and which the store should stop calling about.
What you need to start
- Your own Telnyx account with numbers and caller ID.
- Recall, declined-work, confirmation and lapsed lists as CSVs from your DMS.
- A recording disclosure and one headset per advisor.
- A disposition set the advisors and the counter agree on.
The 14-day trial runs in a sandbox with test numbers. Load a sample recall campaign, run a three-line block, and read the summaries before your real book is dialed.