# How to Turn VDP Visitors Into Test-Drive Requests

> A shopper reading a VDP at 9pm won't fill out a generic form. Here's how to capture the test-drive request in the moment and route it to your CRM.

_Source: https://nobi.ai/blog/book-test-drive-dealership-website_

## How do you get more test-drive requests from dealership website VDP visitors?

It's 9pm and someone's on your site reading a VDP, weighing this trim against that price, close to deciding. That's the exact moment a dealership wants to capture, and it's also the moment most sites waste. The shopper has no way to say "let me drive this one" without leaving the page to hunt down a generic contact form buried somewhere in the nav - and most don't bother. Put a conversational assistant right on the VDP and it can offer a test drive for the exact car the shopper is already looking at, right when they're ready to say yes. The request - vehicle, contact info, timing - goes straight to your [CRM or lead form](https://nobi.ai/blog/dealership-lead-capture) through Nobi's Custom Actions, and your team still runs the calendar and confirms the appointment. Here's how that handoff actually works.

## Why do interested VDP visitors never turn into test-drive requests?

A shopper who reads a VDP closely, checking trim, mileage, price, is showing real intent, but most dealership sites give them nothing to do with it except click a generic "schedule a test drive" link buried in the nav. The form that opens doesn't know which vehicle they were looking at, so they have to re-type the year, make, and model they were just staring at. It also asks for a phone number and a preferred time before the shopper has decided they trust you enough to hand those over. By the time they'd finish it, the moment has passed and they're back on the SRP, or gone.

That 9pm VDP read is a real up. No phone rang, no form got submitted, but someone with money to spend was on your site looking at a specific car. When they bounce without acting, there's no record of the visit and no way to follow up. They become an orphaned lead: a shopper who was interested enough to click in, invisible enough to never show up in your CRM.

This gap compounds at scale. A rooftop with strong VDP traffic and a flat appointment set rate isn't losing deals in the showroom. It's losing them here, before the form ever loads.

## What is Nobi, and how does it turn a VDP visit into a test-drive request?

That orphaned lead doesn't have to stay invisible. Nobi is a [conversational assistant that sits on your dealership website and answers shopper questions](https://nobi.ai/blog/ai-assistant-dealership-website) from your own inventory and site content, with the vehicle a shopper is currently viewing as context. On a VDP, that means Nobi can recognize interest as it happens and offer to set up a test drive for that exact car, not a generic visit, right inside the conversation.

Because Nobi reads the VDP the shopper is already on, it knows the year, make, model, and trim before it asks a single question. There's no re-typing what they were just staring at. That single detail removes the friction that kills most of these conversations before they start.

Nobi doesn't lead with the ask, either. It answers the questions that come first: is this the only one on the lot, what's included at this trim, has the price moved. Those are the questions a serious shopper actually has at 9pm, and answering them well is what earns the trust to offer the test drive at all. A form that jumps straight to "pick a time" skips that step, and shoppers bounce.

When Nobi does send the request to your team, the vehicle goes with it. Your BDC sees "someone wants to drive this Silverado" instead of a bare name and number with no context, which is what a generic contact form hands off today. That's a warmer up to call back, and it's faster to work because nobody has to ask the shopper what they were even looking at.

## How does the assistant know when to offer a test drive?

Capturing the up is only half the job; timing the ask is what keeps it from backfiring. Nobi offers a test drive when a shopper's questions signal real interest in the vehicle on the page, asking about availability, trim differences, or financing, rather than opening every VDP visit with the same prompt. When it does offer, it names the vehicle directly: "Want to set up a time to drive this Silverado?" instead of a generic "schedule a test drive" banner. That specificity is what makes the offer read as the next logical step in a conversation, not a pop-up sales pitch.

The offer is scoped to the page, not the site. It shows up as a contextual suggestion pill or a direct reply tied to the VDP a shopper is already on, never as a site-wide interruption that fires the same way on a homepage visit or an SRP scroll. A shopper skimming ten listings on the SRP isn't shown the same prompt as one who's asked three specific questions about a single car.

Timing matters for CSI, not just conversion. An assistant that pushes the test-drive ask before answering what the shopper actually typed reads as pushy, and a pushy AI interaction is worse than no AI interaction at all. Nobi answers the question first. The test-drive offer comes after, as a next step earned by the conversation, not a script the shopper has to get past to reach an answer.

## How do I connect test-drive requests to my CRM?

That confirmed request still has to land somewhere your BDC actually works leads. Nobi's Custom Actions is a JavaScript API that fires the moment a shopper confirms a test-drive request, triggering whatever workflow your dealership already runs: a CRM lead, a scheduler call, a lead form submission. The vehicle and shopper details from that conversation ride along with it. You wire it once to whatever system your BDC already works leads in. Nobi doesn't need to replace your CRM or DMS to do this.

When Custom Actions fires, it sends structured data, not just a name and a phone number. The vehicle rides along: year, make, model, trim, and VIN if your inventory feed has it. So does whatever contact info the shopper gave up in the conversation. That's the difference between a lead your BDC has to chase down ("who is this and what were they even looking at?") and one that arrives already qualified: someone wants to drive this specific Silverado, here's how to reach them.

Custom Actions plugs into whatever your rooftop already runs leads through. If your CRM has an API, it posts there. If your process routes through a lead form endpoint or a scheduling tool's webhook, it posts there instead. Nothing about your BDC's workflow has to change to make this work. The request shows up the same way a phone-up or an internet lead would, just with the vehicle attached from the start.

This is a one-time setup, not something anyone touches per conversation. A developer wires the connection once, pointing it at your CRM or scheduler, and every confirmed test-drive request after that flows through automatically. Your BDC never sees the plumbing. They just see a qualified, vehicle-specific request sitting in the system they already check every morning.

## Should Nobi ask for anything before sending the request to sales?

A light qualification step, just before the request goes out, keeps your BDC from chasing requests with no real intent behind them. Nobi asks for timing (today, this week, no rush) and how to reach the shopper before confirming, which is enough for a rep to prioritize a hot transfer without turning the moment into a multi-field form.

Two questions is the ceiling, not a starting point. Ask for a third and the shopper abandons before confirming, which defeats the purpose of asking at all. Timing is the one that matters most: it lets your BDC sort a same-day request from a someday-maybe one, and that distinction is what speed to lead is built on. A rep working a "today" request and a rep working a "no rush" request are doing two different jobs, and knowing which one they're on before they dial changes how fast they move.

This isn't a credit app, and it isn't meant to replace one. It's not trying to qualify the shopper the way F&I eventually will. It's just enough context for a rep to decide the first call is worth making right now instead of sitting in a queue.

## What doesn't Nobi do once the test-drive request is sent?

Nobi captures the request and hands it to your CRM or scheduling tool with the vehicle and shopper details attached. It does not see your appointment calendar, does not confirm a time slot, and does not talk to your DMS. Your team still owns the schedule and the actual confirmation call or text.

That boundary matters because a calendar is exactly the kind of thing you don't want an AI guessing at. No calendar access means no risk of Nobi double-booking a slot or promising a 4pm test drive when your last tech leaves at 3. The confirmation, the part where a real person calls or texts to lock in the time, stays with your BDC. That's the moment where trust actually gets built, and it's not something worth automating away even if it could be.

The same boundary applies to price and lot status. Nobi can tell a shopper what's on your VDP and answer from your connected inventory feed, but it can't confirm with certainty that a car is still physically on the lot beyond what that feed says, and it doesn't quote numbers your DMS hasn't published. If your feed runs a day stale, that's a dealership-side fix, not something the assistant can correct for on its own.

## Frequently asked questions

### What does Nobi cost?

The base plan is $25 a month, which covers 2,500 searches and 250 conversational messages. Additional usage runs $0.01 per search and $0.10 per message. There's no revenue share and no seat fee, so a rooftop can look at this line item and know exactly what drives it up.

### Can Nobi quote a wrong price or a sold vehicle?

Nobi answers from your connected inventory feed, which refreshes twice a day. Grounding in that feed leaves less room for error than a model working from memory, though no AI system can guarantee it's never wrong. In practice, the most common cause of a wrong answer is the feed itself lagging a sale or price change between refreshes.

### Does this replace our BDC?

Nobi captures the request and routes it with the vehicle attached. Your BDC still makes the call, owns the calendar, and closes the deal.

### Will this hurt our CSI score?

A grounded assistant that answers real questions and hands off cleanly carries a different risk than a scripted bot that loops. The qualification step here is deliberately short, just two questions, to avoid the back-and-forth that generates complaints.

See how Nobi turns VDP visitors into vehicle-specific test-drive requests your CRM already knows how to work.