Voice agents that read CDK Drive — VIN to appointment in one call.
WFW connects to CDK Drive via the CDK API. Service calls resolve the customer's vehicle by VIN, pull service history, check recall status, and book the appointment — all in real time.
Service advisors stop fielding scheduling calls. Recall inquiries convert to appointments automatically. Service-ready notifications go out without staff dialing.
Live Data Flow — Recall Inquiry Call
CDK security data guidelines followed
All CDK Drive data handled per CDK's data use policies. Customer vehicle and service data never persisted in WFW.
Capabilities
What this integration enables.
Three concrete capabilities unlocked by connecting WFW to CDK Drive.
Live Data
Service Appointment Scheduling via VIN Lookup
The agent pulls the customer's vehicle record from CDK Drive using their VIN or customer ID. With year/make/model and service history in context, the agent offers appropriate service options and books the appointment directly in CDK Drive.
Live Data
Recall Inquiry Handling
When a customer calls about a recall notice, the agent queries CDK Drive for the customer's VIN and checks recall status in real time. If a recall applies, the agent schedules the recall service appointment — VIN to appointment in one call.
Live Data
Service-Ready Notification Calls
When a service order is marked ready in CDK Drive, WFW triggers an outbound call to the customer. The agent states the vehicle is ready, provides the total, and handles any questions about the service performed — without service desk staff dialing out.
Data Flow
How it works.
From VIN lookup to appointment confirmation — what moves between WFW and CDK Drive.
Customer and vehicle identified
Caller ID or spoken name is matched to a CDK Drive customer record. The customer's vehicle VIN, year, make, model, and service history are pulled into the agent's context before the first response.
Service need resolved against vehicle data
For service requests, the agent uses the vehicle's actual mileage and service history from CDK Drive to recommend the right service. No guessing — the agent knows when the last oil change was and what's due.
Appointment created or recall booked
Confirmed service appointments are created in CDK Drive's scheduling system. For recall inquiries, the agent confirms the recall applies to the customer's specific VIN before booking — preventing unnecessary appointments.
Extraction data available post-call
GET /v2/calls/{id}/extractions returns the VIN, service type, and extracted service need from the call — structured for service desk review or downstream CRM triggers.
Use Cases
Before and after.
Real dealership service workflows transformed by the CDK Drive + WFW integration.
Before
Service advisors fielding scheduling calls while managing write-ups, loaners, and customer check-ins. Hold times increase. Customers give up and book at the competitor.
After
WFW answers scheduling calls instantly. The agent pulls vehicle data from CDK Drive, presents available service times, and creates the appointment — service advisor queue untouched.
Before
Recall notice calls handled inconsistently — some customers get accurate information, some get transferred multiple times. Recall completion rates suffer.
After
Every recall call gets the same flow: VIN lookup → recall status confirmed → appointment scheduled in one conversation. Recall completion rate improves because every call books.
Before
Service desk calling customers when vehicles are ready — a manual task competing with active write-ups, cashiering, and customer walk-ins.
After
CDK Drive status update triggers WFW outbound call automatically. Customer is notified, questions answered, and loaner swap handled — without a service advisor picking up the phone.
Technical Details
Integration specifications.
Connection method, auth, data fields, and CDK compliance posture for your IT team.
| Connection method | CDK Drive API — REST over HTTPS, CDK security data guidelines followed |
| Auth method | CDK Drive API credentials stored encrypted in WFW vault |
| Data pulled from CDK Drive | Customer record, VIN, year/make/model, service history, open recall status, appointment availability |
| Data written to CDK Drive | New service appointments, appointment status updates, customer notes from call |
| Extraction fields | VIN, service type, customer intent — available via GET /v2/calls/{id}/extractions |
| Avg API round-trip | 150–250ms — within real-time voice conversation tolerances |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once CDK Drive is connected. Trigger service-ready notifications, pull VIN and service type extractions, and monitor service scheduling call volume.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger outbound service-ready notification call from CDK Drive status change
/v2/calls/{id}/extractionsRetrieve VIN, service type, and recall ID extracted from the call
/v2/agents/{id}Check agent health and CDK Drive connection status
Setup
Connect CDK Drive in three steps.
CDK credentials, service type mapping, agent activation. Done.
Add CDK Drive credentials
Enter your CDK Drive API credentials in WFW admin under Integrations → CDK Drive. Credentials are encrypted per CDK security data guidelines.
Map service types
Configure how WFW extraction fields (oil change, recall, tires, etc.) map to CDK Drive service type codes in your DMS. Takes about 5 minutes.
Enable on your agent
Toggle CDK Drive active on your service scheduling agent. VIN lookups, appointment booking, and service-ready notifications go live immediately.
Get Started
Connect CDK Drive to your voice agents.
Service scheduling, recall handling, and service-ready notifications — all reading from CDK Drive in real time. No middleware required.
Connect CDK DriveQuestions? Talk to our team →