Nobody rings a venue to say the Continue button on the booking page was greyed out. They close the tab. Maybe they book somewhere else, maybe they try again on a laptop that evening, and either way nothing in your diary shows they were ever there.
That has bothered me for a while, because the problems that cost you bookings are exactly the ones nobody reports. So this week we went looking. We went through 312 recorded visits to venues' booking pages, one visit at a time, and fixed what turned up. All of it was small. None of it would normally get a blog post, which is partly why I wanted to write one.
How we went through them
Since 10 November, booking pages can record how a visit goes: the screens a guest saw, what they tapped, how far they scrolled, where they gave up. Two days of that gave us 8,401 visits across 150 venues, far more than anyone could sit and watch. So the first job was sorting. Each recording becomes a timeline you can read like a till receipt ("0:16 pressed Continue", "0:19 pressed Continue"), which is how we got through 312 of them and picked out the ones worth a proper look. We studied those with the guest's screen in front of us at the moment things went wrong, and pulled 203 stills along the way. Nothing was changed on the strength of a timeline alone. Every fault was checked against the live data or reproduced on a test venue first.
The 312 came from 59 venues, and we were deliberate about which ones. Some were guests who booked with no trouble at all. Some hung around for a while and left without booking. The rest were whatever came up, unfiltered. It's tempting to skip the first group, but read only the visits that went wrong and every page looks broken. You need the boring successful ones to see what the stuck guests were missing.
Small percentages, real people
I want to be straight about the scale, because a list of faults makes a product sound like it's on fire, and it isn't. Most of these weren't happening to one guest in a hundred.
The ten-hour visit fault further down caught two people, on a day when more than 6,000 bookings were started. The payment slider one left 27 bookings a few pence short, out of roughly 100,000 made online since payment plans launched in August. That's 0.03%. A month ago I'd have told you a 0.03% problem wasn't worth anybody's afternoon.
The trouble with that maths is the other number. Venues on BookingNinja took 33,755 online bookings in the last 30 days. If something small stops just half a percent of guests, that's 169 people a month who had picked a date and got as far as a form before giving up. And it's never one thing catching all of them. It's a handful of things catching a sliver each, on different steps, at different venues, which is why no single venue ever sees enough of it to notice.
A button that said nothing
The details step asks for a name, an email and whatever else you've chosen to ask. Its Continue button stayed greyed out until every required field was filled in, and nothing said which one was missing. Reading those timelines is a bit painful. Tap Continue. Wait. Tap it again. Scroll to the top, scroll to the bottom, tap it again.
Now the button can always be pressed, and if something is missing the page says what, right above it: "Still needed: Full Name (and 1 more)".
The date step did something similar. A date you couldn't book was just dead, with no reason given, so a closed Monday looked the same as a Saturday that had sold out. Tap one now and the reason appears under the calendar in a sentence, "No times left on Wednesday 11 November" for instance, with a button for the next date that does have space.
A third one only showed up on booking pages embedded in a venue's own website. On the guests step, Continue could end up two screens below the last thing the guest had touched. It now sits at the end of the step.
Twenty-seven bookings that owed pennies
This one is my favourite, in the way you have a favourite pothole.
Payment plans let a guest choose how much to pay today by dragging a slider. The slider moved a pound at a time, so on a total that wasn't a round number, the far end of it stopped short. A guest who shoved it all the way to the right, plainly meaning to pay the lot, still owed a few pence. Between 1p and 80p, in the cases we found.
Then it gets daft. Stripe won't process a card payment under 30p. So some of those guests owed a venue 1p and had no way of paying it, even if they'd wanted to.
It had happened to 27 bookings at one venue, £5.90 between them. The slider now snaps to the full total at the top, and anything too small for the card provider to charge counts as paid. The 27 balances have been written off.
The moment after pressing Pay
The Pay button could be pressed before the card form had finished loading. It now waits. If the card form never loads, the guest gets a button to reload it instead of an empty box. And if a payment goes off and no answer comes back, the page checks what happened to it. Before, it would spin for as long as you were willing to look at it.
Gift card buyers had a stranger one. A payment is confirmed by two routes, the guest's browser and a message from the payment provider, and the two race each other. When the provider won, a buyer who had paid was shown the words "voucher_basket_empty". They'd paid, the gift card existed, and we greeted them with an error code. They now land on their completed purchase.
Eleven presses in twenty-five seconds
One board game café offers a ten-hour visit. The booking page showed the ten-hour option, and the server behind it refused anything over eight hours, replying with "The duration field must not be greater than 480." I don't know what the guest made of 480. I do know they tried eleven times in twenty-five seconds, then gave up and booked a shorter visit.
Four venues offer visits longer than eight hours, and all of them can now be booked.
A question you couldn't answer
A guest who went back to the calendar partway through a booking was asked "Start New Booking?", with two buttons underneath. If a session's details were still open behind the question, neither button could be pressed. You could read it and you couldn't answer it. Three of the 312 visits ended right there. Both buttons work now, and "Continue Booking" takes the guest back to the step they left.
Some venues cap how many bookings one guest can make in a day. Guests over the cap only found out after filling in the whole details form, from a message that popped up, said no and disappeared. The message now stays on the page and says what the limit is, with a "Choose another date" button that keeps everything they typed. A guest who is signed in gets told at the date step, before they reach the form at all.
Times that looked like buttons
On the calendar view, the times with space on a day were laid out as a row of neat rounded boxes. They looked exactly like buttons and they weren't. About half the guests who saw them tapped one. We could have restyled them to look less tappable, but if half your guests think something is a button, it should probably be a button. Tap a time now and the booking starts with that time carried through.
The time step had a dead end of its own. A day can have more than one thing to book, ordinary dining and a special brunch, say. If the one you'd picked had no times left, you got a grid of crossed-out times, no explanation and a Back button. It now tells you there are no times left for that option on that day and shows the options that do have space, next to a "Choose another date" button.
Why this gets our time
Booking software gets judged on its feature list, and I enjoy shipping features as much as anyone. But your guests will never see the floor plan editor. They see a calendar and a form with a Pay button at the end of it, on a phone, probably with something else going on around them.
And you can't see what they see. A guest who leaves isn't in your bookings, so there's nothing there for you to notice. We can look across every venue's booking page at once, which makes this our job.
One more thing, since I've spent most of this post on faults: a lot of what we read was dull. Somebody picks a date and pays. Nothing was slow. What went wrong was nearly always one small thing in one place.
We're going to keep reading them. And if a guest has ever told you they gave up on your booking page, tell us where they got stuck. We'd like to go and look.