What a one-in-a-million booking taught us about looking after yours.
Every so often, something lands on our desk that stops us mid-sentence. This week, one did — and the story is worth telling, because it says everything about how we work and what we care about.
It began the way the best improvements always do: a restaurant told us something wasn’t right.
“Two bookings are sitting on the same table”
One of our venues got in touch. They’d found two separate reservations on the same table, at the same time, on the same evening — a 7pm dinner, two different parties, one table. On a busy night, that’s the kind of thing that becomes an awkward conversation at the door and a scramble to find space. Not good enough. Not for them, and not for us.
Here’s what a report like that does to our day: it stops everything. Whatever we were building that morning went straight on the shelf. When a booking goes wrong — the one thing our entire system exists to protect — it goes to the very top of the pile. No exceptions.
The mystery: our software says this is impossible
The first thing we did was retrace exactly how those two bookings were made. And at first, it made no sense at all. Our software is built so that the instant a table is taken, it vanishes from everyone else’s screen. Two people simply cannot book the same table. So how on earth did they?
Then we spotted it.
The two bookings weren’t made minutes apart. They were made in the very same instant — two different guests, on two different devices, somewhere out in the world, both pressing “confirm” within the same heartbeat.
Picture two people reaching for the last free seat on a train at exactly the same moment. Each glances down, sees the seat is empty, and goes to sit — because in that fraction of a second, neither could possibly know the other was reaching too. That’s precisely what happened. Each booking checked whether the table was free, and in that razor-thin sliver of time before either had finished, it genuinely was free — for both of them.
It’s astonishingly rare. It needs two strangers to choose the same restaurant, the same evening, the same table, and tap the button in the same slice of a second. But “rare” is not “never” — and if something can happen once, it can happen again. So we set out to make sure it never would.
Understood, fixed, tested and shipped — inside an hour
Once we truly understood what was happening, the fix became clear. We taught the system to account for those “someone is booking this right now” moments, so that two guests can never be handed the same table again — no matter how perfectly their timing lines up.
From first glance to a working, tested fix on its way out to restaurants: under an hour.
But we didn’t stop at fixing it. Fixing it, honestly, was the easy part.
The part we’re proudest of: making sure it stays fixed
Anyone can patch a problem once. The harder and far more important job is making certain it can never quietly creep back in six months later, when nobody’s looking.
So we wrote a set of automated tests that recreate this exact scenario — two bookings, one table, the same instant — and proved they would catch it. These tests now run automatically, every single time we prepare a new release. If any future change ever nudged that door back open, even by accident, these tests would slam it shut and stop the release before it ever reached you.
And that’s not a one-off; it’s simply how we build. Today, nearly 14,500 automated checks run before any update reaches your restaurant — and that number climbs by the hour. Every bug we fix and every feature we ship leaves behind another test, standing guard. It’s a safety net that gets stronger with everything we do.
Why we’re telling you this
We could have quietly fixed this and said nothing. We’re sharing it because it’s a small, honest window into how we work:
- We listen. All of this started with one restaurant taking a moment to say “this looks wrong.” That single message set the whole thing in motion.
- We take it seriously. A booking going astray isn’t a minor glitch to us — it’s the heart of what we do, and it jumps the queue every time.
- We build to last. Solving today’s problem is only half the job. The other half is guaranteeing it’s the last time you’ll ever see it.
To the restaurant that flagged it: thank you. You didn’t just help yourselves — you made the system better for every venue that uses it.
And to everyone else: if you ever notice something that doesn’t look right, tell us. It might just become our next story.