A Better Way to Book Meetings on Behalf of Busy Senior Teams

16 Aug 2026 · by Peter Grillet

If you book meetings for senior people, the hard part is not just finding an open slot. This post explains how assistants and coordinators can reduce calendar chasing by standardising meeting types, required attendees, booking forms, and team links without removing control from the people being booked.

A Better Way to Book Meetings on Behalf of Busy Senior Teams

If you book meetings on behalf of busy senior people, you know the awkward truth: the calendar is rarely the only problem.

The client needs a meeting. The director, founder, partner, producer, strategist, or account lead needs to attend. Someone else on the team may also need to be there. The meeting might need to be in person, on Microsoft Teams, on Google, or over the phone. The client may need to give you enough context before anyone joins the call.

From the outside, this looks like a simple scheduling task. Inside the business, it is a small routing job every time.

That is why booking meetings for senior teams can quietly take over the day. You are not just asking, "What time works?" You are deciding who should attend, which link is safe to send, whether the meeting needs prep, how much notice the team needs, and what happens if the client moves it.

A better process does not remove your judgement. It removes the repeated chasing around the parts that are predictable.

Why booking on behalf of others gets messy

Most scheduling tools are built around one person sharing their own availability. That works when the person sending the link is also the person attending the meeting.

That is not how a lot of client-facing teams work.

An assistant may book a client review for a director. A client services coordinator may need a strategist and account manager on the same call. A production coordinator may need a producer, client lead, and external stakeholder to agree a slot. A sales coordinator may need to book a prospect with the founder and a specialist.

When the real meeting depends on several internal decisions, a personal booking link only solves one slice of the problem. It lets the client choose a time with one person. It does not decide whether the right people are available, whether the booking page has the right instructions, whether the meeting should ask for context, or whether the link being sent is still current.

That is why teams end up with workarounds: shared documents full of links, old email templates, Slack messages asking for availability, calendar holds, and one coordinator holding the whole thing together from memory.

Start by separating the meeting types

The first thing to fix is not the software. It is the shape of the meetings.

Busy senior teams often get into trouble because different meetings are treated as if they are the same. A quick intro call, client review, project kickoff, proposal follow-up, production approval, handover, and advisory call may all end up being booked through the same link or arranged manually every time.

That gives you too many decisions to make on the fly.

A more useful starting point is to list the meetings you arrange most often and define the rules for each one:

Who normally needs to attend?
How long should the meeting be?
Does it need a buffer before or after?
Can the client choose phone, video, or in person?
What information should be collected before the meeting?
How much notice does the team need?
Is this a reusable booking page or a one-off invite?

This is where the admin load starts to drop. You are no longer rebuilding the decision from scratch for every client. You are choosing the right meeting type and letting the rules do some of the repetitive work.

Decide when senior people really need to attend

One of the most useful parts of this exercise is deciding when senior attendance is actually required.

Senior people often get pulled into meetings because nobody wants to make the call on whether they are needed. That creates two problems. Their calendar gets filled with meetings that could have been handled elsewhere, and genuinely important meetings become harder to book because the best slots are already gone.

For each meeting type, set a simple attendance rule. For example:

A discovery call goes to the client lead unless the prospect is strategic or referred by a senior contact.
A project kickoff needs the producer and account manager, but not always the director.
A proposal review needs a senior person only when pricing, risk, or scope needs approval.
A handover needs both outgoing and incoming owners when relationship context matters.

The point is not to block access to senior people. The point is to make their involvement intentional. Once the rule is clear, the person arranging the meeting has much less hidden judgement to carry.

Use shared team event types instead of everyone making their own version

In many teams, booking pages drift because every person creates their own version.

One director's client review is 45 minutes. Another person's is 30. One page asks useful prep questions. Another only asks for name and email. One booking page allows same-day meetings. Another requires two days' notice. None of this is usually malicious. People are busy, they create what they need in the moment, and the team ends up with ten slightly different versions of the same meeting.

For an assistant or coordinator, that creates avoidable friction. You have to remember which link is best, which one is outdated, and which person forgot to update the instructions.

With team event types and team management in calendr.so, one person can create the meeting details and template for the team. The shared parts stay consistent: the name, duration, description, questions, location options, booking window, and fallback behaviour. Team members still control their own availability, so the process does not force meetings into times that do not work for them.

That is the balance most teams need. Central control over the client-facing setup, individual control over the calendar.

Use multi-host booking for meetings that need several internal people

Multi-person meetings are where manual scheduling gets especially painful.

