The test drive is where vehicles are actually sold — and in most dealerships it runs on a whiteboard: keys handed over on trust, the demo car double-booked at 11, the outcome living in the consultant's head. Test drive management software replaces the whiteboard with an engine. xMatix treats the test drive as what it is: a scheduled appointment on a bookable asset, with compliance before the keys and a result on the opportunity after.
Booked like the appointment it is
Test drives are a first-class appointment type on the scheduling engine: slots backed by real capacity, the demo vehicle attached as a required bookable resource, and holds that keep a slot honest while the customer confirms. Double-booking the one diesel variant stops being a Saturday tradition — the engine checks the vehicle's existing bookings before it promises.
KYC before the keys, odometer out and in
The test-drive record carries the compliance trail: the customer's KYC document captured before the drive, the demo asset identified, and usage readings out and in — so the odometer story of every demo vehicle is complete, drive by drive. Cancellations carry reasons; no-shows are data, not mysteries.
The result lands on the opportunity
Every drive ends with a recorded outcome — status, rating, the customer's own words — attached to the opportunity it came from. The consultant's follow-up references what the customer actually said in the car; the sales manager sees drive-to-booking conversion by model, consultant and source. The test drive feeds finance and the configured quote on the same record.
The demo fleet, planned like a fleet
Demo vehicles are capacity: how many drives per vehicle per day, which branches hold which variants, when a demo unit rotates out. Because drives are appointments on bookable assets, demo-fleet utilisation is a report — the variant that never gets driven and the one that is booked solid both become visible, and the fleet plan follows evidence. (The longer argument: the demo fleet as a bookable resource.)
Common questions
How does test drive booking prevent double-booking of demo vehicles?
A test drive books the demo vehicle as a required resource on the scheduling engine, which checks the vehicle's existing bookings and slot capacity before confirming. A held slot expires if the customer never confirms, releasing the vehicle automatically.
What compliance details are captured before a test drive?
The record carries the customer's KYC document number, the identified demo asset, and usage readings at start and end of the drive — so licence verification, vehicle custody and odometer history are all on the record rather than on trust.
How do test drive results connect to the sales pipeline?
Each drive closes with a status, a rating and the customer's feedback, attached to the opportunity. Managers see drive-to-booking conversion by model and consultant, and follow-ups reference the actual outcome of the drive.
What should test drive management software record on every drive?
The booking against a real vehicle slot, the customer's KYC before the keys, odometer readings out and in, and the outcome — status, rating, feedback — landed on the opportunity, so the drive is a measurable pipeline event rather than a whiteboard entry.
Can test drives be arranged from the customer's location?
Yes — the appointment model supports home test drives and pickup/drop patterns, with the assigned consultant and vehicle tracked like any other scheduled visit.