Why Public Booking Pages Don't Work for Experts

Who is a public booking page actually designed for?

Someone with no prior relationship to you. Every design decision follows from that assumption: the link is open, the form starts empty, the questions are the ones you would ask anybody, and the confirmation explains what happens next.

For a first booking this is right. You genuinely do not know who they are, and the form is how you find out.

Why does that misfit most expert bookings?

Because most expert bookings are not first bookings. David A. Fields puts healthy repeat business at 40 to 80 percent of a consulting firm's revenue, and treats anything below 40 percent as a problem to fix (David A. Fields Consulting Group).

So the majority of the bookings a working practice takes come from people it already knows well, and every one of them runs through a flow designed on the assumption that it knows nothing about them.

The client absorbs this quietly. They retype their name, restate their reason, and pick from slots chosen without reference to the cadence they have kept for a year.

What happens to what the client tells you?

It goes to the event. Calendly allows up to 10 custom questions per event type, and after someone books, their answers are saved under the Calendar page and included in notifications by default (Calendly Help). Retrieving them later means exporting the meeting details from that page.

Calendly's documentation describes retrieval by meeting and by export. It does not describe a view of one person's answers across their bookings.

That matters because the booking form is the single moment a client volunteers context without being asked twice. They are telling you what they want from the session, unprompted, in writing. Filing that by event puts it in the same place as the room link and the start time.

Can you not just pre-fill the link?

You can, and it is worth knowing exactly how far it goes. Calendly supports pre-filling a booking link with name, email and answers to questions before the invitee lands on the page (Calendly Help).

The mechanism is a URL you build yourself: copy the event link, add a question mark, then append each field as a variable joined by ampersands. Calendly does not recognise a returning invitee and populate this on its own.

So the capability is real and the operation is manual. You are maintaining a personalised link per client, by hand, which is a workaround you run rather than a system that remembers.

What would a booking page that knew the client do?

Less, mostly. The value is in what it stops asking:

• Skip the intake. It already knows who they are and how to reach them.
• Show what is outstanding from last time, so the booking starts from the commitment rather than from a blank field.
• Offer the cadence they actually keep instead of every open slot in the calendar.
• Attach whatever they write to the client's record, where the next session will open it.

Erik Altmann and J. Gregory Trafton found that cues available before an interruption improve performance after it, attributing the effect to people deploying "preparatory perceptual and memory processes" to mitigate the disruption (Altmann and Trafton, Cognitive Science Society). A booking form that carries the last session forward is that cue, arriving at the one moment both people are already thinking about the work.

There is a second cost that shows up later. Umit Gurun, Noah Stoffman and Scott Yonker found that roughly 40 percent of client assets follow a financial adviser who moves to a different firm (Journal of Financial Economics 141(3)). When the knowledge of a relationship sits with a person rather than in a record, the relationship travels with them.

Frequently Asked Questions

Are public booking pages bad for professional practices?

They are well suited to first contact and poorly suited to repeat work. The page assumes no prior relationship, which is accurate once per client and inaccurate every time after. The question worth asking is what share of your bookings are first bookings.

Where do Calendly booking form answers go?

Calendly saves invitee answers under the Calendar page and includes them in notifications by default, and they can be retrieved by exporting the meeting details (Calendly Help). The documentation describes retrieval per meeting rather than a view of one person's answers across their bookings.

Can a booking link remember a returning client?

Only if you build the link. Calendly supports pre-filling name, email and answers through URL parameters that the host constructs by hand (Calendly Help). It does not detect a returning invitee automatically, so the memory is yours to maintain per client.

Does a private scheduling tool solve this?

Privacy and access control are a separate question from memory. A private link restricts who can book. It does not, on its own, make the booking write to a record of the person booking, which is the part that decides whether session nine opens with session eight in front of you.

Airtym keeps booking, the video room, payment and the session summary on one running record per client, so the next conversation opens with the last one already in front of you.

Related Articles

• How to Manage Client Bookings Without Email Threads — the booking link ends the back-and-forth and the accumulating record in the same move.
• When the Meeting Link Stops Being the Trust Signal — presentation wins the first call and expires; continuity replaces it.
• Meeting Notes Apps for Client Calls: Two Questions Before You Pick One — per-client grouping exists in every major notetaker; what decides it is who does the filing, and what none of them hold.