If a client needs to meet a founder and account manager, or a producer and strategist, sending one person's booking link only gets you halfway there. The client books a time, then someone checks the second calendar, then the meeting has to be moved, or someone important is missing.

That is the kind of coordination that makes a team look less organised than it is.

With multi-host booking, you can create a booking page that checks the required internal attendees before showing availability to the client. The client sees the times that work for the people who actually need to be there.

This is worth using for meetings where internal attendance matters to the quality of the conversation: client kickoffs, major reviews, handovers, proposal calls, approvals, or anything where the meeting would be weaker if one person did not attend.

Use it deliberately. Not every meeting needs three internal people. But when it does, the booking flow should reflect that from the start.

Collect the context before the meeting lands in the calendar

Another reason coordinators end up in the middle is that the booking itself does not capture enough information.

The calendar invite says "Client call". The senior person asks what it is about. The account manager is not sure whether it is a review, issue, approval, or new opportunity. Someone has to go back to the client or dig through previous messages before the meeting can be prepared properly.

Booking forms help when the meeting needs context before it is accepted as a useful appointment. For a client-facing team, useful questions might include:

Which company or project is this about?
What would you like to cover on the call?
Is there a deadline we should know about?
Who else should attend from your side?
Do you want to meet by phone, video, or in person?

The goal is not to interrogate the client. The goal is to stop the internal team from joining cold or interrupting you later to ask what the meeting is for.

Make the right links easy to find

Even a well-designed booking process breaks if nobody can find the right link.

This is especially common in teams where people book meetings on behalf of others. Links end up in documents, saved replies, old emails, Notion pages, CRM notes, or messages from six months ago. Someone copies the link that worked last time, even though the meeting type has changed or the person no longer handles that call.

Calendr gives teams colleague search and an "Everyone's event types" view so you can quickly find the right person or meeting type and copy the current link. That matters because the best booking setup in the world is not much use if the team still relies on link archaeology.

For assistants and coordinators, this is one of the most practical improvements. You can send the client's next step without asking the senior person to resend their link, checking three documents, or guessing which version is correct.

Searching for a type of booking page to get everyone's links

Plan for links to outlive the person who sent them

Booking links do not stay neatly contained.

They get added to proposal follow-ups, project templates, client onboarding messages, email signatures, saved replies, and old threads. That is useful until someone changes role, leaves the business, or stops handling that type of meeting.

If the old link still exists in a template, the client should not hit a dead end or land with the wrong person. The coordinator should not have to remember every place that link might have been used.

Fallback options in calendr.so help when a team event type points to a colleague who is no longer available. Depending on your settings, the booking flow can offer alternative host options instead of breaking the client journey.

This is a quiet but important feature for teams that rely on templates. It accepts reality: links travel, teams change, and the booking process needs some resilience built in.

A simple version to set up first

If you want to test this without making it a big project, start with one recurring meeting type that currently creates the most chasing.

For many teams, that will be a client review, kickoff call, proposal follow-up, or handover. Pick the one where you regularly have to check several calendars, ask for missing context, or repair the meeting after the first invite goes out.

Then set up the minimum useful version:

Create the meeting type with the correct duration and client-facing instructions.
Decide who must attend and whether it needs multi-host availability.
Add the prep questions the team usually asks you after the booking.
Set the availability window and buffers so the meeting is not booked at unworkable times.
Save the current link somewhere the team can find it, or use colleague and event type search when sharing it.
Update one template or outbound message so the client receives the cleaner booking route.

That is enough to prove the value. You do not need to rebuild the whole company calendar process on day one. You need one meeting that used to create avoidable admin to become easier to book, easier to prepare for, and easier for the client to move if needed.

Where calendr.so fits

calendr.so is useful here because it is designed for teams, not just individuals sending their own link.

For assistants, admin coordinators, client services teams, and busy senior teams, that means you can create consistent event types, support multi-host meetings, collect context with forms, let clients choose suitable meeting locations, find colleague links quickly, and reduce the risk of old links sending people to the wrong place.

The better way to book on behalf of senior people is not to remove the human judgement from scheduling. It is to stop spending that judgement on the same repeated admin decisions every day.

Once the repeatable parts are captured in the booking page, you can focus on the part that actually needs you: choosing the right route for the client and protecting the team's time.

Start with one team workflow

Make senior-team meetings easier to book

Use calendr.so to create consistent booking pages, find the right team links quickly, collect meeting context in advance, and let clients book with the right people without another email chain.

Start a free trial

Making meeting management easier for Executive Assistants

#Executive assistants #Admin coordinators #team scheduling #Client meetings #Multi-host booking