Lead Handoff Rules Between the BDC and the Sales Floor

The BDC marks the lead "appointed." The floor is in a deal. At 4:50 p.m. a couple walks in and says they were told to ask for Mike. Mike is on a test drive. Nobody has the stock number, the CRM note says "interested in the silver truck," and the greeter treats them like a cold walk-up. They wait twelve minutes, look at a different unit, and leave a one-star story about a store that "didn't know we were coming."

That is not a lead-quality problem. That is a handoff failure. Lead handoff rules between the BDC and the sales floor exist to make an appointment a transferable object: vehicle, time, greeter, conversation summary, and a fallback if the greeter is stuck. Without those rules, BDC and floor will each believe they did their job while the buyer stands in the showroom unpaid.

This article is the operating play for internet directors and used-car managers who already decided who owns first response. If you still need that org-chart decision, start with BDC vs floor handling. Here we assume both teams exist and still drop the baton.

What a Complete Handoff Contains

If it is not in the record before the visit, it does not exist. Verbal "I told them" is not a handoff.

The required packet

• Buyer name and best number.
• Vehicle: stock number or VIN, plus a one-line description they will recognize ("silver 2019 Ram, crew, stock 4412").
• Status of that unit at handoff: available, pending, in recon, or substitute already agreed.
• Appointment date/time and whether they confirmed in the last touch.
• Named greeter, plus a backup name.
• What was already promised (price quoted, trade mentioned, "we'll pull it up front").
• Open questions (financing, out-of-area, second driver).
• Channel of origin (Marketplace, website, phone-listing) so the greeter does not ask them to "fill out a form we already have."

If any of the first five bullets is missing, the appointment is not set. It is a hope.

What does not belong in the packet

Do not dump a credit application, a full recap of every message, or internal gossip ("this guy is a time-waster"). The greeter needs to start a human conversation, not a trial. Keep sensitive financial data in the system of record your store uses for that purpose. This is not legal advice; confirm with counsel how you transfer and store customer information between desks.

Timing and Ownership Rules That Prevent Dual-Texting

Most bad handoffs are not missing data. They are two people talking to the customer at once, or nobody talking after the set.

One thread owner until greet

From first response until the greeter has made in-person contact, one team owns outbound messages. Typical rule:

1. BDC owns the thread until the appointment start time.
2. At start time minus a published window (for example, the morning of the visit), BDC sends a confirmation and copies the greeter in the CRM, not in a side text the floor will miss.
3. Floor owns the conversation from greet onward. BDC does not send "how did it go?" to the customer while they are on the lot.

If the floor needs to take the thread early (buyer insists on texting the salesperson), the CRM owner field changes and BDC stops. Parallel courtesy texts feel like care. They feel like chaos to the buyer.

The named greeter is a required field

"Ask for sales" is an incomplete handoff. Put a person. If that person is in a deal, the backup greets within a few minutes and says the named person's name. The buyer should never have to explain why they are there twice.

Failed greets have a clock

If the buyer is more than a short, published grace window late, the greeter logs it and the original thread owner starts the no-show sequence. Do not let a late appointment sit on the board as "still coming" until close. That is how you miss the rescue call.

Confirmation mechanics that reduce no-shows are covered in the appointment confirmation sequence. Handoff rules make sure that sequence has a human to hand to.

Handoff Failure Modes Used-Car Stores Repeat

Name them in training so people can catch themselves.

The ghost unit handoff

BDC sets an appointment on a VIN the floor already marked sold, or that is in recon and not showable. Rule: inventory status is checked at set and again at confirmation. If the unit is gone, the appointment is re-cut on a substitute or cancelled honestly. Never "we'll find you something" with no vehicle named.

The orphan greeter

Appointment sits on a manager's name who is not on the floor. Rule: greeter must be a person scheduled to work that daypart. Managers can be backups. They should not be the default because nobody wanted to pick a rep.

The second negotiation

BDC quoted a number to get the appointment. Floor starts over at a higher number with no explanation. Rule: promised numbers are in the packet. If the floor cannot stand behind them, the appointment is not set until a manager reconciles. Undercutting your own first conversation is how internet buyers decide the store is bait.

The CRM fork

Floor cannot find the BDC record, creates a walk-in, loses the source, and the BDC keeps working a lead that already arrived. Rule: search phone before create. If a walk-in says they have an appointment, the greeter searches before they build a new up.

The after-hours set with a morning vacuum

BDC or an on-call rep sets a 10 a.m. Saturday appointment at 9 p.m. Friday and nobody on Saturday's floor reads the notes. Rule: after-hours sets hit a next-day board that the opening manager is required to read. Not "it's in the CRM." A board, a huddle, or a printed list — whatever you will actually look at.

A Written Play the Floor Will Actually Use

Long SOPs die. A one-page play survives.

BDC side (before it is "set")

• Packet complete.
• Greeter and backup named and scheduled.
• Unit status verified.
• Customer has the greeter's name and the vehicle description in their last message.

Floor side (before the time slot)

• Greeter acknowledges the appointment in the CRM or board (a simple "got it").
• Keys and location of the unit known, or recon status known.
• If the greeter will be in a deal, backup is told before the slot, not after the buyer is waiting.

Manager side (daily)

• Unacknowledged appointments are defects, same as missing stock numbers on deals.
• Dual-text incidents are coaching, not jokes.
• Sold-unit appointments are emergencies: call before the buyer drives in.

For Marketplace-specific first messages that make this packet easier to build, use the anatomy of a strong first response. A sloppy first reply produces a sloppy handoff because nobody captured the vehicle.

How PostToMarket Automates This

Handoffs break when the BDC is working a Facebook thread the floor cannot see and a vehicle status the lot already changed. PostToMarket does not move records into your CRM. It keeps inventory and Marketplace inquiries in a state both desks can trust.

Same vehicle truth on both sides of the baton

• Inventory statuses (draft, posting, posted, sold, failed) so a set appointment is not built on a ghost.
• Mark as sold and archive from inventory or the queue, which should trigger a same-day appointment review.
• Unlimited inventory on every plan, so the unit in the packet is the unit in the system.

Visibility so the floor is not guessing

• Leads inbox for managers, which is the difference between "BDC said they messaged" and a thread a manager can inspect.
• Team analytics by rep and source so you can see whether Marketplace work is actually flowing toward appointments.
• Roles (admin, manager, sales rep, sales associate) and team queue view to release stuck claims — the posting analog of a lead nobody will greet.

Posting duty that does not steal the greeter

• Per-rep queues and manager assignment to associates.
• Mobile dashboard to reorder the posting queue between customers.
• Chrome extension that posts one vehicle at a time with human-like delays and server-enforced daily limits, so the greeter is not disappearing into a burst of listings at 4:45.

PostToMarket is independent and not affiliated with Meta. It will not make a greeter appear. It will reduce the "we didn't know about this car or this message" class of handoff failure.

Write the Handoff Rules, Then Treat Broken Packets as Deals Without Stock Numbers

Lead handoff rules between the BDC and the sales floor are a required packet, one thread owner, a named greeter, and a clock on failed greets. If the packet is incomplete, the appointment is not set. If two desks text at once, that is a defect.

PostToMarket keeps the inventory and Marketplace half of the packet from being a rumor. Starter is $59 per month for one login. Dealership is $299 per month for up to 13 logins, including two managers.

Open your 10-day free trial with secure Stripe checkout. Get sold units off the board, put inquiries where managers can see them, and give the floor a vehicle they can actually greet. Cancel anytime.