Tracking No-Show Patterns by Lead Source and Daypart

Most used-car meetings treat no-shows as a character issue. The rep "didn't confirm." The buyer "wasn't serious." The Saturday closer "always gets stood up." That story is convenient and usually incomplete. When you actually log misses against lead source and daypart, the same store often finds that Marketplace evening slots behave nothing like phone-ups at lunch, and that one source's Tuesday 6 p.m. appointments are a staffing problem, not a motivation problem.

Tracking no-show patterns by lead source and daypart is not a data-science project. It is a weekly tally that any desk can run on a spreadsheet. You do not need invented conversion rates or a purchased benchmark. You need a consistent definition of a show, a miss, and a source, plus enough weeks of notes to stop guessing.

This article is for general managers and internet directors who already know their CRM has a source field that nobody fills in the same way. It defines what to count, how to slice the log, how to change confirmation and staffing without overreacting to a single weekend, and how to keep Marketplace posting volume from creating appointment chaos you cannot see.

What You Are Actually Trying to Learn

The goal is not a vanity dashboard. The goal is three operational decisions:

• Which hours deserve a dedicated greeter versus a "we will squeeze you in" promise
• Which sources need a tighter confirmation sequence before you pull a car
• Which misses are lot problems (car not ready, long wait, unclear address) versus buyer problems

If the log cannot change one of those three, you are collecting trivia.

Define a show before you count a miss

Write the definitions on the sheet:

• Booked: a day and time the buyer agreed to, written in the thread or calendar.
• Show: buyer arrived during the published grace window, or called ahead and arrived in a window the desk accepted.
• Miss: no arrival, no call, and no reschedule accepted before the slot ended.
• Reschedule: a new day and time agreed before or immediately after the original slot. Count it as a miss-then-recovery, not as a clean show.

Do not count "they said they might come by this afternoon" as a booked appointment. Soft maybes inflate the miss rate and hide the real pattern.

Define lead source the way the floor actually works

Source is where the conversation started, not where the buyer eventually signed. Typical buckets for an independent or franchise used lot:

• Facebook Marketplace (and related Facebook chats)
• Dealership website form
• Phone-up / call tracker
• Walk-in / be-back
• Referral
• Third-party listing sites (group them until volume justifies a split)

If two reps log the same Marketplace buyer as "internet" and "Facebook," your pattern is noise. Pick one label and enforce it in the morning meeting.

A One-Sheet Log for Tracking No-Show Patterns by Lead Source and Daypart

You do not need a BI tool. You need columns a manager will actually fill.

Minimum columns

1. Date of appointment
2. Day of week
3. Daypart (see the grid below)
4. Lead source
5. Unit (stock or last six of VIN)
6. Rep who owned the appointment
7. Outcome: show / miss / reschedule
8. Notes in five words or fewer ("car in recon," "buyer at work," "wrong address")

That is enough. Adding credit score, trade value, and weather will make the sheet prettier and less used.

A practical daypart grid

Use the same buckets every week so you can compare:

If you close at 7 p.m. on weekdays, do not invent a "late night" bucket with three appointments a month. Sparse buckets lie.

How long before you trust a pattern

Look at weeks, not days. A single rainy Saturday is not a source problem. A conservative operating standard: review after you have a full month of booked appointments, then again at 90 days. If a cell in the grid has only a handful of bookings, treat it as "not enough to change policy" and keep logging.

Do not publish a "no-show percentage by source" as a league table in the sales meeting until the definitions are stable. Weaponized numbers make reps hide misses instead of logging them.

How to Read No-Show Patterns by Lead Source and Daypart

Once the sheet has a month of rows, sit down with the used-car manager and the internet director. Read it in this order.

Source first, then daypart inside the source

Marketplace misses clustered at weekday evenings are a different problem than website-form misses on Saturday mornings.

• Same source, one daypart hot: confirmation timing or staffing. Example: Marketplace buyers book 6 p.m. slots while the only closer is in a desk deal.
• One source hot across all dayparts: qualification or confirmation sequence for that channel, not the clock. The first reply may be booking people who never intended to visit.
• All sources hot on one daypart: lot operations. Long waits, cars not pulled, address confusion, or a greeter who is also the cashier.

Separate "did not intend to come" from "could not get here"

Notes matter more than the outcome column. "Stuck at work" repeating on weekday evenings is a daypart problem. "Found another car" repeating on Marketplace is a speed-to-lead and uniqueness problem. "Went to the other rooftop" is an address and map-pin problem.

Watch the confirmation method, not just the source

If Marketplace appointments get a same-thread confirmation and phone-ups get a call plus a text, you are comparing two processes. Log confirmation type in the notes for a month if the first cut is messy: thread only, thread plus SMS, phone call. You may find the source is innocent and the confirmation is not. For the message sequence itself, use A Confirmation Message Sequence That Reduces No-Shows as the standard, then see whether misses drop in the next month's log.

What to Change When a Pattern Holds

Change one variable at a time. If you restaff, rewrite the confirmation, and tighten qualification in the same week, you will not know what worked.

