Restaurant guest information: make booking requests useful to reception and service

Guest information should improve the visit

A guest requests a particular area, a group celebrates an occasion or a booking changes at short notice. These details help reception when they belong to the correct reservation and are written clearly. A guest record is not valuable simply because it contains many notes. It is valuable when an authorised colleague can quickly understand what matters for the visit in front of them.

Bonzumo connects guest information, reservations and seating context. You can prepare around the actual booking: who is expected, what has been discussed and what does the service team need to know? That relationship supports personal hospitality without requiring one employee to remember every previous conversation.

Separate the contact from the individual booking

The same person may reserve several times, but earlier information does not necessarily apply to each new visit. The size of a birthday party, a one-off delay or a particular table request initially belongs to a specific occasion. Keep these visit details distinct from the contact information needed for the guest. That helps prevent an old note from becoming an assumed current promise.

Bonzumo places guests and bookings in a shared operational environment. During setup, check where your information is held and which view reception actually uses. The useful test is whether another colleague can understand today's visit without knowing the entire history. If a note contains conflicting statements, clearer wording is more helpful than another free-text field.

Record requests with an explicit meaning

A useful note states the request and, where relevant, whether it has been agreed. A request for a quiet table with confirmation still outstanding is clearer than an unexplained abbreviation. Avoid subjective comments about guests and record information for a defined operational purpose. The existence of a note field is not a reason to collect details unrelated to the visit.

Handle sensitive information deliberately. A note about an intolerance, for example, does not replace direct clarification about the actual dishes and ingredients. Staff need to understand what to ask and who will coordinate the answer with the kitchen. Define how information moves from reception to the responsible server. A saved note by itself does not guarantee that the correct person has seen or acted on it.

Use contact details for the booking task

A phone number or email address may be needed to discuss a reservation change. Make sure it belongs to the correct booking. When names are similar, clarify the identity instead of assuming they refer to the same person. With group bookings, the organiser may also differ from the first guest to arrive at reception.

Using contact details to organise a visit is not automatically the same purpose as sending a newsletter. Assess communication purposes, responsibilities and applicable requirements separately. Bonzumo provides the guest and booking context; the communication your venue uses is configured for its actual process. Do not assume that a guest record automatically includes a marketing campaign or loyalty service that has not been established.

Share relevant details at the right moment

A short pre-service overview often covers the important exceptions: a larger party, an unresolved area request or a later arrival that has been discussed. Servers need the information relevant to their task, rather than an entire contact history. A deliberate handover is therefore more useful than indiscriminately forwarding every note in the system.

After a change, check whether earlier information still applies. If the group has been offered a different area, an older conflicting note should not continue unnoticed. Bonzumo connects reservations with table planning so the current arrangement can serve as the reference point. Guest information supports attentive service when it remains current, understandable and accessible to the people who need it for the visit.

When the organiser arrives after the rest of the group

Eight people are expected at 7 pm. The organiser has asked about a quieter area and said she will arrive a little later. At 6:50 pm, three members of the group reach reception. They know the booking name but do not know which seating arrangement was agreed. Reception needs the connection between the reservation, party size and current agreement: identify the booking, establish the status of the area request and welcome the guests on that basis.

An earlier note asking for a window table is not proof that this table has been promised today. Suppose a different area was subsequently agreed by telephone. The current information needs to be maintained clearly enough that another colleague does not turn the older request into a second promise. The server needs a concise handover: three of eight guests have arrived, the organiser will follow and the agreed seating arrangement applies. Service can then begin without asking each new arrival to reconstruct the booking history.

The organiser’s absence should not leave reception guessing about every detail. Identify which matters have already been agreed and which genuinely need her answer. Guests can be welcomed while an unresolved optional request is clarified, provided the team understands the limits of the existing arrangement.

Turn a birthday note into a specific agreement

Birthday alone does not tell staff what has been requested or promised. The organiser might want a discreet greeting, or might have asked about bringing a cake without yet receiving an answer. Wording should distinguish a preference, an unresolved question and a confirmed arrangement. A note can identify that the cake request still needs discussion with the responsible colleague before the visit.

Reception mainly needs to know whom to ask and whether the conversation should be discreet. The server needs to know what is actually expected during the meal. Neither needs unrelated personal history about the celebration. If a specific dessert or other service has been agreed, its scope and ownership belong in the venue’s operating arrangements.

Guest information in Bonzumo provides the reference to the visit. It does not by itself create a production order, a price agreement or an event programme. That distinction helps avoid an employee interpreting a one-word occasion label as an instruction to provide something that has never been arranged.

Handle a telephone amendment against the right booking

A group was initially booked for six people. During the afternoon, someone calls to change it to eight and alter the arrival time. Before editing, reception establishes which booking is meant and whether the caller is the appropriate contact for that change. A shared surname is not enough when several reservations could match. Date, planned time and the actual booking context help avoid confusion.

Bonzumo provides reservation editing workflows. A change in party size also needs attention to seating: adding a note that eight people are coming is not operationally sufficient if the assigned table is still being prepared for six. The relevant colleagues need the revised position and any remaining seating question.

Do not assume that writing an amendment automatically alerts every member of staff. Agree who tells the receiving team about a change affecting preparation. A clear handover identifies what differs from the earlier arrangement rather than making everyone search the full record to infer which detail was updated.

Check seating requirements against the physical venue

A guest requests a table reachable without stairs. That is useful preparation information, but it does not establish which table is suitable. Reception clarifies the actual access route and available seating with the responsible person at the restaurant. A general label saying accessible is too vague as a promise if the entrance, route to the table and other areas the guest needs have not been considered.

Record the concrete arrangement for the visit, such as the agreed area and a specific access question still being clarified. Staff need information that helps them welcome and guide the guest, rather than an extensive personal description. Bonzumo connects the reservation with table context; whether a physical place meets the stated requirements is confirmed at the venue.

The same distinction applies to a request for a quieter table. It communicates a preference but cannot guarantee the noise level of a dining room throughout the evening. A clear conversation about the available area is more useful than storing an absolute promise that staff cannot substantiate.

Who needs which guest information?

Does the bar need every booking note? Usually it needs the information relevant to its actual task. A seating request initially concerns reception and floor service; an agreed drinks arrangement may concern the bar. Share information according to the work rather than simply forwarding everything in the record. This keeps preparation readable and avoids distributing unrelated personal detail.

What should happen to an older preference? Check whether it applies to the new visit. A birthday seating arrangement or previous party size should not automatically become a permanent description of the guest. A useful Bonzumo demonstration follows a returning visitor whose arrangements have changed: inspect the current reservation, table reference and information reception will actually use.

That example shows whether staff can offer a personal welcome while remaining open to what the guest wants today. The aim of restaurant guest information is to support the present visit, not to make every future conversation follow an assumption left over from a previous booking.