ContactBook a call

Industries/ Hospitality/ Booking flows guests finish

Online booking guests finish with one thumb, on the bus home

A guest who gives up at the date picker or the card screen was halfway to booking with you. We find the step where people leave, rebuild it for a phone on top of the reservations system you already run, and measure the difference.

A woman booking a table on her phone while walking along a sunny street lined with restaurant terraces.
Used by
Guests on phones, reservations managers and reception
Takes the place of
Clunky booking widgets and the did-it-go-through phone call
Connects to
Your reservations system, booking engine and card payments
Built with
Our design refresh service

Where it hurts today

A normal week, before it exists

Your reservations widget was designed for a desktop and squeezed onto a phone. The calendar dates are too small for a thumb, the party size sits in a drop-down that opens behind the keyboard, and the guest tries three times in a row before finding one that is actually free. Some get as far as their name and number before being asked to create an account with a password, which is exactly the point where a guest in a hurry closes the tab.

The card step is worse. The deposit appears only on the final screen, the bank's security check opens in a new window that loses the booking behind it, and a guest who goes back to read the cancellation terms finds the table has been released. On a hotel site, the rate on the first screen grows at the last step once breakfast and a resort or booking fee are added, and the guest goes off to compare it somewhere else.

None of this is visible from the office. The reservations system shows the bookings that arrived, not the guests who tried and failed. What you do see is reception taking calls from people asking whether their booking went through, and the same guests booking you through a marketplace page that happened to be easier on a phone. Each of those bookings costs you a commission and, often, the guest's contact details.

What it does

Booking flows guests finish, feature by feature

What changes in the journey, and the evidence that decides which part we change first.

  1. 01

    Booking funnel analysis on real phones

    Before redesigning anything, we record how guests move through each step on phones, with personal details masked, and listen to the booking questions reception gets. That tells us which step loses the most people, so the first fix is the one that matters rather than the one everyone dislikes.

  2. 02

    A date and time picker made for thumbs

    Party size comes first, then a calendar with large dates and fully booked days clearly marked, then only the times genuinely free for that party. If the time they wanted has gone, the nearest alternatives and a waitlist appear straight away. All of it works with a screen reader and a keyboard too.

  3. 03

    Live availability that is true when they tap

    Times come live from your reservations system, never from a copy. Once a guest picks a time, it is held for a few minutes while they enter their details, so the table cannot vanish from under them, and it is released again if they walk away.

  4. 04

    Total price, deposit and terms up front

    Unavoidable fees are in the first price the guest sees. Deposits, card holds for no-shows, the cancellation window and optional extras such as breakfast are explained in plain words before the card screen, not revealed on it, so the guest knows what they are agreeing to before the bank's security check appears.

  5. 05

    Only the guest details you actually use

    Name, phone and email, then the things your team acts on: the occasion, dietary needs, a high chair, step-free seating. No forced account and no password. A guest returning from a link in their confirmation email finds their details already filled in.

  6. 06

    Booking confirmations that answer the phone questions

    The email and text give the time, the address with a map, parking, the dress code, the dog policy and a single link to change or cancel. A calendar file adds the booking to the guest's phone, and a reminder goes out the day before.

A day with it

How the day runs instead

One booking, and the week around it, once the new journey is live.

  1. Monday, 7.15am
    Guest on the train

    Opens the booking page, chooses four people and Friday, and sees that 7.30pm has gone. Taps 7.00pm from the suggestions, notes that it is a birthday and one guest is coeliac, pays the deposit with a phone wallet and has a confirmation before the next stop.

  2. Monday, 10am
    Reservations manager

    Sees the booking in the reservations system exactly like any other, with the birthday and the coeliac note attached. Nothing is retyped and nothing arrives in a separate email. The kitchen will see the dietary note on Friday's list.

  3. Thursday, 6pm
    Guest

    A fifth friend can come after all. The guest taps the change link in the confirmation, the journey checks whether a table for five is free at 7.00pm, updates the deposit and sends a new confirmation. Nobody phones the restaurant.

  4. Friday, 9am
    General manager

    Opens the weekly view of the journey on phones. The date step is no longer where guests leave. The card step on Android now is, more than on iPhone, and that becomes the next thing to fix.

  5. The following week
    Our designer

    Releases the change to the card step behind a switch, on a quiet weekday. We compare the same days before and after, and if the new version does worse, it is switched back the same day and we say so.

What it connects to

Works with what you already run

The new journey is a front on top of your existing systems. Your team keeps working in the same screens they use now.

  • Reservations or table management system

    Live availability, short holds while the guest enters details, and finished bookings with their notes, written straight into your system where it offers an API. If it offers only its own widget, we work within what it allows and tell you where the limits are.

  • Hotel booking engine

    Room types, rates, minimum stays and restrictions read from your booking engine where it offers a booking API, so the price on the first screen is the same price the guest sees on the last.

  • Card payments

    Deposits, card holds for no-shows and refunds run through an established payment provider, with phone wallets and the bank's security check kept inside the journey. Card details are entered into the provider's own fields and held by the provider, not by your systems.

  • Email and text messages

    Confirmations, reminders and change links sent through the messaging your reservations system already uses, or through a separate provider if it cannot carry the details you want guests to have.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Recordings and step-by-step figures showing where phone guests leave today
  • A rebuilt party size, date and time step that works with one hand
  • Total price, deposit and cancellation terms shown before the card screen
  • A confirmation with directions, parking and a single change or cancel link
  • A weekly view of each step, compared with the weeks before the change

