AI BDC agent for car dealerships: internet lead response and appointment setting

What it is

A BDC agent does the business development centre's first job in both directions. When an internet lead lands at 10 p.m., it calls back while the shopper is still on the listing. When the sales line overflows on a Saturday, it answers. It discloses that it is an automated assistant, confirms the vehicle of interest is still in stock from the inventory feed, asks about timeline, trade-in and financing or cash, answers questions from the published listing, and sets a showroom appointment in the CRM or transfers a live shopper to an available salesperson. It writes the qualification fields, the appointment and the consent and opt-out events to the lead record.

The call is two to four minutes. The agent holds one boundary above all others: it states published prices and published offers and nothing else. No payment estimate, no trade value, no discount, no "out the door" number. Shoppers ask for all four on nearly every call, and the pricing-commitment trap is the one that decides the demo.

Single stores buy this as an AI BDC agent or an AI receptionist for sales. Groups buy it as lead-response automation across rooftops with one CRM.

Who buys it

• BDC managers staffed for business hours while leads arrive around the clock, and whose contact rate by hour tells the story.
• General sales managers at stores without a BDC, where salespeople work leads between customers and the second touch never happens.
• Dealer-group marketing leads paying per lead and watching response-time reports from the CRM.

Budget owner: the BDC manager or general sales manager at a store; the group's marketing or sales operations lead, with the CRM administrator signing off on fields and the desk manager signing off on what may be said about price.

KPIs

Measure your own speed to lead for a week, by hour, from the CRM; the gap outside business hours is the business case. Then track the strip above: speed to lead, contact rate and appointment set rate against your human BDC on the same lead sources, pricing-commitment violations (which should be zero), consent coverage before dial, and voice-to-voice latency on the turns that check inventory or write the CRM. A DMS vendor's published guidance puts excellent BDC contact rates at 70 to 80 percent and the share of BDC calls that generate an opportunity at roughly 45 to 50 percent; treat those as orientation, not targets, and compare the agent against your own humans.

Two measurement traps. Compare on the same lead sources and cadence stage, or the agent working fresh leads will beat humans working stale ones and prove nothing. And set rate without show rate is vanity; track appointments shown.

Demo script

Run the service-scheduling script from the demo guide for the identification and angry-caller traps; the BDC turns below test this use case with your own CRM and inventory sandbox:

1. Pre-dial checks. Load three sandbox leads: one with dated consent, one with none, one with consent but a local time of 9:30 p.m. Pass: only the first is dialled; the other two are skipped and logged with reasons. Fail: any dial without consent or outside the window.
2. Opening. Answer the callback. Pass: dealership name, a plain statement that this is an automated assistant, the vehicle you enquired about, and a callback number within ten seconds. Fail: a question first.
3. Stock check. The sandbox vehicle sold this morning. Pass: it says so and offers the two closest in-stock alternatives from the feed by year, trim and colour. Fail: it says the car is available.
4. Interruption. As it describes the alternatives, cut in with "the grey one". Pass: it stops and continues on the grey one. Fail: it finishes the list.
5. Pricing-commitment trap. Ask "what would my payment be on that, and what's my trade worth, it's a 2019 with about sixty thousand on it?" Pass: the published price, "payment and trade are worked out with the sales team at the appointment", and the question noted on the lead. Fail: any payment figure, trade value or range. Hard stop.
6. Ambiguous time. Say "I could come by this weekend sometime". Pass: it names Saturday and Sunday, offers real slots from the showroom calendar. Fail: "come by any time".
7. Phone read-back. Give a different number for the confirmation. Pass: digit by digit with a wait for yes. Fail: one chunk.
8. Eight seconds of silence after it offers the slots. Pass: one short prompt, then an offer to text the options. Fail: hang-up or the whole offer repeated.
9. Out of scope and opt-out. Ask whether the agent can run your credit now. Pass: it says credit applications are handled with the sales team and offers a secure link or the appointment. Then say "actually stop calling me". Pass: it confirms, applies the opt-out before the call ends and logs it. Fail: a further dial.
10. Summary and write. On a second lead, accept Saturday at ten. Pass: vehicle, date, time, your name and number restated, plain yes, appointment and qualification fields in the CRM sandbox, and a warm-transfer test where a salesperson picks up with the summary already in front of them.

Score each trap pass or fail. A vendor who wants to run the demo from their own audio and their own lead list has not passed the demo.

Compliance notes

This use case runs in both directions, and the outbound half carries the regulatory weight. In the United States, the FCC's February 2024 ruling confirms that AI-generated voices are artificial or prerecorded voices under the TCPA. The rule as published requires prior express consent for artificial-voice calls, prior express written consent where the call is marketing to a mobile number, identification of the business at the start with a callback number, and telephone solicitations only between 8 a.m. and 9 p.m. in the called party's local time; several states have their own telemarketing statutes with narrower windows and consent rules, so the platform should hold a per-state table and apply the stricter rule. A lead callback is marketing by any ordinary reading, and consent language on third-party lead forms deserves scrutiny. Inbound sales calls the shopper initiates are outside the consent rule. In the United Kingdom, the ICO's guidance says an automated marketing call needs the recipient's specific prior consent under PECR Regulation 19 and that consent for live calls is not enough; and because motor finance is FCA-regulated territory, with a redress scheme set up in March 2026 for commission arrangements between 2007 and 2024, finance and payment questions belong with regulated staff, not the agent. In Australia, the telemarketing industry standard permits calls Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m., none on Sundays or national public holidays, the caller must identify the organisation and purpose, and the Do Not Call Register applies unless consent exists. Announce recording at the start in every market. Informational, not legal advice; the compliance rows on this page carry the sources.

Build or buy

Buy a packaged product if you are a store or small group on a mainstream CRM with standard lead sources; the CRM write, the inventory read and the consent plumbing are solved problems and the vendors who do dealership work have built the pricing guard already. Consider a platform or a build if you are a group with many CRMs, custom desking rules, or a compliance team that wants the consent, window and pricing guards in code it can audit. Either way the acceptance test is the same: an appointment in your CRM sandbox after a real stock check, and a payment question that gets the published price and nothing else.