Staffing moves that match the log

• Put a named greeter on the daypart that shows the most Marketplace appointments, even if closing volume is higher at a different hour.
• Stop promising "come anytime after 5" if the log shows after-5 Marketplace slots collapsing. Offer two specific times you can actually cover.
• Do not pull Saturday closers into Monday morning internet appointments just because Saturday "feels" worse. Check the sheet.

Confirmation moves that match the source

Marketplace threads die when the last message is "see you then" with no day, time, address, and unit. Website forms often need a human confirmation call because the buyer submitted at midnight and forgot. Phone-ups may need a same-day text because they already spoke to someone. Match the channel. Do not copy a BDC script onto a Marketplace chat and call it a process.

Qualification moves without turning into an interrogation

If one source books a high share of first-touch "I'll come today" appointments that never appear, slow the book. Ask one constraint question: who is coming, and are they available at a named time. That is not a credit application. It is a filter for fantasy visits.

Inventory moves

If misses cluster on units that were still in recon or on test-drive from a previous up, the pattern is readiness, not source. Fix When the Car Is Not Ready: Handling Buyer Arrivals before you blame Facebook shoppers for walking.

Pitfalls That Make the Log Useless

Scoring reps on miss rate alone

A rep who books more Marketplace appointments will show more misses in raw counts. Compare within source and daypart, and look at recovered reschedules. Punishing volume producers trains them to stop booking.

Mixing walk-ins into the appointment log

A buyer who said "maybe Saturday" and then appeared is not a show against a booked slot. Keep walk-ins on a separate tally or you will congratulate the store for chaos.

Changing source labels mid-month

If you split "internet" into Marketplace vs. website on the 15th, start a new month. Do not splice the old rows.

Acting on tiny cells

Four misses in a bucket of six bookings is a story, not a policy. Keep logging. Change the process when the same cell is ugly for several consecutive weeks.

Forgetting sold-unit and duplicate-listing noise

If the listing is stale or the VIN is double-posted, some "appointments" are buyers arriving for a car that already left. That inflates Marketplace misses and is an inventory-control problem. Mark sold units immediately and keep one live listing per vehicle.

A Monthly Review Agenda That Stays Short

Put this on the used-car meeting once a month. Fifteen minutes.

1. Total booked appointments vs. shows vs. misses vs. reschedules.
2. Top two source-and-daypart cells by miss count (not by a dramatic percentage on a tiny sample).
3. One process change for next month, owned by a named manager.
4. One thing you will not change, so the floor does not get a new rule every week.
5. Hygiene check: are sold units archived, and are Marketplace conversations owned by one rep?

Write the process change in one sentence. Example: "Weekday Marketplace appointments after 4 p.m. get a same-day confirmation with address and two arrival options; greeter is assigned until close." Then log next month against that sentence.

When a miss still happens, the recovery belongs to the reschedule playbook, not to a new spreadsheet. Keep Rescheduling Missed Appointments Without Burning the Lead as the buyer-facing sequence so the log does not turn into a pile of angry follow-ups.

How PostToMarket Automates This

No-show patterns stay invisible when listings, conversations, and ownership live in three tools and a paper calendar. PostToMarket will not replace your appointment book, and it does not claim to predict who will show. It keeps the vehicle, the posting source, and the lead in one workflow so the monthly review is not a scavenger hunt.

Source you can actually attribute

• Team analytics with posting activity by rep and source, so Marketplace volume is not a rumor when you sit down with the no-show sheet.
• Leads inbox for managers who need to see which conversations produced a booked visit versus a dead thread.

Ownership that matches the log's "rep" column

• Per-rep queues so the person who posted the unit is visible, and associates work from assigned queues instead of a shared inbox.
• Team queue view to release a claim when the appointment owner is off and the miss would otherwise have no follow-up.

Inventory state that does not fake demand

• Statuses (draft, posting, posted, sold, failed) and mark as sold / archive so you are not counting appointments against units that already left the lot.
• Unlimited vehicles in inventory on every plan, with bulk CSV/Excel import and a row-level error log, so the board you are staffing against is the board that is actually on the ground.

The Chrome extension still posts one vehicle at a time with human-like delays and server-enforced daily limits. That pacing does not guarantee distribution, but it does reduce the burst posting that creates a pile of same-hour appointments nobody can cover.

Staff the Hours the Sheet Points To, Not the Hours That Feel Busy

A lot that guesses at no-shows will keep stacking Saturday Marketplace appointments onto a two-person desk and then call the buyers flaky. Tracking no-show patterns by lead source and daypart is how you move a greeter, tighten one confirmation sequence, and stop pulling cars for fantasy visits.

PostToMarket is built for that kind of operational discipline: unlimited inventory, AI titles and descriptions you edit before posting, per-rep queues, and a leads inbox managers can actually open. Starter runs $59 per month for a solo seller or independent lot with a single login. Dealership runs $299 per month for up to 13 logins.

Start a 10-day free trial and check out through secure Stripe checkout. Get the inventory and the posting source into one system before the next month's no-show meeting. Cancel anytime.