The recall campaign playbook — from OEM notice to completed repairs, by rooftop
Building the outreach list, TCPA-compliant outbound with consent and call-time windows, scheduling into real service capacity, SMS confirmations and rescheduling, and the completion-rate reporting the OEM will ask for.
On this page
A recall is an outbound campaign with a deadline
When the OEM announces a recall, the dealer group inherits an outbound program overnight: a population of affected VINs, a remedy that consumes service capacity, a regulatory clock, and an OEM watching completion rates by store. Treat it like any other one-off and you get the standard result — a burst of calls in week one, a trickle of bookings, and a long tail of unreached owners that drags the completion number for months.
Treat it like a campaign and the shape changes. This playbook covers the run order: build the list, dial it compliantly, schedule into capacity that actually exists, confirm and reschedule by text, and report completion by rooftop so the OEM conversation is a report instead of an apology.
Build the outreach list before you dial anything
The list is where recall campaigns are won or lost, because the population you can't reach can't book.
- Start from the OEM's affected-VIN file and match it against your customer records — service history, sales records, and prior campaign contacts
- Deduplicate across rooftops first. In a dealer group, the same owner often appears at two or three stores; without dedup, they get three calls and you look disorganized at exactly the moment you're asking for trust
- Segment the list: customers with recent service history (warm, likely reachable), known customers with stale contact data, and OEM-file-only owners you've never seen
- Scrub for contact preferences and prior do-not-call requests before the list ever reaches a dialer
- Record where each contact record came from — it matters for consent, below
Dial it like a regulated campaign, because it is one
Recall outreach is outbound calling and texting to consumers, which puts it squarely in TCPA territory. A safety recall does not suspend the rules; it just raises the cost of getting them wrong on a campaign this visible.
- Use TCPA-compliant outbound dialing with consent tracking built into the platform, not into a spreadsheet someone maintains
- Enforce call-time windows by the customer's local time zone automatically — the platform should make an out-of-window call impossible, not just discouraged
- Honor do-not-call and channel preferences at the dialing layer, and capture revocations the moment they happen on any channel
- Use brand-specific scripts and disclosures per store, so every agent opens with the right dealership identity and the required recall language
- Keep an audit trail per contact attempt: when you called, what was disclosed, what the customer said. If the campaign is ever questioned, this is your answer
Your counsel sets the consent posture for each segment; the platform's job is to enforce whatever that posture is on every attempt, automatically.
Schedule into real service capacity, not into hope
The fastest way to burn a recall campaign is to book appointments the stores can't honor.
- Book against live bay availability through the DMS — CDK, Reynolds, DealerTrack, or Tekion — so every appointment an agent confirms is a slot the service department actually has
- Gate bookings on parts: recall remedies are parts-constrained more often than bay-constrained. Confirm the remedy part is on hand (or schedule for its arrival) before confirming the customer
- Reserve recall capacity per rooftop deliberately, so the campaign doesn't cannibalize the paying service schedule — or sit unused because every slot was already taken
- Capture loaner needs at booking for remedies that take the vehicle out of service
Pace the outreach to the capacity. Dialing the whole list in week one when the stores can absorb two hundred remedies a week just manufactures hold time and no-shows.
Confirm by SMS, and make rescheduling effortless
Recall appointments have a built-in no-show problem: the customer isn't paying, the car usually still drives, and the appointment may be weeks out.
- Send an SMS confirmation at booking with the date, time, rooftop, and what the recall visit involves
- Send a reminder the day before with a two-way reschedule path: the customer replies, the system offers new slots from live availability, and the appointment moves without a callback
- Treat a reschedule as a save, not a failure — the alternative was an empty bay and an open VIN
- Follow up after the repair to confirm completion and close the record
Track completion rate by rooftop and DMA
Completion rate — repaired VINs over affected VINs — is the number the OEM cares about, and the only way to manage it is to break it down.
- Track the funnel per rooftop and per DMA: reached, booked, showed, repaired. Real-time dashboards tied to the raw event stream mean you see the funnel as it moves, not at month end
- Use per-dealership reporting and scorecards to find the outliers — the store whose reach rate is fine but whose show rate is half the group's has a confirmation or capacity problem, not a list problem
- Watch the unreached segment explicitly. As the campaign ages, this is where the remaining completion points live; rotate channels and retry strategies against it rather than re-dialing the same numbers on the same schedule
- A/B test script and routing variants where the numbers lag — versioned campaigns with rollback make this cheap to try and safe to undo
Report to the OEM like it's a product
OEM recall reporting is recurring, structured, and judged. Build it once and let it run:
- Reconcile completed repairs against the original affected-VIN file so the completion number you report matches the number the OEM computes
- Report by the cuts the OEM uses — rooftop, DMA, campaign wave — on the cadence they expect
- Keep the contact-attempt audit trail attached: a store with a modest completion rate but documented, compliant, repeated outreach is in a very different position than one with the same number and no record
- Version the campaign itself, so when the OEM revises the remedy or expands the VIN population mid-campaign, you ship the change and keep rollback in your pocket
The short version
Run a recall as a managed outbound campaign: build a deduplicated, segmented, consent-scrubbed list from the OEM VIN file and your own records; dial it with TCPA-compliant outbound, enforced call-time windows, and a full audit trail; book into real DMS bay availability gated on parts, pacing outreach to what the stores can absorb; confirm and reschedule over two-way SMS so reachable owners become repaired vehicles instead of no-shows; and track the reached-booked-showed-repaired funnel by rooftop and DMA in real time. Do that, and the OEM report writes itself — completion rates with the evidence behind them.
Back to
Industries
Return to the main industries page to see the full product family.
Related guides
Guide
The year-end giving campaign playbook — planning the December surge without burning out your team
Compliant appeal outreach, SMS-first touchpoints, volunteer staffing with one-day onboarding, secure donation processing at volume, and the post-campaign follow-up that turns December givers into January donors.
Guide
The TAS migration checklist — moving off a legacy answering service platform without losing a client
Importing client scripts, rebuilding dispatch rules, preserving on-call contact trees, migrating reporting formats, parallel testing high-risk clients, and sequencing go-live so nothing breaks at 2 a.m.
Guide
The subscriber retention playbook — saves, win-backs, and the calls that keep circulation alive
Renewal reminders, price-increase notices, cancellation save offers, payment-failure outreach, and win-back campaigns — plus the two numbers that tell you whether any of it is working.