Inquiries per Unit: A Simple Listing Health Metric

A used-car manager can tell you days-to-turn on the pack. Ask how many Marketplace conversations each live unit produced last week and you usually get a shrug, a Messenger screenshot, or a claim that "the good cars always get messages." That is not a metric. It is folklore. Silent listings hide in the same feed as the truck that filled the inbox, and the desk treats both as "posted."

Inquiries per unit is a simple listing health metric you can run without a data team. It does not prove a listing will sell. It does not measure Facebook distribution. It answers a narrower question: of the vehicles that were actually live, how many conversations did we record, and which VINs produced none? Used as a health check, it tells you where to fix a photo, a price, a description, or a dead posting status. Used as a vanity rate, it will lie to you.

This article is for internet directors and used-car managers who already track aging and want one number that is honest enough to act on. Pair it with how to write listings that get messages when the problem is copy, and with lead response time when the problem is speed.

Define Inquiries per Unit Before You Count

If two managers define "inquiry" differently, the metric is a fight, not a tool.

What counts as an inquiry

Count a conversation, not a notification. Practical definition:

• A buyer-initiated Marketplace message about a specific vehicle (availability, price, condition, appointment, or options).
• Logged against that VIN, not against a generic "Marketplace" bucket.

Do not count:

• Your own replies.
• Reactions, listing views, or "people reached" screens you cannot verify.
• Repeat pings in the same thread unless you are measuring something else (then say so).
• Obvious scam or wholesale-spam openers, if you already have a triage rule that files them separately.

Write the definition on the scorecard. Change it only at month start.

What "per unit" means

Denominator is live retail units, not posts:

• Unit = a VIN that was in posted status for a defined window (illustrative: a calendar week, or the last seven days).
• A vehicle posted three times in that window is still one unit.
• A vehicle that never reached posted status is not in the denominator. Including drafts inflates silence that was really a queue problem.

Numerator is inquiries logged against those VINs in the same window. A unit with three messages and a unit with zero both belong in the set. The metric is total inquiries divided by live units. The useful view is also the list of zeros.

Why this is a health metric, not a sales forecast

A high inquiries-per-unit number can mean:

• The listing is visible and the price is interesting.
• The listing is underpriced or uses bait language.
• Reps are slow, so buyers send a second and third "you there?"

A low number can mean a weak listing, a throttled account, a saturated segment, or a logging failure. The metric tells you where to look. It does not tell you to buy twelve more of the quiet body style, and it does not tell you the listing is "banned." Diagnose before you act.

How to Capture Inquiries per Unit on a Real Floor

Most stores fail this metric at capture, not at math.

Pick a single inbox, then enforce it

If inquiries live in five personal Messenger threads, you will undercount the quiet units and overcount the noisy rep. Route Marketplace conversations into one place a manager can see. A leads inbox is the operational version of that rule. If you are not there yet, a shared log (VIN, timestamp, first message type, owner, first reply time) is better than nothing.

Rules that keep the log honest:

• First message creates the row. Later messages in the same thread do not create new inquiries unless you explicitly track "reopens."
• The VIN on the row must match the listing the buyer saw. "The silver one" is not a VIN.
• Unassigned threads at close of day are a process miss, recorded as such.

Tie every inquiry to a live listing

An inquiry on a sold unit, a pending unit, or a vehicle that is not in inventory is a hygiene problem. It still gets a row, with a flag: sold-still-live, wrong vehicle, or duplicate listing. Those flags belong in the health review. They should not inflate "demand" for a segment.

A weekly tally a manager can finish in fifteen minutes

1. Export or list VINs that were posted during the window.
2. Count inquiry rows per VIN.
3. Sort: zeros, ones, many.
4. Pull the zero list into a working queue: photo, price, copy, visibility check, or archive if the unit is not actually for sale.
5. Spot-check the "many" list for bait pricing, duplicate ads, or a unit that is too cheap relative to the jacket.

You do not need a dashboard for step one. You need a frozen VIN list and a log. Later you can automate the statuses. First you need the habit.

How to Act on Silence, Noise, and Zeros

The point of inquiries per unit as a listing health metric is a punch list, not a chart.

The zero list

