A booking starts a guest journey
A restaurant reservation begins with a name, time and party size. Reception needs more context to turn it into a good visit: which area is intended, how the group fits the tables and what happens if arrival is delayed. A digital reservation book becomes especially useful when those decisions connect to the floor plan. The team should be able to recognise the booking in the actual dining room.
Bonzumo connects reservations, guest information and table planning. The system includes online booking, changes, table assignment and check-in. This supports the journey from an expected visit to guests being seated. Its practical value appears at reception, where the information is used to decide the next few minutes of the guest experience.
Bring booking channels into the shared process
Guests reserve in different ways. Some book online, others call or ask in person. What matters to your team is that reliable details reach the shared reservation process. Confirm the date, time, party size and necessary contact information when accepting a booking. A telephone promise left only on a loose note will be missing when someone later decides how to use a table.
Bonzumo includes online booking and reservation management for the venue. During setup, establish which times and rules apply and how the booking entry point will be used on your website. Follow the complete journey with an appropriate test booking: what can the guest select, what does reception see and how is a change handled? A clear booking page becomes useful when its information also makes sense in the reception workflow.
Match table allocation to the party
Four guests need more than four unrelated empty chairs. They need a suitable seating arrangement. A pushchair, an area preference or a group wanting to sit together may affect the choice. Record relevant requests clearly and distinguish a preference from a confirmed promise. A request for an outdoor table does not automatically guarantee terrace seating in all weather.
Bonzumo's table context includes areas, tables and seating capacity. Use it to assign bookings appropriately and discuss the arrangement with service staff. Review larger groups early: which tables are available, which combination is practical and which other bookings sit close to the same time? A total headcount cannot replace that assessment, even when the restaurant appears to have enough seats overall.
Treat check-in as a meaningful transition
Arrival changes a booking from a plan into a party that is physically present. An organised check-in helps the team recognise that transition. Confirm the correct name and actual party size, resolve outstanding arrangements and check the proposed seating. Servers should be able to identify the arrived group rather than guessing from a booking list whose status has not changed.
Bonzumo includes a check-in process and reservation statuses. These are useful when the team applies them consistently. Decide who handles arrivals and when a further update is needed. If two colleagues share reception, they also need enough coordination to avoid processing the same party twice. A clear status supports their work, while the personal welcome remains the responsibility of the people greeting the guests.
Handle changes in their seating context
A later arrival may affect another reservation. Review the table arrangement and the next intended use instead of changing only the time. The same applies when a party grows. An extra guest does not automatically fit every table already assigned to the booking. The relevant question is whether the actual seating arrangement remains suitable at the revised time.
Give service staff a short handover whenever a change affects their work. What has been promised, what remains unresolved and who will speak to the guest? Bonzumo brings reservations and seating context together so these decisions can use a shared basis. Restaurant reservation software can then bring structure to reception while preserving the flexibility needed for a real evening of service.
Friday service: a party grows from six guests to eight
At 4 pm, a party booked for 7 pm calls to add two people. Two more chairs may sound like a minor change, but at the assigned table they would narrow the route to the kitchen. The neighbouring tables are needed for another booking half an hour later. Reception therefore finds a workable arrangement before confirming the larger group, instead of treating a changed number as proof that suitable seating is available.
Bonzumo allows the reservation to be handled with its revised party size and appropriate table or area assignment. The useful sequence is to establish the seating, update the shared booking and tell the affected service team. If the only suitable alternative is at another time, discuss that specific offer with the guest. The benefit comes from making the new arrangement workable in the room as well as correct in the booking details.
Preparation matters too. Eight guests may require a different table setting from six. Service staff need to know which arrangement to prepare before finishing the original layout. A short, clear handover can prevent the team from setting and resetting the same space immediately before a busy evening.
Two guests arrive before the rest of their party
Only two members of a six-person party initially arrive. Reception welcomes them, identifies the reservation and asks whether they would like to sit down. Their arrival should not make the table appear to require only two seats. Equally, the team should not assume the entire party is present if that would give service staff the wrong expectation about when everyone will be ready.
Agree how the existing reservation details and check-in process will be used in this situation. The booked party size remains the reference for seating, while the actual arrival is handled through the intended workflow. Give the server a short explanation: two guests are seated and four are still expected. No automatic presence-detection feature is assumed. What matters is a shared account of what has actually happened and what the team should expect next.
If another guest later asks for the party using a different name, the established booking context helps reception connect them with the right table. They do not need to create a second apparent reservation or allocate additional space. A little clarity at the first arrival avoids confusion when the rest of the group follows.
Separate late arrivals from visits that will not happen
A booking expected at 8 pm has not arrived by 8.10 pm. That observation alone does not establish that the table can be reassigned. Somebody may have called about a delay, or there may be a misunderstanding about the agreed time. Begin by checking the latest information associated with the booking. If a follow-up is appropriate, one responsible person should handle it rather than several colleagues independently contacting the same guest.
Decide internally when the supervisor makes a decision about further table use and how existing promises are considered. This is a restaurant policy, not a universal waiting period. Bonzumo provides the reservation time, assignment and status as context; automatic release after an arbitrary delay is not assumed here. Your team should distinguish a party that has not arrived yet, a known delay and a visit that has been confirmed as cancelled.
Once a decision is made, reception and service need the same account. Otherwise one person may reassign the table while another still prepares for the original party. A late guest is easier to welcome calmly when staff know the last agreed arrangement and the reason for the current seating decision.
Carry a telephone promise through to the evening team
A colleague may take a request during the afternoon while different staff welcome the guest at night. The essential detail needs to reach the reservation process rather than remain in the first person's memory. A useful handover describes the practical requirement, such as additional room around a table, and distinguishes it from a promise that has already been confirmed. Personal speculation about the guest adds little to that task.
Keep the information relevant to the visit. Reception should quickly understand what needs preparing or clarifying. A dietary request may also need a discussion with the responsible kitchen colleague; recording a note does not establish that every requested preparation is possible. The restaurant supplies the professional answer and then makes the agreement with the guest clear. This avoids a request being repeated internally as if it were already an unconditional commitment.
When a telephone conversation changes an existing booking, work within that context. Creating another reservation because the first is not immediately recognised can make the space requirement appear twice. Check the name, date and time together before deciding a new booking is needed.
Prepare the few bookings that need a decision
Before service, concentrate on reservations that genuinely need attention: large parties, close transitions between visits, unresolved area requests and known changes. An ordinary table for two rarely needs the same briefing time as a group without an agreed seating arrangement. Reception can identify the exceptional cases and tell the service team which table plan is current at the start of the shift.
After the evening, ask specific questions. Was a group moved because its party size had not been updated? Did a telephone request fail to reach the person greeting the guests? Did two colleagues interpret a late arrival differently? Each answer points to a focused improvement without adding unnecessary administration to every future booking. Bonzumo supports the common reference through reservations, table context and check-in.
For a demonstration, choose one of these real cases. Follow a booking, change the number of guests and carry its seating arrangement through to arrival. That shows whether your team can use Bonzumo to keep promises aligned with the space actually available, while maintaining the flexibility that a busy restaurant evening requires.