Vapi recall booking for automotive dealership groups

A dealer may have hundreds of unresolved recall records but insufficient parts for every vehicle. Outreach that fills the calendar with unrepairable appointments frustrates customers and wastes service-bay capacity.

1. Obtain approved Reynolds & Reynolds DMS integration access and import only required VIN, recall and owner-contact fields into n8n.
2. Validate the current manufacturer campaign and available remedy; avoid paraphrasing safety risks beyond the approved notice.
3. Check parts and technician availability before Vapi offers a slot, and apply outbound consent and contact rules.
4. Use a supported Claude model to capture scheduling intent and owner corrections; do not run the retired Claude 3.5 Sonnet direct-API ID.
5. Reserve the service appointment through the approved DMS integration and keep a parts-waitlist branch for non-bookable campaigns.

DMS unresolved VIN → campaign verification → parts/capacity gate
  ready → Vapi approved recall notice → appointment → DMS
  remedy unavailable → waitlist → parts-ready outreach

This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.

// n8n Code node: recall eligibility is not repair readiness
const recall = $json;
return [{ json: {
  vinRef: recall.vin_ref,
  action: !recall.owner_contact_authorized ? "suppress" :
    recall.campaign_open && recall.remedy_available &&
    recall.parts_reserved && recall.qualified_slot_available
      ? "offer_service_slot" : "parts_waitlist",
  approvedNoticeId: recall.manufacturer_notice_id
} }];

Track completed recall repairs, no-shows and appointments canceled for missing parts. An illustrative ten additional completed eligible repair orders creates value only at the campaign’s actual reimbursement and labor terms, not a generic revenue claim.

Manual BDC outreach can handle owner objections well. Voice automation is useful for approved notices and scheduling, but a simple parts-ready CRM campaign may be enough for low-volume recalls.

Have Imperio assess your DMS access and build a parts-aware recall scheduling pilot.

Can it explain whether a vehicle is safe to drive?

Use the manufacturer’s current approved guidance and escalate questions beyond it.

Can it book when parts are backordered?

Use a waitlist unless the service team explicitly supports a non-repair appointment.

What if the owner sold the car?

Record the correction and suppress further owner outreach; do not assume the new owner’s contact permission.

• Anthropic model lifecycle and retirement dates