Booking abandonment: where guests give up

Every restaurant with online booking loses some guests partway through. They open the booking page, look at the dates, perhaps pick a time, and then leave without booking. Some come back later or phone instead. Many book somewhere else. Booking abandonment is the name for that loss, and it is one of the least visible costs a venue has, because the guests who give up leave no trace except an empty table.

The good news is that abandonment is not random. It happens at a few predictable points in the booking flow, for a few predictable reasons, and most of those reasons can be fixed without spending anything. A venue that finds where its guests give up, and removes the friction there, often gains more bookings than any marketing campaign would bring.

This guide walks through the four screens where most guests abandon a booking, in the order they meet them: the first load, the availability screen, the details form and the final step. For each, it explains why guests leave and what to test. Every figure in it is an example.

A booking is abandoned when a guest starts the booking flow and does not finish it. It is the opposite side of booking conversion: if 1,000 guests open the booking page in a month and 300 complete a booking, the conversion is 30 per cent, and 70 per cent of visits ended without one.

Not all of those are losses you can win back. Some guests were only checking availability, some were comparing venues, some opened the page by accident. But a share of them wanted to book and were stopped by something on the page. That share is what this guide is about. Our guide to booking conversion from page view to confirmed covers measuring the overall rate.

It helps to think of the booking flow as a funnel, with fewer guests at each step than the one before. The idea is standard in online selling, summarised in Wikipedia's article on the conversion funnel. For a restaurant booking, the steps are usually:

Some guests leave at every step. The question is where the biggest drops are, because that is where a change makes the most difference.

The first place guests give up is before they see anything useful at all. The page is slow to load, or the guest lands somewhere other than the booking form: a home page, a menu, a page of links. Many guests arrive from Instagram or Google on a phone, often on mobile data, and they will not wait long.

What to look at:

What to test next week: tap every booking link you control, from a phone, and time how long it takes to see the date and time choices. If it is more than a few seconds, or if any link lands somewhere other than the booking form, fix that first. Our guides to mobile booking, booking from Google and bookings from Instagram cover each route in detail.

The second big drop happens when guests look for a time and do not find one they want. Sometimes the venue really is full. Often, though, it has availability that the page fails to show clearly: the preferred time is taken and the page shows nothing else, the times are hard to read on a phone, or the guest cannot see beyond the next few days.

What to look at:

What to test next week: try to book your busiest night for a party of four, at the time most people want. If the page does not offer you a nearby time or a waitlist, that is where guests are giving up. Then look at your booking rules: the lead time, the maximum party size and the booking times you offer online. A rule set long ago for a different trade can quietly hide tables guests would happily book.

Once a guest has chosen a time, they have to fill in their details. On a phone, typing is slow, and every field is another reason to stop. Long forms are one of the most common causes of booking abandonment, and one of the easiest to fix.

What to look at:

What to test next week: fill in the form on a phone, one-handed, and count the taps. Then look at every field and ask whether you need it to hold the table and contact the guest. Our guide to booking form fields goes through which to keep and which to delete.

The last screen can lose guests who were nearly there. The usual causes are a request for card details, a box of terms and consents that is hard to understand, or being asked to create an account or a password.

Card details are the biggest of these. Asking for a card number at booking, to take a deposit or hold a card against no-shows, protects the venue and can lose bookings, especially from new guests on a phone. Our guide to reservation deposits covers when they are worth it. If you do ask, explain why before the card form appears, and ask only where it matters, such as large groups and the busiest nights.

What to test next week: complete a booking all the way to the confirmation on a phone. Note anything on the last screen that made you hesitate: an unclear tick box, a surprise request, a button that does not say what it does. Each hesitation is a share of guests lost.

A booking that is made but not clearly confirmed can still be lost. A guest who is not sure whether the booking went through may book again elsewhere, or simply not turn up. The confirmation screen should say plainly that the table is booked, for how many, when and where, and a confirmation email should follow immediately.

Check that the confirmation email arrives within a minute or two, looks like your venue, and does not land in spam. A missing or late confirmation is a quiet cause of no-shows that looks, from the venue's side, like a guest who did not care.

Some booking systems hold a table for a few minutes while the guest finishes booking, so that two guests cannot book the same table at once. That is sensible, but a hold that is too short can expire while a guest on a phone is still typing, and the booking then fails at the last moment.

If your system has a time limit to finish booking, set it long enough for a guest typing on a phone, with a clear message if it runs out, and an easy way to start again with the same choices.

Groups abandon bookings in a particular way. A guest trying to book for nine, on a page whose online maximum is eight, reaches the party size screen and finds no way forward. If the page says nothing more, that guest leaves, and a large booking is lost at the very first step.

Set the online maximum deliberately, and above it, tell guests what to do instead: call, email or write to the venue, with the details right there on the page. A group that is shown a clear next step usually takes it. One that meets a silent limit assumes the venue does not want large parties.

Regulars meet the same four screens every time they book, and they notice friction more, not less, because they know they will come anyway. A regular who has to type their full details on every visit, or verify their email again and again, may start phoning instead, which costs the venue staff time.

