Bookings arrive on their own. What you do afterwards is the part that decides whether a booking page is worth having.
What arrives with each one
Who booked, their organisation, their email and phone if you asked for it, anything they wrote, and the answers to your context questions.
Plus where it came from. A booking made through a WhatsApp conversation is marked as such; one from the website is marked web. That origin is worth reading, because somebody who has already had a conversation with you arrives at a different point from somebody who found a link.
Marking takes seconds
The entire discipline is two clicks per booking, and everything downstream depends on it.
Do it immediately after the meeting rather than in a weekly sweep. A booking marked while you still remember the conversation is accurate; one marked five days later is a guess, and a list of guesses is not worth keeping.
Four states
| State | Means |
|---|---|
| Confirmed | Booked and expected |
| Completed | It happened |
| Cancelled | Called off |
| No show | Nobody came |
Marking them is the whole discipline of this surface, and it takes seconds.
Why marking them matters
An unmarked booking is a meeting that may or may not have happened, and a list of those is worthless.
Completed is what makes your booking page measurable. Bookings taken is a vanity number; meetings held is the real one, and the gap between them is the thing worth managing.
No show is the number that tells you whether your process is working. A rising no-show rate is almost never about the people booking, it is about how far ahead they booked, whether they were reminded, or whether the meeting was worth their time.
What completed actually means
The meeting happened. Not that it went well, not that it converted.
Keeping that definition narrow is what makes the number useful. A team that marks only successful meetings as completed has a held-rate that measures optimism rather than attendance, and the no-show number it produces is worthless.
Handling a no-show
Assume it was an accident, because it usually was.
Follow up the same day, briefly, offering to rebook. Same day matters: after twenty-four hours the reply rate falls sharply.
Send the link rather than proposing times. They already showed willingness to use it.
Once, not three times. Somebody who does not respond to one warm follow-up is telling you something.
Look for the pattern before blaming the person. If no-shows cluster on bookings made more than a fortnight ahead, the problem is how far ahead you allow booking, not the individuals.
Reducing no-shows
Four things, in order of effect.
Shorten the booking horizon. A meeting booked three weeks out is a meeting somebody's circumstances will have changed before.
Confirm automatically. A visitor left waiting for acceptance is half-committed at best.
Ask why they are coming. Somebody who selected a topic has invested something and is measurably more likely to attend.
Make the meeting sound worth it. The description is doing more work than it appears to.
The origin is worth reading
Every booking records where it came from: a link, the website, a WhatsApp conversation, web chat.
Somebody who booked after a conversation arrives warm and part-informed. Somebody who found a link cold arrives with whatever your description told them. Treating those two identically wastes the advantage of the first and under-serves the second.
It takes two seconds to look and it changes how the first minute of the call should go.
Cancellations
A cancellation is a better outcome than a no-show, and it should be easy.
Somebody who cancels has given you back the hour and told you the truth. Treating cancellation as failure produces no-shows instead, which cost you the hour as well as the information.
Recording the meeting
A booking is a calendar event, so the recorder can be sent to it like any other meeting.
Worth doing for first conversations in particular. A discovery call where somebody explains their situation for twenty minutes is the single most useful recording your organisation can hold about that account, and the summary is the fastest way to hand it over.
What is not built yet
Insights is one of the sections showing a "coming next" panel. Booking volume, conversion and no-show analytics are planned rather than present.
Until then, bookings appear on your calendar under the Bookings source, and the Workspace reports include meetings by source, which is a partial view of the same question.
Rescheduling
A visitor who needs a different time cancels and rebooks, and both actions are theirs.
That is worth knowing so you answer confidently when somebody emails asking to move: send them the link rather than proposing times. It is faster for both of you and it keeps the booking in the system rather than turning into a calendar entry you made by hand.
Where you need to move it, cancel and tell them why. A booking that silently disappears from somebody's calendar is a bad experience even when the reason was good.
Preparing for one
Two minutes before the call, in this order.
Read the context answers. What they picked, and whether they can decide.
Look at the record. A returning customer has history; a new one has whatever the origin tells you.
Decide the one outcome you want. A first conversation with a defined outcome is a different meeting from one where you are both finding out.
Most of the value of the context step is realised here, before anybody speaks, and none of it is realised if the first time you read the answers is while they are already talking.
A weekly habit
Five minutes.
Mark last week's bookings completed or no-show. Nothing downstream works without this.
Follow up any no-shows that have not been chased.
Look at the ratio. Held against booked. If it is falling, look at the horizon and the reminders before anything else.
That is the entire routine. The value of a booking page is not in taking bookings, which happens by itself, but in the small amount of attention that turns them into meetings that actually occur.
Did this answer your question?
No, ask a person