BDC

AI BDC handoffs. When should a person take over?

A practical lesson for BDC managers on the moment a customer needs a person.

A dealership manager reviewing an AI BDC handoff with a colleague at a laptop.

An AI BDC handles the first replies, routine questions and appointment requests that arrive at a dealership. A person should take over when the shopper asks for one, needs a decision outside the approved rules, or raises a concern the AI cannot resolve from verified information. A useful handoff preserves the question and assigns responsibility.

Key takeaways

  • A request for a person should trigger a handoff.
  • An alert does not prove that someone has answered.
  • The next employee needs the unresolved question and relevant conversation history.
  • Test the full transfer, including what happens when staff are unavailable.

Imagine this fictional showroom conversation. A shopper asks whether a used SUV is available, then asks for a lower price because a competing store has a similar vehicle. The first question may have an inventory answer. The second needs someone authorized to discuss the deal. Repeating a booking invitation leaves the real question untouched.

Our overview of AI BDC for car dealerships (opens in a new tab) explains the broader role. This article focuses on the moment a conversation needs human judgment.

Why should managers test the handoff?

A system can answer promptly and still leave the customer waiting for help. In its September 14, 2026 Service Scheduling Effectiveness study (opens in a new tab), Pied Piper reported that roughly one in three attempted AI to human transfers failed. Customers reached voicemail, disconnected or remained on hold.

The study evaluated 6,538 service requests across 33 US automobile brands and four independent service center brands. It studied service scheduling, not sales lead conversion or QualiFlow performance. The useful lesson for a BDC manager is to test the complete interaction, rather than treating a fast first answer as proof of resolution.

When should an AI BDC hand the conversation to staff?

Set a clear boundary whenever the customer needs an authorized decision, a verified answer the system lacks, or personal attention. Write that boundary into the store’s operating process before testing the tool.

  • Inventory question: Check the approved record. Staff resolve conflicting or missing information.
  • Discount request: Preserve the request without agreeing. Staff discuss and authorize the offer.
  • Trade value: Collect vehicle details. Staff arrange and complete an appraisal.
  • Request for a person: Begin the handoff. Staff accept the conversation and answer.
  • Complaint: Record the concern. Staff review and respond personally.

These are proposed operating boundaries, not a claim that every AI product behaves this way. A published price is different from an approved discount. A preferred visit time is different from a confirmed booking. Keep those distinctions visible to the shopper and the team.

What information belongs in a useful handoff?

Give the employee enough context to answer the unresolved question without making the customer start again. Record the vehicle or service involved, the customer’s own request, relevant facts already checked, and the next action. Include the preferred contact channel and language when known.

For the fictional SUV inquiry, a useful note might read: “Customer is interested in the listed SUV and asks whether the store will match another advertised offer. No discount agreed. Sales manager review needed.” Keep the original conversation available so the employee can check the summary.

The NIST AI Risk Management Framework Playbook, Govern 3.2 (opens in a new tab), recommends defining responsibilities for human oversight. It is voluntary guidance, not a dealership performance study. Our practical application is simple: decide who receives each exception, who covers their absence, and who checks that it was answered.

How can a BDC manager test the process?

Run controlled test conversations from the customer’s first question through the employee’s response. Use test records and follow the store’s testing policy so the exercise does not create false customer work.

  1. Ask an ordinary inventory question, then request a discount. Check that the request reaches the right employee without an invented concession.
  2. Ask directly for a person. Confirm that the system stops repeating qualification questions.
  3. Repeat the test when the usual employee is unavailable. Check the backup route and the customer’s message.
  4. Have staff take over. Confirm that automated replies stop in that conversation.
  5. Read the employee’s answer. Check that it addresses the original question and preserves any limits already stated.

Record where each test stopped: recognition, routing, acceptance or answer. “The alert appeared” only proves routing. It does not prove an employee accepted the work or the customer received an answer. Our guide to testing dealership software before rollout (opens in a new tab) explains how to define acceptance evidence.

What should happen when nobody is available?

Give an honest next step and preserve the request for staff. Do not promise an immediate callback or a named employee unless the store can support that promise. A requested callback also needs a responsible person and a way to check completion.

Review the customer’s actual message as well as the internal queue. A clear internal task cannot repair a misleading promise. For the wider evening process, read our guide to handling dealership leads after closing (opens in a new tab).

How should the dealership measure handoff quality?

Count eligible handoff requests separately from routine conversations. Track whether each request reached an owner, received an answer, and remained unresolved at review time. Keep the time of the AI reply separate from the time of the staff answer.

Compare similar channels and staffed periods. A rise in escalations may mean the system is recognizing more requests that need people. Read the conversations before deciding whether the change is good or bad. Do not convert a transfer count into a sales result.

What should you ask to see in a QualiFlow demo?

QualiFlow AI is an AI agent platform for US car dealerships; its AI agent, Aria, answers every lead within moments, day or night, and books the appointment when the calendar confirms.

The QualiFlow AI BDC overview (opens in a new tab) describes staff alerts and conversation takeover. Bring a negotiation request or customer concern and book a free 30 minute demo (opens in a new tab) to follow that request through the handoff. Ask what happens when the employee is unavailable, where the history appears, and how your team confirms the answer was sent.

Frequently asked questions

Does an AI BDC replace the sales manager?

An AI BDC can handle routine communication within the dealership’s approved rules. Decisions about discounts, trade appraisals and deal terms still need authorized people. Define those responsibilities before rollout, then test whether the system recognizes the request and passes the relevant context to staff.

What counts as a completed AI BDC handoff?

For a useful operating review, separate routing from resolution. An alert proves that work was sent somewhere. Staff acceptance proves that someone has picked it up. The customer still needs an answer to the original question. Record those stages separately so a successful alert does not conceal an unanswered request.

Should the AI keep asking questions after a customer requests a person?

A request for a person should begin the handoff rather than another qualification loop. The system may need limited information to route the request, but the customer should understand what happens next. Test the actual conversation and confirm that a staff member can see the request and its context.

What should a dealership check before enabling automated replies?

Check the approved information, decision boundaries, staff ownership and backup coverage. Test an ordinary question, an exception and a direct request for a person. Confirm that staff takeover stops automated replies in that conversation. Review the customer’s final answer as well as the internal alert before expanding use.

Sources

Luis Garcia writes QualiFlow’s educational articles for dealership sales and BDC teams. Examples and the proposed review method are illustrative.

Keep reading

More from the QualiFlow blog.

Every lead gets a reply

Never leave a lead waiting until morning.

Aria answers, qualifies and books test drives around the clock, in English, Spanish and French, inside the rules you set.

Smart Flow · Card required. Subscription charges automatically after seven days unless cancelled; optional guided onboarding is charged upfront. Nothing goes out to customers until you connect your channels and approve Aria’s go-live checklist.