How to Organize Phone, Walk-In, and Website Reservations
Three intake channels, one dining room. How to keep the phone, the door and your website feeding a single book without double-booking a table, wrecking your pacing or losing a walk-in you could have kept.
A restaurant with one dining room usually has three ways into it. The phone rings, someone appears at the door, and a form on your website fills itself in at half past eleven at night. Each channel arrives with different information, at a different speed, into a different pair of hands — and all three are competing for the same forty tables.
Nearly every reservation problem worth solving is a collision between those three. This is how to run them as one system rather than three habits.
One book, whatever the channel
The rule is short enough to put on the wall by the phone: every booking goes into one book, whatever channel it came from, and it goes in within sixty seconds of the promise being made.
Sixty seconds is not arbitrary. It is roughly how long a promise survives in a busy person’s head before a table needs bussing, a supplier walks in the back door and the whole thing evaporates. Anything longer than that and you are not running a reservation system, you are running a memory test during the busiest hour of your week.
- The website booking is already in the book. Nobody has to do anything, which is the entire point of it.
- The phone booking goes in while the guest is still on the line, not after.
- The walk-in that asks for next Thursday goes in before they leave the building.
- The booking taken by the owner on their personal mobile at the weekend goes in from the owner’s phone, not on Monday morning.
There is no such thing as a temporary second list
A sticky note by the till, a WhatsApp message to the manager, a name written on the back of a docket. Each one is a second book with a half-life of about three hours, and the table it double-sells will be on a Saturday. If it is not in the book, it did not happen.
If your intake still runs partly through an inbox, that is a fourth channel and the worst of them. How to Stop Managing Restaurant Reservations Through Email deals with closing it down without losing the guests who use it.
The phone during service
The phone is the hardest channel because it demands attention at exactly the moment you have none. Three decisions make it manageable.
First, decide who answers, by name, for each shift. Not "whoever is nearest" — that is how a call gets picked up by a runner with two plates in their hands. During peak seating, the person on the pass or the host stand takes it, because they are the one standing next to the book. Everyone else lets it ring through to voicemail with a message that gives out the website address.
Second, agree what they say. A booking call should take ninety seconds, and it takes ninety seconds when the order of questions is fixed: date, time, party size, name, mobile number, anything we should know. Ask for the mobile number before the name — people give it more readily mid-flow, and it is the field you will regret missing.
Third, and this is the one that matters, enter it while the guest is still on the line. Reading the details back off the screen rather than off a scrap of paper catches the wrong Thursday, the misheard surname and the party of six that was actually a party of sixteen. "I will write it down after service" is the single most expensive sentence in restaurant operations, and it is always said sincerely.
The busy-signal test
For one week, count the calls that went unanswered during your two busiest hours. If it is more than two or three a night, the fix is not more discipline on the phone — it is making the online route obvious enough that those guests never need to call.
Walk-ins in a booked room
Walk-ins are not the opposite of bookings. They are the part of your covers that has not been scheduled yet, and a room booked to one hundred per cent is a room that turns away everyone who walks past and likes the look of it.
- Hold a share back. Reserve a proportion of covers for the door — commonly ten to twenty-five per cent, higher for a bar-led room, lower for a destination restaurant people travel to. Hold specific tables rather than an abstract number, ideally the small two-tops that are hardest to fill with bookings anyway.
- Set a last-seating cut-off and mean it. Both online and at the door. The kitchen needs to know the latest ticket, and a walk-in seated fifteen minutes past it costs you a clean finish and a chef’s goodwill.
- Quote a realistic wait, then beat it. Look at the table you intend to give them, add the time to eat and the time to reset, and add ten minutes. A guest told forty-five minutes and seated in thirty-five is delighted. Told twenty and seated in thirty-five, they are annoyed, and it is the same table.
- Turn the refusal into a booking. If you cannot seat them tonight, do not say sorry and open the door. Offer next Thursday and enter it there and then on the stand. This is the highest-conversion booking channel you have and most restaurants use it by accident.
Record the walk-in in the book even when they are seated immediately. A walk-in that is never entered is a cover that never happened, and by the end of the month your covers report is wrong by however many people simply came in.
Website bookings arrive with details and no context
The online channel is the inverse of the phone. You get a clean name, a real email address and a working mobile number, with zero of the information a host picks up in the first ten seconds of a call: the tone, the occasion, the fact that one of the party uses a wheelchair, the fact that they are catching a train at nine.
That means the special-request field is not a nicety, it is the entire context channel. Label it so it prompts the right answer — "Occasion, access needs or anything else we should know" pulls far more useful detail than "Notes". Keep the rest of the form short; every extra required field costs completions. Restaurant Booking Widget Explained covers what belongs on the form and what does not.
Then act on what comes back. A booking that says "wife’s birthday" and gets no acknowledgement is worse than no field at all, because the guest told you and you did nothing with it. Someone should read the day’s requests once, in the afternoon, and either handle them or reply.
The online channel also has a property the other two lack: it can tell you where the guest came from. If your booking links carry tracking, a booking from a Google listing looks different in your reporting from one that came off an Instagram story, and after a couple of months you can stop guessing which of your marketing is doing anything.
What to record for every booking, whatever the channel
Different channels arrive with different information. What you store should be identical, or your reporting compares things that are not comparable.
The status field is the one that gets skipped and the one that pays. Without it you cannot tell a quiet Tuesday from a Tuesday where a quarter of the book did not turn up, and those two problems have completely different fixes.
Holds, grace periods and the shift handover
Decide your grace period once, write it in the confirmation, and apply it the same way every night. Fifteen minutes is the common standard, and it works because it is short enough to release the table and long enough to survive a bus.
- At the booked time, the table is theirs. Do not seat a walk-in on it because the room looks busy.
- At five minutes late, call the mobile. This one call recovers more tables than any policy you can write, and it is the reason the number is a required field.
- At fifteen minutes with no answer, the table goes back into the pool and the booking is marked as a no-show. Marking it matters as much as releasing it.
- If the guest arrives after that, seat them if you can and be gracious about it. The policy exists to protect the room, not to win an argument.
Grace periods manage the symptom. Reminders reduce the cause — How to Reduce Missed Restaurant Bookings covers the messaging side of the same problem.
The handover between shifts is where cross-channel information leaks. A lunch host takes a call about a party of ten on Saturday, sorts it beautifully, and goes home. Keep the handover to three things: anything promised verbally that is not in the notes, anything moved or cancelled since the sheet was printed, and any guest arriving tonight who needs a specific table. Two minutes, spoken out loud, with the book open in front of both people.
Pacing: why four bookings at 20:00 is a kitchen problem
Four tables of four booked at 20:00 and four tables of four booked across 19:45 to 20:15 are the same sixteen covers and completely different nights. In the first, sixteen starters hit the pass inside four minutes, the kitchen falls behind by a ticket and stays behind for an hour, and the guests who booked at 20:30 wait for food that is already late. In the second, the same sixteen covers arrive in three waves the kitchen can absorb.
This is not a kitchen skill problem. It is an arithmetic problem you created when you let four bookings land on the same slot, and it is fixed in the booking rules rather than on the line.
- Space your online slots at fifteen minutes rather than thirty. Guests barely notice, and the peak flattens on its own.
- Cap the covers bookable in any one slot. Work out how many starters your pass can genuinely fire in five minutes, and set the ceiling there.
- Apply the same cap to phone and walk-in bookings. A pacing rule that only one channel obeys is not a pacing rule.
- Watch the shoulders. If 19:00 and 21:00 are always empty while 20:00 is always full, the answer is usually a reason to come early rather than a bigger kitchen.
Pacing rules only work if they bind every channel
The common failure is an online form that respects the cap while the phone happily books over it, because saying no to a guest on the line feels rude. Set the cap in the system, let the system be the one that says no, and give the team a script for offering fifteen minutes either side.
Run this at the start of every service
Ten minutes, same order, every day. It is the cheapest operational habit in the building.
- Print or open tonight’s book and read it end to end, including the notes column. Do not skim it.
- Check the peak slot for pile-ups and move anything you can with a friendly call, offering fifteen minutes either way.
- Flag the bookings that need something — birthdays, access needs, dietaries, anyone on a deadline — and tell the section who owns them.
- Confirm today’s walk-in hold: which tables are being kept back, and until when.
- Confirm the last-seating time out loud so the kitchen and the floor have the same number.
- Check that every large party has a mobile number attached, and chase the ones that do not.
- Name who is answering the phone during the peak, and where the pen is if the system goes down.
None of this depends on which software you use, or whether you use any. It depends on the book being one book. If you are still deciding what that book should be, Paper Reservation Book vs Online Reservation System is the honest version of that comparison.
Related articles
- Paper Reservation Book vs Online Reservation SystemAn honest comparison of the paper diary and a reservation system across the things that actually matter during service — speed at the pass, availability, reminders, guest history, reporting and what happens when the internet drops.Updated 7 July 2026Read More
- How to Stop Managing Restaurant Reservations Through EmailEmail is a message queue, not a reservation system. Here is how to audit what your inbox is really doing, move the first step off it, and keep the exceptions email genuinely handles well.Updated 31 March 2026Read More
