The industry field guide
AI voice agents for auto dealerships
Sales inquiries and service bookings, grounded in live inventory and workshop capacity.
The right vehicle. The right department.
A dealership phone line serves several businesses at once: vehicle sales, workshop service and parts. Start by identifying the department and a precise vehicle reference. Keep inventory, advertised pricing and service availability connected to maintained systems.
An editorial deployment framework. Example workflows require approval by your business; this is not legal, clinical or regulatory advice.
The call map
Design the next step, before the greeting.
- 01Incoming inquiry
- 02Sales / service / parts
- 03Inventory or workshop lookup
- 04Appointment request / specialist handoff
- Typical call
- Vehicle availability
- Typical call
- Test-drive request
- Typical call
- Service appointment
Within a defined scope
Safe to automate.
- Read approved inventory details using a stock number.
- Request a test drive within the sales calendar.
- Book eligible service categories against workshop capacity.
Give a person ownership
Escalate to a human.
- Finance terms, trade-in valuations and negotiations.
- Recall interpretation or vehicle safety concerns.
- Warranty disputes and unusual repair requests.
The systems it needs.
- Dealer inventory feed
- Dealer management / service scheduler
- Sales CRM and department directory
These are integration requirements for your workflow, not a claim that every platform offers a native connector. Test the exact action and permissions.
Risks to design around.
- Inventory can change between inquiry and arrival.
- A service appointment does not guarantee repair completion time.
- Avoid quoting lending decisions or unapproved discount terms.
Choose for these capabilities.
- Stock-number confirmation
- Department transfer
- Service-category constraints
- Inventory freshness visibility
A starting point to evaluate
Retell AI
Teams that want visual call flows and developer access in the same operating workflow.
Confirm: stock-number confirmation and department transfer.
Inspect the platformA starting point to evaluate
Vapi
Developers who want explicit choices across models, voices, transcription and business tools.
Confirm: stock-number confirmation and department transfer.
Inspect the platformThis is an editorial shortlist by operating model. We have not tested these platforms in a auto dealerships deployment or verified the required business-system connectors.
Compare the two starting pointsTest the awkward calls.
A polished greeting is not an acceptance test. Add these cases to the pilot:
- Two vehicles have nearly identical descriptions.
- The vehicle is sold during the conversation.
- The caller switches from sales to service.
- The requested repair requires a specialist bay.
Budget for the actual workflow.
- Compare sales and service call duration separately.
- Promotions may create concurrency spikes without a lasting increase in average volume.
An editable example, not an industry benchmark or forecast.
Estimate this workflowNeed someone to build it?
Prepare a call map, the systems to connect, expected volume and an acceptance checklist before speaking to an implementation partner. Ask who owns maintenance, support and the phone number after launch.
We do not collect or route implementation leads yet. You can review the official Vapi partner directory ↗ or contact a platform through its profile. How commercial relationships work.
Evidence, in the open
Go to the source.
Product capabilities are documented vendor statements. We have not independently benchmarked call quality or latency. How we evaluate evidence.
Where AI should stop.
Keep exceptions, disputed identity and requests outside the approved call flow with your team. Name a staffed destination, an unanswered-transfer path and an owner for failed system actions.
Test this industry workflow