It’s Saturday night and the dining room is nearly full. You have five reservations arriving between 8:30 and 9:00. A couple walks in without a reservation, peers inside, and asks: “Do you have a table for two?” What do you do?
Say no and you lose two covers. Say yes and seat them at a reserved table that hasn’t arrived yet, and you risk chaos when the reservation shows up. Wing it and maybe it works — but maybe it doesn’t.
This dilemma plays out dozens of times a week in most restaurants. And the answer isn’t “reservations only” or “walk-ins only” — it’s finding the balance between the two.
Why you need both
Some restaurants work by reservation only. It works for them, but they miss a slice of clientele: the spontaneous diners, the people who walk by and get curious, those who don’t want to plan ahead.
Other restaurants don’t take reservations at all. It works for casual, high-turnover spots, but it means queues outside, guests walking away, and no ability to plan service.
Most restaurants live in the middle: they accept reservations but also want walk-ins. The problem is that without a system, the two streams collide.
The most common problems
The phantom table
You have a table reserved for 8:30 that at 8:45 hasn’t shown up. Meanwhile, you’ve turned away three walk-ins because “that table is reserved.” Result: the table sits empty for an hour, the walk-ins went elsewhere, and the no-show cost you twice. We covered this in our article on restaurant no-shows.
The overridden reservation
A walk-in arrives, the server seats them at the only available table. Five minutes later, the guest with the reservation walks in — that was their table. Embarrassment, apologies, an angry guest. Your reputation takes a hit.
The endless wait
The walk-in agrees to wait “ten minutes.” After twenty, they’re still standing. After thirty, they leave — and tomorrow they write a bad review. The estimate was wrong because nobody had visibility into when a table would actually free up.
The buffer strategy
The most effective solution is the buffer: keep a percentage of tables off the reservation system, always available for walk-ins.
In practice:
- If you have 15 tables, make 12 reservable and keep 3 always available for walk-ins
- The percentage depends on your mix: if 30% of your covers are walk-ins, the buffer should reflect that
- On slow nights (Monday-Wednesday), the buffer can be smaller
- On busy nights (Friday-Saturday), the buffer matters more
The advantage is twofold: you never completely turn away walk-ins, and reservations are never disrupted.
The timeline as a decision tool
When a walk-in asks for a table, the real question is: “When does a table free up and how long can I use it before the next reservation?”
With a paper book, answering is an exercise in memory and instinct. With a digital timeline, it’s data:
- Table 5 has a reservation at 8:00 for 2 guests → estimated free at 9:30
- Table 8 is a walk-in who arrived at 7:45 → probably free at 9:15
- Next reservation for a 2-top is at 9:45
You can tell the walk-in: “We’ll have a table in about 15 minutes — would you like to wait at the bar?” Precise information, no vague promises.
Managing the waitlist
When you don’t have immediate tables for walk-ins, the waitlist is your tool:
- Get name and phone number — don’t ask guests to stand by the door
- Give an honest estimate — “About 20-25 minutes” is better than “Soon”
- Notify when the table is ready — a quick text or call
- Track who’s waiting — to avoid forgetting anyone
If your system has an integrated waitlist, the flow is automatic: the guest registers, receives a message when the table is ready, and their data enters the system like any other reservation. For a deeper look at timing, estimates, and communication, read our guide to managing and communicating the restaurant waitlist.
Walk-ins and CRM: the data you’re losing
The hidden difference between reservations and walk-ins is data. Guests who reserve leave their name, phone number, often email. Walk-ins are anonymous — you don’t know who they are, can’t re-contact them, can’t build loyalty.
This is a problem because walk-ins are often the ones with the most potential: they’re local, they pass by often, they could become regulars. But if you don’t capture their data, you can’t build a relationship.
The solution is simple: register walk-ins in the system too. Ask their name when seating them (you already do this as a courtesy), and if service goes well, ask if they’d like to leave their contact for next time. “Next time you can book directly from our website — shall I send you the link?”
Every walk-in converted to a contact is a future guest you can retain.
Team alignment and communication
Balancing walk-ins and reservations only works if the entire team is aligned. A server who seats a walk-in without checking the timeline throws off the whole service. A host who turns away a walk-in while tables are free loses covers.
Clear rules:
- Only the person with full visibility assigns tables — typically the host or manager
- Servers never seat a walk-in independently without confirmation
- The updated timeline is the single source of truth — not memory, not “I think”
With a system accessible from a phone, anyone can check the situation in a second. We covered this in our article on running your restaurant from your phone.
Walk-ins and reservations: allies, not enemies
Coperti manages reservations and walk-ins on the same timeline. You see in real time which tables are occupied, reserved, or free. The waitlist is integrated. Walk-ins are registered in the system and their data enters the CRM just like any booking guest.
If you want to stop improvising and start managing the flow with data, get in touch for a demo. Walk-ins and reservations don’t have to be a problem — they can be your best system for filling the dining room.