The person reserving a table often does not yet have every name and menu choice. Details arrive later in several messages: one guest chooses a different menu, someone changes a companion’s name, and another adds a dietary request.
If those updates stay in correspondence, the team has to put them together again before the event. 100LICA connects guest details to reserved seats and lets guests update existing seats through secure reservation access.
Updating an existing reservation
Changing details is different from buying extra seats. Adding a name or menu choice applies to seats already included in the reservation. It does not automatically increase the guest count or extend the reservation to a neighbouring table.
This flow suits groups organised by one person. Instead of staff copying every new message, details can be added to the existing reservation using the options available for that event.
A menu choice is different from a note to the kitchen
Menu selection should use the options the organiser has defined in advance. A dietary note needs additional attention: submitting a request is not confirmation that the kitchen can safely fulfil it.
For allergies and other sensitive needs, organisers should have a clear confirmation process with responsible staff. Do not request medical documents or information that is unnecessary to provide the service. Access should be limited to staff who need it for their work.
An update deadline makes preparation easier
The kitchen needs a usable overview, and sales needs a process for last-minute changes. Organisers should set a deadline for guest updates and say whom to contact afterwards.
Before the event, check several reservations from start to finish: seat counts, names, menus and agreed exceptions. The goal is to make the information needed for service accurate and available to authorised staff, rather than fill every field at any cost.
To see this flow from the guest’s and team’s perspectives, email sales@100lica.rs.
