Academy › Build › Bookings and orders
Whoever pays first keeps it, not whoever looks first
That the slot belongs to whoever finishes booking first, and that gets checked before you confirm, not when someone sees it open, plus there's a different plan for when the conflict has already happened and two confirmed appointments are fighting over the same resource.
By Yodai · Published September 7, 2026 · Updated October 12, 2026
Two people open the booking page for the same service at almost the same time: a paraffin wax treatment, and you only have one paraffin treatment table in your shop. Both see the 10 a.m. slot open. Both fill in their details. Both hit book within fifteen seconds of each other.
If both bookings get confirmed without anyone checking the treatment table, the first person shows up at ten, and a quarter hour later the second one arrives, and there's no table left for her. That appointment isn't lost to bad luck. It's lost because no one decided ahead of time who keeps the slot and at what point that gets checked.
The moment that matters is confirmation, not the asking
When two services want the same time slot, someone has to lose it. What you need to decide is when you find out who loses. And the answer isn't whoever got to the page first. It's whoever finishes booking first: whoever completes the booking and, if you ask for a deposit, pays it.
Between the moment someone sees an open slot and finishes booking it, seconds go by, sometimes minutes if they have to dig out their card. During that time the slot still shows as open to anyone else looking, so you can end up with two requests for the same table. That's why the real check happens on your end, before you confirm: you look at which one finished first, confirm that one, and message the other. If you confirm both without checking, neither person finds out until one of them shows up and there's no room.
- 10:02:00Ana and Bruno both see the 10 a.m. slot open with the paraffin wax table.
- 10:02:05Ana finishes booking and pays the deposit.
- 10:02:20Bruno finishes booking the same slot fifteen seconds later.
- 10:15:00You see both requests. There's only one paraffin wax table, so you confirm Ana's, since it was completed first.
- 10:16:00You message Bruno with the other open slots that have a table free, so he doesn't have to start searching from scratch.
What you tell the second person
Bruno is going to lose that slot either way. What really matters is how you tell him. A message that just says there's no room left forces him to scroll through the whole schedule from scratch, and he might go to another business before he's done looking. Message him right away with specific openings, and if he already paid the deposit, tell him you'll apply it to the new time or refund it.
When the conflict already happened: two confirmed appointments for the same resource
Checking before you confirm prevents the clashes right in front of you, but not the ones that slip through when several channels are running at once: a phone call you jot down by hand, or an appointment a customer locks in over WhatsApp while someone else on your team separately confirms a booking from the website. That's when two already-confirmed appointments really can end up sharing the same table at the same time, and then someone actually has to be moved.
Which one gets moved? The slot belongs to whoever confirmed first, and you don't move that person without their okay. What you can do is ask: if the person who confirmed first is a regular with an open week, and the other person can only make it that specific day, call the regular first and ask if they're open to switching. If they say yes, nobody loses out. If they say no, you move the appointment you confirmed later, and you tell that person right away, with other time options.
- Both requests come in, and you check which one was completed first
- You confirm one and offer the other person a different slot, so no one ends up with an appointment and no room for it
- It happened over the phone, on WhatsApp, or through a manual entry
- Both appointments already exist, confirmed
- Both people think they have a spot
- The slot belongs to whoever confirmed first, unless they agree to switch; whoever gets moved is told right away, not whenever there's a free minute
Which one applies: In the first case, you decide before anyone has an appointment; in the second, someone already thinks they have a spot, and you have to move them. The more bookings run through one place you check before confirming, and the fewer that get jotted down loose over the phone, the less often you'll run into the second case.
How long you hold a slot for someone who hasn't paid the deposit
When the booking comes in by WhatsApp or by phone and you ask for a deposit, another problem shows up: what happens if that person says yes and never actually pays? If you hold the slot with no deadline, you're the one who loses out, not them. That's why you hold the slot with a short deadline that you state in the same message, for example, "I'll hold it for you until 6:00 PM": just enough time to make the payment, not enough to mull it over with a coffee. Once the deadline passes, you free it up and give it to whoever asks next.
With that, the whole shared-resource mechanism is in place: you know which resource your services share, you know what buffer you build in, you know what to do when two appointments want it at once, and now you know the exact moment that decides who keeps it: at confirmation, by checking which request was completed first.
- The slot belongs to whoever finishes booking first, not whoever sees it first, and you're the one who checks before confirming
- The second person gets concrete alternatives, not just a message saying there's no room left
- If you hold a slot while waiting on a deposit, hold it for a short window stated in the message, and release it once that window passes
- An already-confirmed conflict, by phone or WhatsApp, gets resolved by leaving the slot with whoever confirmed first, unless they agree to switch, and letting whoever gets moved know right away
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. Two customers text on WhatsApp almost at the same time, asking for the same slot with the only clay oven you have. One pays the deposit on Venmo at 4:03 PM, the other at 4:07 PM. Who gets the oven?
The 4:03 PM one, even if they both wrote in at the same time: whoever finishes booking first, deposit paid, wins, not whoever asked first in the chat.
2. A customer asks you over WhatsApp for an appointment with your only delivery van, you tell them you'll hold it until 6:00 PM if they pay the deposit, and they don't pay. At 6:30 PM another customer asks for that same slot. Do you give it to them?
Yes. The deadline you gave the first customer has already passed with no payment, so the slot is free. Holding it longer for someone who never came back costs you the booking of someone who actually wants to pay right now.
3. You jotted down a phone appointment by hand for the physical therapy room at noon, and before you logged it in your calendar, someone else on your team confirmed a website booking for that same time. Both appointments end up confirmed. Which one do you move?
The slot belongs to the phone customer: you confirmed it first, even if you took a while to write it down. If you know they can come at one o'clock without any trouble, and the website customer can only make that day at that time, call them right now and ask if they're okay switching. If they say yes, nobody loses out; if they say no, you move the website customer and tell them right away, with other time options.