Once it is in use

  • A waitlist that texts guests when a table at their time frees up
  • Returning guests recognised from a link, with their details already filled in
  • Group and private dining enquiries with menus chosen in advance
  • Extras at booking, such as a cake or a bottle waiting on the table

Buyer's guide

Before you commission one

Four decisions that shape the work, best made before anyone starts drawing screens.

  1. 01

    Your provider's booking page or a new journey

    Most reservations systems and hotel booking engines come with their own hosted booking page or widget. For a single site with simple tables, set up well and restyled within its limits, that is often the right answer and we will say so. A new journey built on the provider's API earns its place when phone guests leave at a step the widget will not let you change, or when you sell tables, rooms and events together.

  2. 02

    Settle deposits, fees and cancellation terms

    Decide which dates, party sizes and rooms need a deposit or a card hold, when the cancellation window closes and what a no-show is charged. Check which fees are unavoidable, because those belong in the headline price. These are commercial decisions, and the journey cannot be designed until they are made, so write them down in the words you would use on the phone.

  3. 03

    Give the journey one owner

    Booking journeys sit between marketing, who bring guests to the page, and the reservations team, who live with the bookings. Name one person, usually the reservations manager or the general manager, to own the journey, approve changes and read the weekly figures. Without that, each fix waits for a meeting, and nobody notices when a provider update breaks something.

  4. 04

    Choose the signals before you start

    Agree what you will watch before anything changes: how many phone guests who start at the date step reach the confirmation, the step where most of the rest leave, calls to reception asking whether a booking went through, and how many bookings still arrive through marketplaces. Record them for a few weeks first, then compare the same days afterwards.

Terms worth knowing

The words you will meet

Drip pricing
Showing a low price first and adding unavoidable fees as the guest moves through the booking. The UK has banned it since 6 April 2025, and in the US the FTC's fees rule requires hotels to show the total price up front. It matters because the fix lives in the booking journey itself, not in the small print.
Strong customer authentication
The extra check a guest's bank may ask for when they pay online, usually a code or an approval in their banking app. In the UK it comes from the Payment Services Regulations 2017 and has applied since September 2019, and other regions have their own rules. It must sit inside the journey without losing the booking behind it.
PCI DSS
The card industry's data security standard, now in its version 4 series, which applies to businesses that accept card payments. Letting the payment provider's own fields collect card details, rather than your booking page, keeps much of the work with the provider, though the pages around those fields still need looking after.

Handled with care

The details that matter here

A booking journey takes money and promises a table or a room. These are the parts we treat most carefully.

  • Holds and the last table

    We test the hold on a table or room by having two phones race for the last slot, and agree with you how long a hold lasts before it is released. If your reservations system cannot hold a slot, we tell you plainly and design the final step so a clash is caught before payment.

  • Deposits, refunds and card data

    We agree the wording of every charge with you before it is built, and test the bank's security check on real phones, including when it fails halfway. Card details go into the payment provider's own fields, which keeps much of the PCI DSS work with the provider. Refunds and partial charges follow the rules you set.

  • Price display rules by region

    In the UK, the drip pricing ban in force since 6 April 2025 means unavoidable fees, such as booking fees, belong in the headline price. In the US, the FTC's fees rule has required hotels and other short-term lodging to show the total price prominently since 12 May 2025. We design the price display around these rules with your adviser.

  • Changing a live journey safely

    We release changes behind a switch, so the old journey can be brought back the same day if something goes wrong. We avoid releasing anything in the run-up to Valentine's Day, Mother's Day, the festive season or a big ticket release, and we watch the first real bookings closely.

Questions

What buyers ask first

Do we need to change our restaurant booking system?

No. The new journey sits on top of the system you already run, and your team keeps working in the same screens. Bookings arrive exactly where they arrive now. The real question is how much that system lets us change. Where it offers an API we can rebuild the journey properly. Where it offers only its own widget, we improve what it allows and are honest about the rest.

Can we take deposits and no-show fees for online bookings?

Yes, through your reservations system's payment provider or one we connect to it. The journey explains the deposit or card hold before the card screen, the bank's security check stays inside the journey, and refunds follow your cancellation rules. If the evidence shows guests leaving at the deposit screen, we will show you plainly, but the policy stays your decision.

How should hotels and restaurants show the full price online?

By putting every unavoidable fee, such as a booking fee or a mandatory service charge, into the first price the guest sees, and listing optional extras separately. In the UK, that is what the drip pricing ban expects. In the US, the FTC's fees rule covers hotels and other short-term lodging, and some government taxes may be shown separately. We design the display with your adviser.

Can guests still book a table by phone?

Of course. Reception books into the same reservations system, so a phone booking and an online one sit side by side in the diary. The aim is not to stop the phone ringing altogether. It is to stop it ringing about things the journey should have handled, such as whether the booking went through or where to park.

How do we know if a new booking flow is working?

By comparing the same measure before and after, on the same days of the week. We record the journey for a period before changing anything, agree one main number with you, and report it weekly afterwards, alongside the booking calls reception takes. If a change makes things worse, it is switched back and we tell you.

Show us the step where guests give up

Send us the link to your booking page. We will try it on a phone, as your guests do, and reply within 48 hours with what we saw and what we would fix first.