Where your booking system can recognise returning guests, or remember details on the guest's own device, it makes the regulars' bookings quicker. Where it cannot, keep the form short enough that typing it again is no great burden.

Guests arriving from different places abandon at different rates. Those who searched for your name on Google are usually close to booking; those who tapped through from a friend's Instagram story are often just curious. Comparing abandonment across channels tells you whether a problem is the booking page itself or the guests a channel sends.

If you tag the booking links you share, by channel, and your website analytics can read the tags, you can compare how many visits from each channel become bookings. A channel with many visits and few bookings is either sending the wrong guests or sending them to the wrong place.

You do not need sophisticated analytics to find where guests leave. Start with what you can see: visits to the booking page, if your website analytics show them, and completed bookings. Then test the flow yourself, on a phone, and watch a few other people try it.

If you can measure each step, look for the largest drop between two steps. If you cannot, the tests above usually reveal the main problem quickly. A venue whose own team gives up booking on a phone has found its answer.

The most useful test is to watch someone who has never used your booking page try to book, without help. Ask a friend, a new member of staff or a regular to book a table on their own phone while you watch. Do not explain anything.

Note every pause, every wrong tap, every question they ask. Those moments are where real guests give up, and most of them are fixable in an afternoon: a clearer label, a missing alternative time, a field that can be deleted.

Guests who book through a booking widget embedded in your website meet the same four screens, inside a page you designed for something else. A widget squeezed into a narrow column, a page that loads slowly around it, or a widget that opens in a small scrolling box all add to abandonment.

Test the booking widget on a phone as well as a laptop. If it is awkward, try linking to the full booking page instead of embedding it, and compare how many bookings each produces. Our guide to the booking widget and the four taps that lose a guest covers the widget in more detail.

Some fixes for abandonment cause new problems. Avoid these:

The aim is a flow with no unnecessary friction, not one with no rules at all.

An invented restaurant notices that its online bookings have fallen while calls asking for tables have risen. Testing its own booking page on a phone, the manager finds three problems. The link from the Google profile goes to the website home page, where the booking button is below the photos. On busy evenings, a full time shows an empty screen with no alternatives. And the form asks for title, full address and how the guest heard about the restaurant.

The restaurant points the Google link straight at the booking page, shows nearby times when the chosen one is full, and cuts the form to name, email, phone and notes. Over the following month, by its own count of visits and bookings, noticeably more visits end in a booking, and the phone rings less with guests who gave up online. No new marketing was needed; the guests were already arriving.

servearound gives each venue a booking page built for phones: party size, a strip of dates, available times as buttons, a form for first and last name, phone and email, a six-digit code that confirms the guest's email before the booking is made, and a confirmation by email. The email code is a deliberate step: it stops fake and mistyped bookings, and it is worth watching as one of the screens in your own tests. When a night is full, a waitlist can catch guests, and the same booking flow can be embedded as a widget on your own site. See the reservations module.

The booking rules are in your hands: whether online booking is open, the maximum party size, the notice you need, how long a guest has to finish booking, and reminders. Analytics shows bookings by source, such as the booking page, the widget on your website, phone and walk-in, so you can see how much trade arrives online. servearound does not show where in the flow guests drop out, so the testing in this guide is how to find it. servearound does not take deposits or card details at booking today. See Analytics.

It is when a guest starts an online booking and leaves without finishing it. It is the other side of booking conversion.

At four points: the first load, the availability screen, the details form and the final step, especially if it asks for card details or an account.

Test the booking flow yourself on a phone, watch a few people who do not know it try to book, and compare booking page visits with completed bookings.

They can, especially for new guests on a phone. Ask for them only where they matter, such as large groups and peak nights, and explain why before the card form.

Only what you need to hold the table and contact the guest: name, an email or phone number, and an optional notes field.

Show nearby times before and after, other days if the evening is full, and a waitlist if you run one. An empty screen loses guests.

Not necessarily, but test it on a phone. If it is cramped or slow inside your site, a link to the full booking page may convert better.

Every few months, and after any change to your website, booking system or booking rules.

Rarely worth it online; guests who leave do not answer surveys. Ask the guests who phone instead, because many of them tried the booking page first, and they can tell you exactly where they gave up.

It adds a step, so it can, a little. It also prevents fake and mistyped bookings, which cost tables and reminders. If your system verifies email, make sure the code arrives within seconds and that the screen explains why it is asked for.

Yes. A lead time, party size limit or set of booking times that is stricter than it needs to be hides tables guests would book.

Booking abandonment is the guests who start an online booking and leave. It happens at four predictable screens: the first load, where slow pages and wrong links lose guests; availability, where empty screens and hidden tables do; the details form, where every extra field costs bookings; and the final step, where card details, unclear consents and account creation stop guests who were nearly there.

Test each screen on a phone, one-handed, and watch people who have never seen your booking page try to use it. Fix the links, show alternative times and a waitlist, cut the form to what you need, ask for card details only where it matters, and make sure the confirmation arrives. Most abandoned bookings are lost to small frictions that cost nothing to remove.