Speed to Lead Standards by Lead Type for Used Car Dealers
One speed-to-lead number for every channel is how stores miss Marketplace chats and over-staff website forms. Set different standards by lead type, then staff and measure them separately.
A used-car manager walks the tower at 11:40 a.m. and asks how fast the store is on internet leads. Someone says "under five minutes." That number is an average of a website form that sat for forty minutes, a Marketplace ping answered in ninety seconds from a phone, and three after-hours inquiries that nobody touched until the next morning. The average looks respectable. The actual buyers did not experience anything close to it.
Speed to lead is not one number. A Marketplace shopper with three other sellers in tabs does not wait the same way a website lead who submitted a credit form does. Phone-ins from a listing, Facebook group comments, and overnight form fills all have different decay curves. If you apply one standard to all of them, you will over-serve the slow channel and abandon the fast one.
This article sets speed to lead standards by lead type for used car dealers: how to define first response, how to set different clocks by channel, how to staff them, and how to stop reporting a blended average that hides the leak.
Why One Speed-to-Lead Number Lies to Used Car Dealers
The phrase "speed to lead" usually means time from inquiry arrival to first human response. That definition is useful only if "inquiry" and "response" mean the same thing on every channel. They do not.
Channels decay at different speeds
- Marketplace / Messenger. The buyer is still on the listing. A delayed "yes it's available" often arrives after they have already booked another lot.
- Dealer website form. Some urgency, but the buyer already invested a name and phone. They will often wait longer than a Messenger ping, not forever.
- Phone-in from a listing. The clock started when the phone rang. If you miss it and call back an hour later, you are a callback, not a conversation.
- After-hours anything. The buyer may still be shopping at 9 p.m. Your opening-bell blast at 9:05 a.m. is competing with whoever answered last night.
A blended "average response time" rewards the channel you already handle well and hides the one that is dying. If you want to measure Marketplace lead response time honestly, it has to sit in its own bucket.
What counts as a first response
Define this in writing or every rep will game it:
- An auto-reply is not a first response.
- Opening the thread without sending is not a first response.
- "Yes" with no next step is a response, but it is a weak one; still start the clock-stop on the first human message.
- A call that goes to voicemail with a specific callback time can count as first contact if you log it; a hang-up does not.
The quality of that first message is a separate standard, covered in the anatomy of a strong first response. Speed without a useful message just gets you to the wrong conversation faster.
Speed to Lead Standards by Lead Type
These are conservative operating standards, not industry benchmarks and not Meta rules. Tune them to your staffing. Publish them so BDC and floor stop arguing from memory.
Recommended clocks (illustrative, not a promise)
| Lead type | First human response target | Owner during store hours | After-hours rule |
|---|---|---|---|
| Marketplace / Messenger | Minutes, not "when I get to the desk" | Named on-duty person, not "whoever sees it" | Covered or parked with a morning first-touch list |
| Website vehicle form | Same daypart; do not let it sit through a sales meeting | BDC or internet desk | Same as Marketplace if the form hits a phone |
| Phone-in / missed call from a listing | Immediate if ringing; rapid callback if missed | Whoever is assigned the floor phone | Voicemail with a next-morning owner |
| Credit / finance form | Fast, but after you confirm the unit is still available | BDC plus F&I awareness | Do not quote terms in a 10 p.m. text |
| Facebook group or profile comment | Treat like Marketplace | Same on-duty owner | Do not leave it in a personal inbox overnight |
Do not publish a single "five-minute" slogan if you cannot staff Marketplace to that slogan on a Saturday. An honest standard you hit is more useful than a heroic number you miss.
Why Marketplace needs a tighter clock than a website form
The Marketplace buyer did not fill out your form. They tapped a listing, typed a sentence, and kept scrolling. Your competitor is in the same feed. The website buyer already chose your store enough to type a phone number. Both deserve a human. They do not deserve the same SLA if you have limited people.
If your team can only tighten one clock this month, tighten Marketplace first. Website forms are easier to queue. Messenger threads disappear into phones.
After-hours is its own lead type
Do not pretend overnight leads are "same as daytime" if nobody is paid to answer them. Write a separate standard:
- Who is on coverage, if anyone.
- What they are allowed to promise (availability, appointment window, not a locked price).
- What gets a morning first-touch list with a hard start time.
- What never waits until after the sales meeting.
A store that answers website forms in four minutes at 10 a.m. and ignores Friday 8 p.m. Marketplace pings until Saturday noon does not have a speed-to-lead culture. It has a business-hours culture wearing internet clothing. For a fuller after-hours model, see handling after-hours Marketplace inquiries.
How to Staff and Measure Each Clock
A standard without an owner is a poster.
Assign a living owner, not a department name
"BDC" is not an owner at 12:15 when two agents are on lunch. Put a name on the board for each daypart:
- Marketplace on-duty.
- Website form on-duty.
- Missed-call callback owner.
Rotate it. Publish it. When a lead sits, you know who to ask. Shared inboxes with no name produce the same lie as a blended average.
Measure median, not average, and never blend channels
Averages are wrecked by one lead that sat overnight. Report:
- Median first-response time by lead type.
- Count of leads that missed the published standard.
- After-hours versus store-hours, separately.
Review twenty leads a week the way you would review twenty deals: timestamp in, timestamp of first human message, channel, owner. If the CRM cannot timestamp Marketplace, you still need a clock. Screenshot times and Messenger timestamps are ugly; they are better than a guess.
Do not let posting volume steal the on-duty person
The person assigned to Marketplace response cannot also be the only person dumping thirty units at lunch. That is how speed-to-lead dies on the days you most need it. Split posting windows from response windows, or give posting to associates on a queue while a named rep or BDC agent owns the inbox.
Pitfalls That Inflate Speed and Shrink Appointments
Fast and useless is a common failure mode.
Auto-replies that stop the clock in the CRM
If your CRM marks "responded" when an autoresponder fires, your speed-to-lead report is fiction. Keep the auto-ack if you want, but the human clock starts when a person sends the next message or places the call.
Racing to say "yes" and then disappearing
A ninety-second "still available" with no appointment ask meets the speed standard and fails the business. Pair every speed rule with a first-response quality rule: confirm the unit, ask one qualifying question, offer two appointment windows.
Cherry-picking easy leads
Reps will answer "is this still available" on a $9,000 car and leave a credit form on a $28,000 truck. Publish that missed-standard counts are by lead, not by how "hot" someone felt. Managers should sample the ignored pile, not only the ones that got appointments.
Counting internal forwards as customer contact
Forwarding a lead from BDC to a floor rep is not speed to lead for the customer. The customer is still waiting. Measure customer-facing first touch. Handoff time is a different metric and belongs in lead handoff rules between BDC and the sales floor.
How PostToMarket Automates This
Different lead types need different clocks, but Marketplace speed fails when inquiries live on personal phones and when the person who should answer is buried in manual posting. PostToMarket is not a CRM timer. It is the operational layer that keeps Marketplace inquiries visible and keeps posting from colliding with response duty.
Make Marketplace inquiries visible to the people on the clock
- Leads inbox so managers can see which conversations are waiting instead of asking the floor to "check your phone."
- Roles (admin, manager, sales rep, sales associate) so response duty can sit with a manager-visible owner, not a shared login.
- Team analytics by rep and source so Marketplace is not blended into a generic "internet" pile in the only report the GM reads.
Stop posting from eating the response window
- Personal and per-rep posting queues, with managers assigning units to associates, so posting work is scheduled instead of stolen from whoever is nearest the inbox.
- Chrome extension that posts one vehicle at a time with human-like delays and server-enforced daily limits, so the store is not dumping a burst of listings in the same hour it is supposed to be answering buyers.
- Mobile dashboard that can live on a phone's home screen, so the on-duty person can reorder the posting queue between customers instead of disappearing into a back-office batch.
Keep the unit status current so a fast reply is also true
- Inventory statuses and mark as sold so a two-minute reply does not confirm a car that already left the lot.
No tool can guarantee Facebook will deliver every message instantly or that every buyer will wait. Faster operational visibility reduces the minutes that are entirely under the store's control.
Put a Clock on Each Lead Type, Then Staff It
Speed to lead standards by lead type give used car dealers a number they can manage: Marketplace on one clock, website forms on another, after-hours on a third. Publish owners by daypart, measure medians, and stop congratulating the store on a blended average.
PostToMarket helps you keep Marketplace posting paced and inquiries visible while that clock runs. Starter is $59 per month for a solo operator with one login. Dealership is $299 per month for up to 13 team logins.
Open the 10-day free trial and check out through secure Stripe checkout. Set your queues, put a name on Marketplace response, and measure the channel that actually decays in minutes. Cancel anytime.