Every BDC software demo goes well. The vendor picks the lead, the script, the time of day and the customer’s mood. That is not dishonesty; it is a demo. The problem is that a dealership then signs a twelve-month agreement on the strength of a conversation that never had to survive a Saturday afternoon.
There is a better test, and it costs nothing but an hour of the BDC manager’s time. Take five situations that happen in your store every week, hand them to the vendor, and watch the software work them live. What follows is the acceptance test I would run before any BDC platform touches a real customer.
1. The After-hours Lead
A lead arrives at 9:40pm from a third-party listing site, asking whether a used truck is still available and what the payment would be with $3,000 down.
Ask the vendor to handle it in front of you, in real time, with the store closed. The evidence to capture is simple: how long before the customer gets a response, what the response says, and where the conversation is recorded the next morning.
The failure condition is a response that answers the payment question. No BDC tool should quote a payment from a listing enquiry, because it does not know the customer’s credit, the trade, or what the desk would actually approve. A good response confirms availability, asks one qualifying question and offers a time. If the software invents a number to keep the customer talking, stop the pilot.
2. The Missed Call
A customer rings the main line during the lunch rush. Nobody picks up. They do not leave a voicemail.
Capture what happens in the next fifteen minutes. Does the customer receive a text? Is the missed call logged against a record the BDC can see, with the number, the time and the line it came in on? If the customer calls back, does the second call attach to the first?
The failure condition is a missed call that leaves no trace except a line in the phone system’s report. In practice this is the most common way a dealership loses a service customer: the call is missed, nothing follows, and the customer books elsewhere. Software that cannot recover a missed call is not a BDC tool; it is a dialer.
3. The Service Booking with a Wrinkle
A customer wants a service appointment on Thursday but also mentions a noise from the front end and asks whether a loaner is available.
Watch whether the software books the appointment, notes the concern, and either answers the loaner question correctly for your store or hands it to a person. Capture the appointment as it lands in your scheduler, not as it appears on the vendor’s screen.
The failure condition is a booking that reaches your scheduler without the noise complaint, or with a loaner promise the store cannot keep. Both create a bad visit before the customer arrives. The test is whether the software knows the limits of what it can commit to.
4. The Duplicate Customer
Pick a customer who exists in your CRM twice, once as “Bob Martinez” with a mobile number and once as “Robert Martinez” with a work email. Have a new lead arrive from Robert.
Ask the vendor to show you what the software does with the match. Does it create a third record? Does it merge silently? Does it flag the possible duplicate and let a person decide?
The failure condition is a third record. Every duplicate is a customer who will receive two follow-up sequences, two service reminders and eventually two apologies. It is also the reason BDC reports overstate leads and understate close rates. Software that creates duplicates will make your numbers worse while telling you they are better.
5. The Human Handoff
Take a real conversation that an AI or automated sequence has started, and have the customer say something the script did not anticipate: “My wife handles this, call her instead,” or “I’m not interested in that model, but do you have anything in blue?”
Capture the moment of handoff. How does the BDC representative know a person is now needed? What do they see when they open the conversation: the full transcript, or a summary, or nothing? How long does the customer wait between the software’s last message and the person’s first?
The failure condition is a handoff the customer can feel. If they have to repeat what they said or wait long enough to wonder whether anyone is there, the automation has cost the store the goodwill it was supposed to earn.
What to do with the Results
Score each scenario as pass, pass with a fix, or fail, and write down the evidence beside it. Two fails on any of the five is enough to pause a pilot until the vendor can show the scenario passing on your data, not theirs.
None of this requires technical knowledge. It requires a BDC manager who knows what happens in the store on a normal week and is willing to make the software prove it can handle it. That hour is the cheapest protection a dealership has against a twelve-month agreement with a demo.
Related Stories: