Capacity is more than a seat count
A room with 40 seats cannot welcome unlimited new parties at 7 pm. Reception, kitchen and service have their own limits. Plan the distribution of arrivals as well as the physical number of chairs. Bonzumo supports areas, capacities, times and rules within the reservation flow. Set those values from real observations. A quiet Tuesday may allow different flexibility from a Saturday when the terrace is full.
Choose realistic visit lengths
Two people visiting for coffee use a table differently from a group having several courses. Giving every booking the same short duration can make the plan look efficient on screen while failing in the dining room. Define useful slots and buffers for your typical visits. Review whether the assumed duration fits actual service. A floor plan helps reception see the effect of a change, but a rule should never be applied without considering the people in front of them.
Spread arrival waves deliberately
When many groups arrive together, more than reception becomes busy. Kitchen, bar and servers all receive work at once. A small change to available times may spread arrivals more evenly. Consider typical peaks and staffing when setting up the system. Bonzumo can show occupancy in the chosen time and area context. It cannot decide for you how many new guests your team can welcome well in one phase of service.
Use a waitlist with a clear promise
When no suitable table is free, a waitlist may offer another route. It should not promise a table that another group is still using. Record who is waiting, the required party size and who will update the guests. Bonzumo provides reservation and waitlist context. The available notification routes must be checked for the exact setup. A friendly, honest estimate is worth more to a guest than an inaccurate automatic promise.
Keep short-notice changes visible
A late arrival, cancellation or smaller party changes the plan. Give someone responsibility for recording the change in the shared view. Otherwise reception may rely on a spoken update while servers still prepare the original table. Review the next bookings and possible walk-ins whenever plans change. Capacity should support judgement, not become a number that replaces the actual situation at the entrance.
Test a busy arrival period
In a demo, put three arrivals close together, including one late party and a walk-in. Ask the team to explain table choices and what a change would affect. Continue until it is clear who updates waiting guests and what the new plan looks like. That reveals whether your time slots serve your concept and whether Bonzumo supports reception during a real peak.
Understand the chain of bookings on one table
A table for four is booked at 6 pm, with another party expected there at 8 pm. The first group orders later than anticipated. Reception cannot look only at the second arrival time. It needs to see what alternatives exist, who updates the guests and whether a buffer was allowed. The same applies to a waitlist: a table that looks nearly free is available only when the earlier visit has actually ended and the place is ready for the next guests.
During setup, run three bookings on one table over a full evening. Extend the middle visit and observe which promises become uncertain. This reveals whether time slots and expected visit lengths fit your restaurant. It can also show whether some space should be held flexibly for walk-ins. Bonzumo supports the plan; the operator decides how much freedom is needed to balance service quality and demand. A visual timetable is helpful only when its assumptions are realistic.
Discuss the words used at the entrance. A waiting party needs a credible range and a person who will return with an update. If a fixed time cannot be supported, say so. Keep the current state in the shared plan rather than building several private queues. An understandable decision protects the mood at the entrance and prevents the next confirmed reservation from receiving a second promise for the same table.
Ask the team to record the reason when a planned slot changes. A late arrival, a table that remains occupied and a larger group have different effects on the following bookings. Seeing the reason lets the next shift respond appropriately rather than treating every delay as the same problem.