Prefer to watch it happen? Rami Goraly walks through every KPI below on-screen, live reports and all — skip to the recording whenever you want.
Ask most teams how scheduling is going and you will get a volume number. Ninety-four meetings this month. Up from last month. Good.
Now ask the questions that number cannot answer. Did those ninety-four spread evenly across seven hosts, or did three people take sixty of them? Were they concentrated in the 9–11am block, leaving the afternoon empty? Did they come from the LinkedIn post, the webinar follow-up, or the QR code at the seminar? How many were cancelled, and how many were reassigned to a different host after the fact?
Volume is the one metric that survives without any of that context, which is exactly why it gets reported. It is also the one metric that never changes a decision.
The backdrop makes this worse than it sounds. Microsoft's Work Trend Index research on the "infinite workday" found that employees are interrupted roughly 275 times a day — about once every two minutes during core hours — by meetings, emails, and chats. The same research found that meetings starting after 8pm are up 16% year over year, and 30% of meetings now span multiple time zones, a figure that has risen eight percentage points since 2021. Calendars are already saturated and already spilling outside working hours. Adding more bookings to a team that is quietly at capacity does not produce more revenue; it produces no-shows, reschedules, and burnt-out hosts.
The fix is not tracking more. It is tracking four specific things instead of one general thing.
This is the metric that changes how you staff a campaign, and almost nobody has it.
Utilization asks: for each hour of each day, what percentage of your available slots are already taken? A team can look comfortable at the weekly level — say, forty bookings against a theoretical seventy — and still be completely unbookable at every hour a client actually wants. When a slot hits 100% utilization, no further bookings can be made at that time, regardless of what the weekly total says.
OnceHub's Capacity Planning report, introduced in the December 2025 release, lays this out as a grid: hours down one axis, days across the other, each cell colour-coded by utilization. You can see at a glance that next Monday at 9am is two slots out of six, and that Thursday afternoon is fully blocked.
That grid is what turns a vague worry into an action. In the webinar demo, a credit union is about to email its entire client base inviting them to book a discovery call. The question is not "how many bookings will we get" — it is "do seven advisors have enough open slots to absorb them, and if not, what do we change first?"
Three levers, in ascending order of disruption:
In the demo, raising limits alone moved several fully blocked cells down to 75% and 40% utilization. Not a transformation — the advisors were genuinely busy — but enough headroom to absorb the campaign without turning people away.
Team workload management starts with a number you set deliberately, not one you discover afterwards.
OnceHub's Workload Management lets you cap how many bookings a host can receive per day, week, or month. Two details matter and are easy to miss:
Once ceilings are set, the per-host metric becomes meaningful. In the webinar's campaign view, three advisors carried a limit of twenty and the rest carried ten — and the booking report showed exactly the distribution you would expect, with the twenties running close to their cap and the tens well below. That is a healthy read. The unhealthy read is when the numbers diverge from the ceilings you set, which means distribution is not working the way you configured it.
This is the KPI that connects scheduling data to marketing spend, and it is the one most teams solve badly — by spinning up a separate booking calendar per campaign.
That approach breaks down quickly. If you have CRM integrations, automations, or routing logic attached to a booking calendar, duplicating it per campaign means duplicating all of that, and keeping it in sync forever.
UTM parameters solve the same problem with one calendar. They are appended to the end of a booking link and record where the click came from. Google's own documentation covers the five standard parameters and how to build the URLs, along with conventions worth following so your values stay consistent enough to group cleanly.
OnceHub reads these automatically. Per the source tracking documentation, UTM tags added to a general booking link are tracked without any configuration change on your side, and the five standard tag names are reserved so they cannot collide with your custom field names.
The webinar demo runs one booking calendar across three simultaneous campaigns: a QR code at a physical seminar, a LinkedIn thought-leadership post, and a post-webinar follow-up email. Same link, three sets of UTM values, three saved views in the reporting. Every booking carries its source, medium, campaign, and content — so eight meetings from the LinkedIn post are visibly eight meetings from the LinkedIn post, not eight anonymous rows in a monthly total.
The tradeoff worth knowing: UTM parameters are visible in the URL. Anyone can see them, and anyone can edit them. If that matters — competitive campaigns, sensitive client segments — hidden fields offer the same tracking without exposing anything in the address bar. UTMs win on simplicity and built-in reporting; hidden fields win on discretion.
A booking that was made is not a booking that happened. Meeting metrics that stop at "scheduled" miss the entire back half of the story.
Booking Analytics breaks activity down by lifecycle status and lets you retrieve by either creation date or meeting date — a distinction that matters more than it sounds. Retrieving by creation date tells you when demand arrived. Retrieving by meeting date tells you when your team will be busy. Campaign planning needs the first; capacity planning needs the second.
Reassignment deserves its own attention here, because it is both an operational tool and a data signal.
When a host cannot make a booking, there are two options, and they are not equivalent. Rescheduling asks the guest to pick a new time — which, for a lead, is an invitation to disappear. Reassignment keeps the original time and moves the meeting to a different host. The guest keeps their slot and simply meets someone else.
For lead-facing meetings, reassignment is almost always the better move. The webinar makes the point bluntly: if the change is coming from your side, asking a client to rebook is how you lose the meeting. The reassignment interface shows every eligible team member with their availability state — free, busy, or outside working hours — and lets you keep the original meeting location or swap it, which matters when the original host's video conferencing account is attached to the booking.
As a metric, a rising reassignment rate is worth watching. Occasional reassignment is healthy flexibility. A pattern of it usually means workload ceilings are set too high, or availability on the booking calendar does not match how a host actually works.
The analytics and reporting portion of the webinar starts around the 30-minute mark and covers capacity planning, workload adjustment, booking metrics, UTM source tracking, and exports in sequence.
Things to Know About Organizational Booking Operations, with Rami Goraly (Founder & CEO) and Aviram Hinenzon (Chief Go-to-Market Officer).
Want the rest of the session, including the live Q&A with Rami? Watch the full recording or register for our next live webinar to bring your own questions.
Reporting tells you what happened. Notifications tell you it is happening. The webinar frames these as three tiers of intrusiveness, and the framing is useful when deciding who on a team needs to know what.
Lowest — copy to calendar. Booking calendar events are copied into a separate calendar of your choosing, so an office manager can see every client meeting across five advisors on one calendar instead of stacking five and mentally filtering out dentist appointments and lunches. The copied events deliberately omit the guest, so nobody receives notifications from them if the event is moved. Completely passive.
Middle — email alerts. The Alert Center lets you create rules by event type (booking received, scheduled, cancelled) and by user or booking calendar, then nominate who gets notified. The host still receives their standard notification; the alert simply adds recipients.
Highest — optional co-host. You are added to the calendar invite, but your availability is never checked when the guest is choosing a slot, and the event does not block your time. The event appears on your calendar as tentative. Useful when a senior advisor wants the option to drop into a junior's client meeting without constraining when that meeting can be booked.
Pick the lowest tier that gives someone what they need. Alerts routed to everyone tend to stop getting read within a week or two.
|
Question |
KPI |
Where to find it |
|
Can we absorb a campaign? |
Slot-level utilization |
Capacity Planning report |
|
Is one host carrying the team? |
Per-host load vs. ceiling |
Workload settings + booking metrics |
|
Which campaign produced this? |
Booking source |
UTM parameters in Booking Analytics |
|
Are bookings turning into meetings? |
Lifecycle status |
Booking Analytics, by status |
|
When will the team be busy? |
Bookings by meeting date |
Booking Analytics, retrieve by meeting time |
|
When did demand arrive? |
Bookings by creation date |
Booking Analytics, retrieve by creation date |
|
Are we quietly over capacity? |
Reassignment rate |
Activity stream |
Little of this is useful if it lives only inside a scheduling tool. Any table in the reporting views can be exported, and the exports carry the full field set — UTM parameters included, not stripped out. The activity list exports the same way.
That matters for two reasons. Quarterly business reviews rarely run on a scheduling tool's native charts; they run on a spreadsheet someone has cross-referenced against CRM data. And an export is a snapshot you can compare against, which is the only way to tell whether the workload adjustment you made last month actually changed anything.
Slot-level utilization, per-host load against a defined ceiling, booking source, and lifecycle status. Total booking volume belongs on the list only as context — it cannot tell you whether the load is distributed, whether you are near capacity, or where the meetings came from.
Calendar analytics generally describes how time is spent across a calendar, including meetings that never went through a scheduling tool. Booking analytics covers meetings created through your scheduling system specifically — which is narrower, but far more actionable, because those are the ones you can route, cap, and reassign.
Use UTM parameters on a single booking link. Each campaign gets its own set of source, medium, and campaign values, and the booking record stores them. This avoids duplicating a booking calendar — and all its integrations and routing rules — for every campaign you run.
Reassign, in most cases involving a lead or a prospect. Rescheduling asks the guest to commit to a new time, which is where meetings get lost. Reassignment holds the original slot and changes the host, so the guest experiences a much smaller disruption.
There is no published benchmark, and any number quoted as one is worth treating sceptically. What matters is the shape: consistent 100% cells mean you are turning bookings away, and consistent low cells mean you have staffed availability nobody wants. The useful target is a distribution without extremes at either end.
Yes. Every reporting table exports, with UTM fields included, and the activity list exports separately. Most teams pull the export and combine it with CRM data rather than presenting the native views directly.
Booking volume is a number that goes up. Utilization, distribution, source, and lifecycle are numbers that tell you what to do next — hire, extend hours, raise a cap, kill a campaign, or leave things alone.
The reporting to answer all four already exists in most scheduling setups. It is a question of looking at the four instead of the one.
If you'd rather see it live than read about it, watch the full webinar recording, or start a free trial and set up Capacity Planning and Workload Management on your own booking calendars.