Why booking volume lies about scheduling health
Picture a growth-stage digital agency or commercial brokerage reviewing pipeline numbers on Friday afternoon. Discovery calls dropped from 28 last week to 17 this week. Marketing blames lead quality; partners blame seasonal softness; someone suggests raising Google Ads bids.
Nobody checks whether the intake link offered open times on Tuesday and Wednesday. Without supply-side telemetry, a 48-hour OAuth disconnect or an unintended calendar hold masquerades inside your CRM as a marketing slump. Measuring availability directly separates "prospects didn't want to meet" from "prospects couldn't find a slot."
Supply-side KPIs also resolve cross-functional friction between marketing and delivery partners. When a firm spends $12,000 a month on paid search or referral dinners, every unbookable hour on the primary scheduling link acts like an unplugged phone line at the front desk. Tracking availability on the same dashboard as pipeline conversion gives operations an objective, blame-free baseline: marketing owns traffic to the scheduling surface, while practice leadership owns keeping that surface inside agreed lead-time and depth targets.
The 5 core Calendly availability KPIs (formulas & targets)
1. Time-to-Next-Slot (TTNS)
TTNS = t(first_open_slot) − t(poll)What it measures: How long an inbound prospect visiting your scheduling URL right now must wait for the earliest selectable appointment. Express TTNS in business hours during working windows so Friday-at-4:30-PM readings onto Monday at 9:30 AM aren't penalized for Saturday and Sunday.
Target band: Median TTNS ≤ 16 business hours (roughly 2 workdays) and p95 TTNS ≤ 24 business hours on new-client intake; median ≤ 32 business hours on direct partner consults.
2. Normalized 7-Day Slot Depth (SD-7)
SD-7 = GreedyNonOverlappingSlots(now, +7d)What it measures: How many real appointments can fit inside the next 7 calendar days. Always normalize overlapping increments: if a 30-minute call offers start times at 10:00, 10:15, and 10:30 inside a single 60-minute gap, booking 10:15 eliminates both 10:00 and 10:30. Counting greedy non-overlapping blocks prevents 15-minute increments from exaggerating true capacity by 2× to 3×.
Target band: ≥ 10 non-overlapping slots per individual intake link; ≥ 25 across a multi-host round-robin pool. Alert below 5.
3. Zero-Slot Incident Duration (ZSID) & Availability Uptime %
Uptime = 1 − (ZeroSlotMinutes / TotalMinutes)What it measures: Total elapsed minutes an active public event type offered zero bookable slots inside its configured rolling horizon, paired with Mean Time to Remediate (MTTR) from breach detection to slot restoration.
Target band: ZSID = 0 minutes on team intake pools (99.9% uptime); MTTR < 45 minutes during business hours when an individual advisor's OAuth token or calendar block trips an alert.
4. Host Coverage Ratio (HCR)
HCR = HostsWithSlots(≤72h) / ActivePoolHostsWhat it measures: The fraction of assigned round-robin members who actually contribute at least one bookable slot within the firm's SLA horizon. If a 6-advisor pool reports healthy TTNS only because 2 junior advisors supply 100% of open times (HCR = 33%), your pool is one sick day away from collapse (see staff calendar oversight).
Target band: HCR ≥ 75% during non-holiday weeks; investigate whenever HCR drops below 50%.
5. 7d-to-30d Horizon Skew Ratio
Skew = Slots(0..7d) / Slots(0..30d)What it measures: How much of a host's 30-day supply is front-loaded into the immediate week. In an evenly paced 30-day calendar, roughly 20–25% of slots sit inside the next 7 days. A Skew Ratio below 5% (for example, 1 slot this week and 38 slots three weeks out) flags chronic near-term calendar blocking or an excessive minimum-notice setting.
Target band: 15% to 30% on rolling 30-day event types.
Running a 10-minute Weekly Next-Spot Review
Metrics only change behavior when reviewed on a predictable drumbeat. High-performing practice managers add a 10-minute scheduling health block to Monday morning operations standup. Here is what a live scorecard looks like for a six-partner advisory practice and how each reading maps to an immediate operational fix:
| Monitored link | p95 TTNS | SD-7 | ZSID (7d) | Monday ops action |
|---|---|---|---|---|
| Firm Intake Round-Robin (20m) | 11 hrs | 34 slots | 0 min | Healthy — no intervention needed |
| M&A Advisory Pool (30m) | 68 hrs | 4 slots | 0 min | HCR = 1/3; clear recurring tentative deal holds on Host 2 |
| Partner Chen — Tax Consult (45m) | > 14 days | 0 slots | 410 min | M365 password reset broke OAuth; EA re-authenticating sync |
| Partner Patel — Estate Review (60m) | 92 hrs | 2 slots | 0 min | Trim symmetric 30m buffers to 0m-before / 15m-after |
Worked calculation: why raw timestamp counts deceive RevOps
Suppose an advisor leaves Thursday open from 13:00 to 15:00 (120 minutes) for a 45-minute Discovery Call configured with a 15-minute after-buffer and 15-minute start-time increments. Calendly's public JSON feed returns five selectable start times: 13:00, 13:15, 13:30, 13:45, and 14:00.
A naive dashboard that sums array length logs "5 available slots." Yet each booked call consumes 45 + 15 = 60 minutes. If Client A books 13:00–13:45 (plus buffer until 14:00), only 14:00–14:45 remains. Worse, if Client A picks 13:30–14:15 right in the middle, zero additional 45-minute calls fit before or after! Greedy non-overlapping normalization walks chronologically from 13:00, claims [13:00, 14:00), claims [14:00, 15:00), and reports the true physical capacity: SD-7 = 2 appointments, not 5. That correction stops teams from overestimating intake headroom by 150%.
Instrumenting availability KPIs without spreadsheets
You cannot compute ZSID or p95 TTNS from manual spot-checks because an outage that starts Tuesday at 1:15 PM and clears Wednesday at 9:00 AM never registers unless something samples the availability surface continuously.
AvailTrack records timestamped availability check history on every active event type, tracks rule breach start and recovery timestamps, and alerts operations the minute TTNS or slot depth crosses your threshold. Explore how check history and rule evaluation work and select the polling cadence your SLA requires on our pricing page.