Appointment Booking Best Practices I Use to Keep Client Projects Moving

18 Aug 2026 · by Hattie Smithson

When client projects depend on milestone meetings, specialist input, and busy calendars, appointment booking can quietly take over the day. Hattie Smithson shares the booking practices she uses at Islington Partners to keep meetings labelled, links easy to find, specialists involved, and project stages moving.

Appointment Booking Best Practices I Use to Keep Client Projects Moving

I am Hattie Smithson, and I work as Practice and Communications Officer at Islington Partners, which owns calendr.so.

That title sounds tidy. The actual work is a mix of communications, coordination, project admin, and quite a lot of executive-assistant-style diary wrangling. If a client project needs the right people in the right meeting at the right stage, there is a good chance I have been somewhere in the background trying to make that happen without turning it into a 14-email saga.

For a while, that was giving "tiny admin task, somehow my whole afternoon". A client needed to speak to the person leading the project, plus a specialist. I would check one diary, message someone else, suggest a time, wait for the client, realise the first person was no longer free, then start again with slightly thinner patience.

That is one of the reasons calendr.so ended up being shaped around real small-business scheduling problems. I did not need an enormous scheduling system. I needed web based booking software that made it calmer to book client meetings across a busy team, especially when the meeting was tied to a project stage or milestone.

1. Put booking links inside the project workflow

The first appointment booking best practice I would recommend is simple: do not keep important booking links in someone's head, inbox, or private notes app.

In the past, when a project reached a certain stage, I would have to work out which meeting needed to happen next and who should attend. That might be a workshop, a training session, a client check-in, an implementation discussion, or a specialist call. If the link was buried in an old message, I had to go hunting. If the meeting needed two internal people, I had to coordinate it manually.

Now, the relevant booking links can be saved at the right stages in the workflow. When the project reaches that point, the next meeting is not a fresh decision. The team already knows which booking page to send.

That is especially useful when projects are billed by milestone. If a meeting type is clearly labelled, it is easier to see where the project has reached and what needs to happen next. The calendar is not just a diary. It becomes a little trail of project progress.

2. Name meeting types like a normal person will read them later

Hattie's original appointment booking links

This sounds obvious, but it is strangely easy to get wrong.

If your booking pages have vague names like "30-minute meeting" or "Client call", they are not very helpful once they appear in the calendar. They might be fine for the person who created the link, but they do not help the rest of the team understand what the meeting is for.

I prefer meeting types that tell you the stage, purpose, or owner. For example:

Client implementation workshop.
Data review call.
Training session with client team.
Project milestone check-in.
Specialist consultation.

The wording does not need to be fancy. It needs to be useful. If someone looks at their calendar on Monday morning, they should understand what is coming up and what they need to prepare.

3. Use multi-host booking when a specialist needs to be there

A lot of our meetings are not one person speaking to one client.

If it is an implementation or consulting project, the person leading the project may need to bring in a data person, trainer, consultant, or another specialist. That used to be the bit where scheduling became messy. I could not just send the project lead's link, because the client might book a time the specialist could not do. I could not just send the specialist's availability, because the project lead also needed to be there.

Multi-host booking solves that specific problem. The client only sees times that work for the required internal people. From my side, that removes the part where I act as the human calendar comparison tool.

It also makes the client experience better. They do not need to know how many internal diaries had to line up. They just choose from the times that are actually possible.

4. Make team links easy to find

Another small-business scheduling problem is link storage. It is not glamorous, but it matters.

If your booking links live in a spreadsheet, a shared document, three Slack messages, and someone's memory, people will eventually send the wrong one. The link may still work, but it might have the wrong meeting length, the wrong host, the wrong questions, or an old version of the meeting instructions.

In calendr.so, being able to search colleagues and event types is genuinely useful. The team setup in calendr.so's team management features means that if I need to send a client to the right person, or find the right meeting type for a particular project stage, I can quickly surface the link and copy it into the client email or project message.

That is the sort of feature that sounds small until you have spent half an hour trying to find the current version of a link someone swears they sent you last month.

5. Use forms to collect context before the meeting

A meeting is much better when the team knows why it has been booked.

For some client meetings, a simple booking page is enough. The client just needs to pick a time. But for workshops, specialist sessions, or project check-ins, it helps to collect a little context before the calendar invite lands.

Booking forms can ask for the project name, the reason for the meeting, the current blocker, the client's preferred meeting format, or anything the host needs before joining. I would keep this light. Nobody wants to fill in a novel before booking a call.

The point is to help the internal team arrive prepared. If the trainer knows the client's question before the session, or the data person knows which report they are reviewing, the meeting starts in a much better place.

6. Connect bookings to the calendar people actually use

This is where Google Calendar integration matters for us.

When a client books, the meeting appears where the team is already looking: on their desktop, on their phone, and in the calendar they use to plan the day. That visibility is important because the booking page should not create a second place people have to remember to check.

It also helps prevent double-booking. If someone's actual calendar availability is respected, I do not need to manually check whether the time is still safe. The whole point of using a booking system is that it should reduce the number of diary checks, not create another admin layer.

7. Keep the setup small enough that people will actually use it

My honest view is that most small businesses do not need complexity first.

They need a clear booking page for the meetings that happen all the time. They need those meeting types labelled properly. They need client context captured where it helps. They need a clean way to bring specialists into meetings. They need calendar integration that people trust. And they need the links somewhere the team can actually find them.

That is why appointment scheduling software for small business should not feel like a huge implementation project. It should take the scheduling work your team already understands and make the repeatable parts easier.

If I were setting this up from scratch, I would start with one project workflow and identify the three meetings that cause the most back-and-forth. Then I would create properly named booking pages for those meetings, decide which ones need multiple hosts, add one or two useful form questions, and save the links directly in the workflow stage where they belong.

The best booking system is the one your team trusts

I do not think small teams need scheduling software because they are bad at organising themselves. Usually, the opposite is true. They are keeping a lot moving with a lot of informal knowledge.

The issue is that informal knowledge does not scale very well. It lives in people's heads, inboxes, and habits. When projects grow, clients reschedule, specialists get involved, or milestone meetings start to matter commercially, the business needs a more reliable way to move from "we need a meeting" to "the right people are booked".

For me, good appointment booking is not about making things feel automated for the sake of it. It is about making client meetings easier to arrange, easier to understand, and easier to trust once they appear in the calendar.

Start with one client workflow

Make client meeting booking easier to manage

Use calendr.so to create consistent booking pages, find the right team member's link quickly, coordinate multi-host meetings, collect useful context, and connect bookings to Google or Microsoft calendars.

Start a free trial

Growing Small Businesses Making meeting management easier for Executive Assistants

#Client meetings #Multi-host booking #Appointment booking best practices #Small business scheduling #Google Calendar integration