An empty table is not always available
A couple arrives without a booking. One table is empty, but it is reserved in 25 minutes. Whether it can be offered depends on expected visit length, preparation and a conversation with the guests. Bonzumo shows reservation and table context so reception and service can decide from the same information. Software cannot replace that conversation. An honest statement about an available window is better than a promise that must be withdrawn after a few minutes.
Make deliberate room for walk-ins
A venue with many regulars arriving without bookings may need a different mix from a restaurant where almost every evening table is reserved. Consider which areas or periods should stay flexible. A fully booked plan can turn away spontaneous demand even when tables later remain empty. Keeping too much in reserve can also waste space. Bonzumo supports rules, capacity and floor planning. The right balance comes from actual arrivals and the character of your service.
Separate booked arrival from actual occupancy
A booking for 7 pm does not mean the party is already seated. A walk-in may also stay longer than expected. Reception needs the current occupancy and must record changes promptly. That is how the plan stays aligned with the room. Decide who updates arrivals, newly available tables and delays. If service and reception each maintain an unofficial list, conflicting promises appear precisely when the venue becomes busy.
Give waiting guests a clear answer
When no suitable table is free, a waitlist may help. It needs a party size, a realistic expectation and a person responsible for updates. Do not tell a guest a table will definitely be ready in ten minutes while the current group is still ordering. Bonzumo provides waitlist and reservation context; specific notification routes need to be checked for your venue. A short personal update with honest flexibility builds more trust than a precise but unsupported wait time.
Record table moves and booking changes
A walk-in moves from the counter to a table while a booked group arrives late. Such changes need to be visible in the shared plan. Before moving anyone, check the next booking for that area. Tell reception and service what was decided so both see the same situation. Bonzumo should serve as a common working view. The actual seating decision remains with the team that knows the room, guests and current pace of service.
Test a small arrival rush
In a demo, place two bookings, a late party and two walk-ins in the same short period. Ask which table can be offered immediately, who needs to wait and when a booking requires a follow-up question. Let another colleague handle the next arrival. Can they understand the plan without finding the first receptionist? This test shows whether floor view, booking times and waitlist genuinely help your venue in its busiest half-hour.
A short table offer can change the whole sequence
A couple without a booking is offered a window table because a reserved party is late. Ten minutes later the booked group arrives after all. The team now needs a view of the promise made, expected visit length and possible alternatives. The walk-in guests cannot simply be moved without explanation. At the first offer, reception should therefore be honest if the place is available only for a limited window. A clear early conversation is easier than a hurried apology once drinks have been ordered.
A booking should not disappear from the plan solely because a party is late. Agree who contacts the guests, how long a place may be held and when it may be offered again. The rule depends on your concept and the specific promise already made. Bonzumo shows reservation and table context so the decision need not be reconstructed from memory or a private chat. Record a change in the shared view before confirming the same space to another party.
During a demo, hand the situation to a colleague who did not make the original offer. Can that person explain what the walk-in guests were told and which booked group is still expected? They need the current plan and a short factual note. Without it, reception may tell two conflicting stories at the entrance. A practiced sequence welcomes spontaneous visitors without pushing confirmed bookings aside by accident. It also gives servers a clear account of why a table has a time limit or why a waiting group has been offered another area.
