Weekly Internet Lead Review Meeting: Agenda and Questions

The meeting was on the calendar as "Internet." It ran 85 minutes. The BDC lead read a CRM export. The used-car manager checked his phone. The GM asked why Marketplace was "down." Nobody defined down. Three action items were spoken. None were written. Next week, the same export returned with newer dates.

A weekly internet lead review meeting is supposed to make the funnel visible and assign the next repair. It is not a tour of every lead. It is not a vendor complaint hour. It is a short, exception-based review with questions that make fake appointments uncomfortable.

This agenda is for GMs, internet directors, and used-car managers in independent and franchise stores. It times the meeting, lists the questions that actually change next week's work, and shows how to close so owners cannot hide in the group nod.

A Weekly Internet Lead Review Meeting Agenda That Ends With Owners

Cap it at 40 minutes. If you need 90, your CRM is doing the meeting's job in the room, which means it is not doing it in the system.

Who must be in the room

• Internet director or the GM if that title does not exist.
• BDC lead or the specialist who owns first response.
• Sales manager who owns greeting internet appointments.
• Used-car manager when listing accuracy or aged units are on the exception list.

Floor reps do not all need to attend. Bring a rep only when a specific handoff pattern is the topic. A full sales meeting that "includes internet" will bury the agenda.

Timed agenda

Print this table. When someone starts a five-minute anecdote, point at the clock.

Pre-work, or do not meet

By Monday morning, the internet owner sends a one-pager: new leads by source, first-attempt misses, appointments set and shown, unworked at close, sold units still advertised, and three example leads. If the packet is missing, the meeting is a standup: "Why is the packet missing?" then adjourn. Rewarding unprepared meetings trains unprepared weeks.

Questions Every Weekly Internet Lead Review Meeting Should Ask

Questions beat dashboards because dashboards hide definitions. Ask these in the same order each week so the room learns that evasion will be asked again.

Coverage and speed

• Which daypart missed the first-attempt SLA, and was it staffing or ignore?
• How many new leads had no human attempt at close on the worst day?
• Did after-hours leads have a named owner, or did they wait for the opener's mood?

If you already published speed to lead standards by lead type, this segment is a variance review, not a philosophy class.

Funnel truth

• Pull three leads marked contacted. What was the actual first human action?
• Pull three marked appointment. Is there a time, a vehicle, and a confirmation?
• Pull three marked dead. Was that a real stop, or a way to clear the board Friday?
• Which leads were worked in Messenger or text and never entered in the CRM?

Use lead to appointment funnel stages as the shared language. If two managers use different stage names, the meeting will argue vocabulary for 20 minutes.

Appointments and shows

• Which no-shows were never confirmed the day before?
• Which shows arrived to a car in recon, a missing key, or no greeter?
• Which "appointments" were "come by this weekend"?
• Did the floor know the buyer's name and stock number before they walked in?

Sources and the board

• Which source produced the most unworkable records (bad phone, duplicate, sold unit)?
• Which source produced shown appointments, not just fills?
• How many inquiries this week were about units that were not actually available?
• Are we still posting in bursts that slam the BDC on one day and starve it on the next?

The question that ends folklore

"What will be different by next Thursday, who owns it, and what evidence will we look at?" If the room cannot answer in one sentence, it was not an action. It was a vibe.

How to Review Leads Without Turning the Meeting Into a Trial

Exception review is not public execution. The goal is a pattern.

Sample rules

• Always include at least one success: a clean set and show, so the standard is visible.
• Always include at least one process miss and one inventory miss, so the BDC is not the only defendant.
• Do not pick only the lead that embarrassed a manager in the driveway. That is revenge sampling.

Language that keeps the room adult

• "The status does not match the notes" is useful.
• "You people do not care" is not.
• "The listing was live after the deal" is a used-car desk item.
• "No time was offered" is a BDC skill item.

If call recordings exist, play 60 seconds of the appointment ask, not the whole call. Pair this meeting with call monitoring and coaching for BDC reps so skill work happens in coaching hours, not as a group roasting.

Write actions like dispatch tickets

Bad: "Get tighter on follow-up." Good: "Maria confirms all Tuesday–Thursday internet appointments by 4 p.m. the day before; GM samples five records Thursday at 4:15."

Carry unfinished tickets at the top of next week's packet. If a ticket is older than two weeks, it is either wrong or unowned. Kill it or escalate it to the GM as a priority conflict.

Cadence Variants for Small Stores

A 40-unit independent with one specialist still needs the meeting. Shrink the packet, not the honesty.

• Solo specialist plus GM: 25 minutes. Skip source theater if you only have two sources. Do not skip the three fake-appointment checks.
• Multi-rooftop: one store per meeting, or the conversation becomes the loudest store's problems.
• Sale week: keep the meeting. Sale weeks are when SLAs die and ghost appointments multiply.

Do not cancel for "we're too busy." That is the week the funnel is lying the most.

How PostToMarket Automates This

Weekly internet meetings stall when Marketplace volume, ownership, and sold-unit status live in screenshots. The packet then takes two hours to assemble and still misses the unit that drew the angry message. PostToMarket feeds the exposure and source pieces of the agenda so the room can spend 40 minutes on exceptions.

Build the packet without a scavenger hunt

• Team analytics by rep and source for the source segment.
• Leads inbox for managers so written threads can be sampled like phone leads.
• Inventory statuses and mark as sold and archive for the "still advertised" question.
• Import history and row-level errors when the week's junk started as a bad file, not as a lazy BDC.

Put an owner next to the listing being discussed

• Queues by person, manager assignment, self-queue for reps, team queue view.
• Roles that match who is allowed to post and who is assigned.
• Mobile dashboard so the used-car manager can check queue order on the lot before the meeting, not after.

Stop the feast-or-famine posting that wrecks Monday's SLA

• AutoPost, one vehicle at a time, human-like delays, server-enforced daily limits.
• AI titles and descriptions and photo picker so sampled listings are not the same cloned paragraph.

PostToMarket is independent and not affiliated with Meta. It does not guarantee that next week's numbers move. It removes the operational fog that makes the meeting a reading of folklore.

Run the Meeting Like Dispatch, Not Like a TED Talk

The weekly internet lead review meeting agenda is a 40-minute exception review: SLA breaks, ten ugly leads, appointment truth, source and listing hygiene, then tickets with names. Ask the same questions every week. Carry unfinished work to the top of the next packet.

PostToMarket keeps Marketplace inventory, queues, and source analytics in one place the meeting can trust. Starter is $59 per month for one login. Dealership is $299 per month for up to 13 logins.

Start your 10-day free trial with secure Stripe checkout. Walk into next week's internet meeting with a board that is current and an owner on every live unit. Cancel anytime.