Treat a live unit with zero conversations after a fair window as a patient, not a corpse. Work the list in this order:

1. Is it actually live and findable? Search logged out for year, make, model, and city. If you cannot find it, you do not have a demand problem.
2. Is the lead photo doing harm? Dark lot, doors open, stock image, or a photo of a different color.
3. Is the price field honest and aligned with the description? Mismatches and "$1" games produce removals or the wrong buyers.
4. Is the copy unique and specific? Cloned DMS dumps read as spam even when the car is real.
5. Is the unit in a dead segment or a glut? If comps are stacked in the feed at lower prices, silence may be the market.

Fix one variable at a time. Changing price, photos, and description on the same afternoon teaches you nothing.

The noisy list

A unit with a pile of messages is not automatically healthy:

• If every thread is "is this still available?" and nothing after your reply, you may have a response-quality problem, not a listing problem.
• If threads mention a different year or trim, the title or photos are wrong.
• If the price in the ad is not the price on the jacket, you are collecting arguments.

Guardrails so the metric does not become a whip

Do not rank reps on inquiries per unit alone. A rep given aged, overpriced units will "lose" to a rep given fresh trucks. Compare similar segments, similar price bands, and similar days live. Use the metric to coach listing quality and response, not to run a public leaderboard.

Do not set a fake target ("every unit must get N messages"). You do not have a published Marketplace baseline, and this article will not invent one. Use relative ranks inside your own pack: zeros vs. the rest, this week vs. last week on the same definition.

Put Inquiries per Unit on the Monthly Card

A weekly zero list is for the desk. A monthly rollup is for the GM.

Roll up without blending away the truth

• Report median inquiries per unit as well as the average, if a few viral trucks would hide a silent sedan row.
• Report the share of live units with zero inquiries.
• Report the share of inquiries with no same-day reply, so you do not confuse health of the ad with health of the desk.

That package sits cleanly on a monthly Marketplace performance scorecard. Inquiries per unit is one row. Coverage and sold-unit hygiene are other rows. Do not collapse them.

Edge cases that break the ratio

• Short-lived units. A car posted at 4 p.m. and sold at 5 p.m. can have zero inquiries and still be a success. Tag units live less than a day.
• Pending and wholesale. Do not leave them in the denominator.
• Multi-lot. Compute per rooftop, then a store total, or you will hide the quiet location.
• Seasonal segments. Compare convertibles to last convertible month, not to trucks in the same week.

Illustrative: a lot with 40 live units and 20 logged inquiries has 0.5 inquiries per unit. That number is meaningless until you see that 28 units had zero and two trucks had most of the twenty. Always keep the zero list.

How PostToMarket Automates This

Inquiries per unit falls apart when listings have no stable status and messages never leave personal inboxes. The operational problem is tying each conversation to a VIN that is actually posted, then seeing which posted units produced nothing.

PostToMarket inventory statuses (draft, posting, posted, sold, failed) give you a clean denominator: posted units, not drafts and not hope. Unlimited vehicles in inventory means the full pack can sit in one system. AI-generated titles and descriptions, editable before posting, plus the Facebook photo picker, are the levers you pull when a zero is a listing-quality miss. The leads inbox gives managers a place to see inquiries instead of reconstructing them from screenshots. Team analytics by rep and source help you ask whether silence is a person, a source file, or a segment. Per-rep queues and manager assignment keep ownership clear so "nobody answered" has a name. Mark as sold and archive so sold units drop out of the live set. PostToMarket is not affiliated with Meta and does not guarantee distribution; the metric measures your logged conversations against your posted inventory.

Turn Silence Into a Punch List This Week

If you cannot name the live units that produced zero Marketplace conversations, you are managing folklore. Inquiries per unit is simple on purpose: count, list the zeros, fix one cause at a time.

PostToMarket includes unlimited inventory, AI listing copy, bulk import with a row-level error log, per-rep queues, a leads inbox, and AutoPost that submits one vehicle at a time with human-like delays. Starter runs $59 per month for one login. Dealership runs $299 per month for up to 13 logins.

Start your 10-day free trial with secure Stripe checkout. Get statuses and inquiries into one dashboard, then run the zero list on facts. Cancel anytime.