Will a confirmation step cost us real test drives?

It costs a small share of low-intent browsers and saves far more in reclaimed calendar capacity. The shoppers who confirm are the ones who show up. Measure show rate before and after, not raw booking count.

How do we tell a bot wave from a real demand spike?

Real demand spikes correlate with something: an ad campaign, a price drop, a weekend. Bot waves correlate with nothing except the clock, and they bring disposable emails and zero confirmations. Check the confirmation rate first; it separates the two in one number.

Should we block the IPs placing fake bookings?

As one layer, yes, but never the only layer. Bot operators rotate IPs cheaply. Blocking buys you a quiet week; behavioral confirmation buys you lasting protection.

Home / Blog

Fake test-drive bookings: how bots drain dealer calendars and starve real buyers

October 4, 2026 - LotWall

Short answer: Test-drive booking bots are usually run by lead aggregators scraping inventory availability, by competitors probing your process, or by affiliate marketers padding lead volumes. They book in bursts, use disposable emails, never confirm, and never show up. The damage is not just wasted time: a full calendar turns away real buyers, and fake bookings pollute your CRM so badly that follow-up metrics become meaningless. The defense is layered: rate-limit booking endpoints, require confirmation on new contacts, score booking behavior, and separate the calendar from the CRM so junk bookings never touch your sales pipeline.

Who books fake test drives and why

The first category is data harvesters. A bot that books a test drive learns your availability patterns, your sales process, which VINs move and which sit. That intelligence gets packaged and sold, or used by a competing lot across town. The second category is lead-volume padders: affiliates or vendors paid per lead who generate bookings that look real in a spreadsheet and evaporate on contact.

The third is plain mischief and competitive sabotage, rarer but real: flooding a rival's Saturday schedule so genuine shoppers see no availability and drive elsewhere. The motive matters less than the mechanics, because all three produce the same signature in your booking data.

The pattern that gives them away

Fake bookings cluster. Look for bursts of appointments from the same IP ranges or device fingerprints, email addresses from disposable domains, phone numbers that never pick up, and bookings made seconds apart at 3 AM. Real shoppers browse first: they view VIN pages, check pricing, maybe run a payment estimate. Bots skip straight to the booking form because browsing costs them compute.

The no-show rate is the bluntest signal. A healthy test-drive calendar no-shows at a predictable rate; a botted one spikes. Track no-shows by booking source and time of booking, and the bot campaigns reveal themselves as statistical outliers. One dealer we have seen discussed publicly found that bookings made between midnight and 5 AM no-showed at four times the daytime rate.

Protecting the calendar without hurting real buyers

The goal is friction for bots, not for buyers. Rate-limit the booking endpoint per IP and per device, and put a confirmation step (email or SMS) on first-time bookers before the slot is held. Real buyers confirm; bots usually do not, because confirmation breaks their economics at scale.

Add behavioral scoring on the booking flow: time on page, interaction with the form, whether the shopper viewed inventory first. None of these should block a booking alone, but together they route suspicious bookings to a verification step instead of straight onto the calendar. Keep a few prime Saturday slots out of the automated pool entirely, held for phone-confirmed appointments, so a bot wave can never zero out your best day.

Cleaning the CRM after a bot wave

If bots have been booking for weeks, your CRM is full of junk leads poisoning your follow-up metrics and your sales team's morale. Quarantine first: tag bookings matching the bot pattern (disposable email, no confirmation, no-show) and exclude them from reporting before you delete anything. Reps should never have been scored against leads that were never human.

Then fix the pipe. The long-term answer is to stop syncing raw bookings into the CRM and sync confirmed appointments instead, with the booking system and the CRM separated by a confirmation gate. Marketing can still see booking volume for capacity planning; sales only sees humans who confirmed. That one architectural change does more than any blacklist.

Training the team to trust the system

The best booking defenses fail if the sales team works around them. Reps who see a blocked booking as a lost commission will take phone bookings that bypass every check, reintroducing the junk through the side door. Align incentives: score reps on confirmed appointments and show rates, not raw booking counts.

Give the team a simple override path for edge cases (the real buyer whose email looks odd) with a verification step attached. Overrides should be rare, logged, and reviewed. A defense the team trusts is a defense that survives contact with a busy Saturday.