Home › Foundation Check
Usually friction in the booking process itself — too many required fields, unclear availability, an account creation requirement, or uncertainty about what happens after booking (confirmation, what to expect, cancellation policy) all cause hesitation at the exact moment someone was ready to commit.
Abandoning a booking partway through is different from never starting one — this is someone who was ready to take action and then, partway through, decided not to. That moment of hesitation is valuable information: something in the process itself introduced doubt or friction that wasn't there before they started.
Common causes: requiring account creation before booking (an extra step that feels disproportionate for a simple appointment), asking for information that doesn't seem necessary for booking (and raises questions about why it's needed), unclear or limited availability that makes someone feel like they're not getting a real choice, and — perhaps most commonly — no indication of what happens after booking. Will they get a confirmation? Can they reschedule if needed? What's the cancellation policy? Uncertainty about these things, surfacing mid-process, can cause someone to step back and think "let me call instead" — and then not follow through on that either.
The fix is usually reducing friction (fewer required fields, no forced account creation) and adding reassurance (clear confirmation process, easy-to-find cancellation policy) — both of which are about removing reasons to hesitate at the exact moment someone was ready to commit.
Want to know where your own foundation stands?
See a sample evaluation →If you use a booking platform, it may have analytics showing started-but-not-completed bookings — if not, a foundation evaluation looks at the booking flow itself for friction points regardless of analytics availability.
For some businesses (recurring services, memberships) an account makes sense — the issue is requiring it as a barrier before a first-time booking, when a guest checkout option would reduce friction.
Even within platform constraints, the surrounding page — what's communicated before and around the booking widget — can address reassurance gaps (confirmation process, cancellation policy) even if the booking form itself is fixed.