The decision this workflow supports
A birthday or anniversary note can help staff understand a guest’s visit. It should not silently create an expectation of decorations, food, discounts or a particular table. Separate the occasion from any requested extra.
Put the review process in place
Collect the occasion only if the guest wants it noted, then record any specific request for staff review. Avoid asking for unnecessary personal details. Restaurant staff decide what can be offered and communicate any arrangements directly.
Worked example for your team
A fictional guest mentions an anniversary and asks whether a particular table could be considered. The assistant records the occasion only as a note and the table as a separate request. It should not add complimentary items or decorations that the guest never asked about. Ask the host reviewer to identify what needs a response and what is simply useful context. If the receipt says your celebration is arranged, revise it. A warm tone can coexist with precise wording about which details staff still need to confirm.
Sample wording to approve
“I can add an occasion note for the team and record any request you would like them to consider. I cannot promise decorations, complimentary items or a particular table.” This wording is a draft for the restaurant owner to approve before use.
Fields for the staff handoff
Staff need optional occasion note, specific requested extra, reservation reference, contact preference, and host owner. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.
Acceptance tests before use
An occasion note does not become a service promise. No unnecessary personal date is requested. Staff can distinguish the celebration from the requested extra. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.
Further reading
Catering inquiry value calculator ↗
Try Ava with your business’s public information ↗