Why agencies should score outbound on meetings held, not meetings booked

"Meetings booked" is a seductive scorecard line. It moves fast. It looks like pipeline. It also hides the empty Zoom rooms your AE sat through at 2pm.

If a third of cold-booked demos never happen, a board that celebrates bookings is celebrating waste. Agencies that sell outbound outcomes to clients need the metric that survives the calendar: meetings held.

Booked is activity. Held is the conversation.

Metabase's framing is clean. Booked counts a scheduled meeting. Held counts a meeting that actually occurred. Report both, and always show held rate (held ÷ booked) so a spike in fragile bookings cannot fake success.

Industry write-ups on cold outbound demos commonly put average no-show rates in the mid-20s to mid-30s percent. Some vendor benchmarks call a 70% to 80% show rate healthy for cold outbound. Exact numbers vary by ICP and offer. The ops point does not: if you only count booked, you optimize for calendar spam.

What breaks when agencies pay (or report) on booked only

• SDRs book anyone who says "sure" without tightening fit or timing.
• Bookings land 10+ days out, where show rates tend to decay.
• Confirmation and reminder cadence is nobody's job because the KPI already fired at booking.
• Client QBRs look green on booked volume while AEs privately stop trusting the calendar.
• Reschedules get double-counted as new bookings if your CRM is sloppy.

You did not buy more pipeline. You bought more ghost slots.

Scorecards that stay honest

For each client workspace, report weekly:

1. Meetings booked. momentum, still useful
2. Meetings held. primary outcome for outbound quality
3. Held rate. held ÷ booked over a rolling 30 days
4. No-show rate and cancel rate as separate lines
5. Rebook recovery. no-shows that became a held meeting within N days
6. Held-to-opportunity. so held meetings that go nowhere also get pressure

Attribute one meeting to one sequence and one owner. A reschedule is still one meeting, not two booked wins.

Fix the handoff that creates empty slots

Counting held meetings without changing process just makes the dashboard sad. The usual levers:

• Keep booking windows short (many teams bias toward five business days or less for cold demos).
• Require a minimum qualification bar before a link goes out.
• Own a confirmation cadence: immediate confirm, day-before reminder, same-morning nudge.
• Put a named AE owner on the calendar event the moment it books, with context in the CRM, not only in Slack.
• Re-engage no-shows fast with a low-friction reschedule path, and track recovery separately.

None of that needs more top-of-funnel volume. It recovers conversations you already paid to create.

Client QBR script that prevents gaming

When you walk into a QBR with only booked meetings, the client hears volume. When you walk in with held meetings, held rate, and a short list of no-show root causes, the client hears operations.

Bring five numbers and one narrative:

• Booked, held, held rate for the period
• Top no-show reasons you actually logged (wrong timezone, no confirm, unqualified book, AE conflict)
• Median days from book to meeting (watch the long tail)
• Rebooks recovered into held
• One process change you will ship next week

If you cannot name a process change, you are reporting weather. The point of held-rate accountability is to force that change list every week.

How this fits conversations-booked language

GTM talks about booked conversations as the optimization goal of the motion, not vanity reply rate. "Conversation" implies a real meeting, not a calendar hold that never opens. Internally, split the funnel:

• Reply → qualified interest
• Booked → on the calendar
• Held → conversation happened
• Opportunity → AE accepted the next stage

Client scorecards should weight held (and held-to-opportunity) over raw booked. Booked stays on the board as a leading indicator. It should not be the number you defend in a renewal meeting.

A simple agency policy

Publish this in the client workspace:

• Primary weekly KPI: meetings held per client
• Guardrail: held rate floor (set with the client; tighten over time)
• Bonus or internal targets may use booked only if held rate stays above the floor
• Any week where booked rises and held rate falls is an incident review, not a win

Agencies that refuse this conversation are selling calendar noise. Agencies that adopt it start fixing confirmations, qualification, and AE handoffs because the number finally hurts when those steps fail.

Score the meeting that happened. Treat the booking as a promise you still have to keep.

If you want outbound scored toward real conversations in client-isolated workspaces, join the GTM waitlist.

Sources: Metabase meetings booked metric, Vendisys demo no-show rates in outsourced outbound, SalesHive B2B meeting no-show playbook, SalesCaptain reduce no-shows, GTM product knowledge.