
Record details that actually help the visit
A booking name, time and party size help reception. A note about a pushchair or a request for a quiet seat may help with table choice. Not every private fact mentioned in conversation belongs in a guest profile, however. Bonzumo provides guest information in the reservation and floor-plan context. Decide which details your team truly needs, who may enter them and how to phrase a note so that it is useful and respectful.
Reception and service need appropriate views
The person at the door needs to find a booking and assign a table. A server may need a relevant seating request or current agreement. That does not mean everyone should see full contact details. Set roles and handovers around the work. Bonzumo connects guest, reservation and team contexts; actual access is configured for your venue. A useful handover names the next action instead of repeating an unnecessary story about the guests.
Update changes in the shared booking
A guest calls to move their arrival or add another person. If the change exists only on a scrap of paper, reception and service soon work with different numbers. Assign someone to update the shared reservation. Then check table capacity and nearby bookings. Guest information should support the decision: who is coming, when, with how many people and with what request relevant to the visit? Old or contradictory notes create work rather than good service.
Handle sensitive notes with extra care
A guest mentions an allergy or another particular need. That may matter to service but requires care in access, sharing and retention. A note is not a substitute for a conversation at the table or a proper kitchen check. Agree how staff confirm information and which wording to avoid. Review privacy and legal requirements for your specific business. A software feature is not blanket permission to store as many personal details as possible.
Do not turn past visits into assumptions
A guest record may help you find an earlier reservation. It does not prove that a past preference still applies. Ask politely when it matters instead of applying an old note without checking. Party size, seating preferences and contact route can all change. Bonzumo can make visit context visible; the current service decision remains with the team and guests. A good welcome feels attentive, not like an unsolicited inventory of old personal information.
Practise a complete arrival
In a demo, use a booking with a relevant seating request. Change its time, then let a different colleague handle arrival. Can they welcome the guest and find the current table without reading more personal data than the job requires? Hand the party to service and check whether the useful note arrives and is confirmed on site. That lets you judge the connection between guest context and floor plan from the perspective of a real visit.
A useful note helps at the decision point
A booking says the party would prefer a quiet seat. On Friday evening the originally considered table is still occupied. Reception now needs the current request, open areas and an understandable alternative. An old note should not be mistaken for a guarantee. Before offering another place, the colleague may ask whether the quiet area matters more than being seated immediately. Guest context then improves a conversation instead of becoming an invisible instruction that nobody checks with the people arriving.
Once the group is seated, the relevant server receives only the detail needed for this visit. A private phone number or the complete booking history will not help when taking a drink order. Decide during setup which roles see which part of a record and how updates are entered. Bonzumo connects guest and team contexts, while permissions need to fit actual tasks. A clear handover can prevent the same question being asked three times without spreading unnecessary personal information around the venue.
A demo can test this boundary deliberately. One person records the booking, another welcomes the party and a third takes over the table. Each should do the job without access to details they do not need. Then change the seating request and see whether the current version reaches the right person. The exercise produces concrete rules for entry, visibility, deletion or retention. Your business can have those rules reviewed professionally, instead of treating every free-text field as an invitation to store more information.



