Find the right guest before service
Use the booking date, party size and correct guest record to understand the intended visit. A reservation tag helps the team prepare; it does not replace checking current notes.
1. Know what a reservation tag means
Reservation tags may be selected by staff, derived from defined occasion expressions or chosen through a permitted guest workflow. They do not necessarily mean the same thing as persistent guest-profile tags.
2. Read service notes before promising anything
A tag such as birthday does not guarantee a celebration package or table assignment. Confirm the written request and staff instructions.
Distinguish guest notes from internal staff notes; guest edits must not overwrite the staff record.
3. Keep gifts, marketing and guest permissions separate
An occasion tag alone does not grant a Gift entitlement. Marketing via Connect still needs valid channel permission.
Treat allergies and health-related dietary declarations through the separate sensitive-data consent process, not a general occasion tag.
4. Record actual outcomes
If a guest visited, record attendance using the correct booking state. Do not count a cancelled visit or a message opened as proof of an in-venue celebration.
Keep notes factual, relevant and within the staff member's access rights.
A typical restaurant service example
A guest books for four and writes 'anniversary'. Staff review the reservation, see a matching occasion tag if the service is enabled, and prepare an appropriate welcome after checking the guest request.
Practical checklist
Use before each service.
- Confirm date, party size and the correct guest.
- Read the original request and current staff notes.
- Understand the source and meaning of tags.
- Check whether a celebration service was actually requested.
- Treat dietary requests through the dedicated consent workflow.
- Record attendance or cancellation accurately.
Exceptions and common mistakes
A tag may be absent if no approved pattern matched or the feature is not enabled. Do not add sensitive health labels as arbitrary CRM tags. See the occasion tag article for the current four-intent scope.
Review automatic occasion tags from notes
On configured deployments, Rezervem recognises four canonical reservation intents in Turkish and English: birthday, proposal, business meal and anniversary. A matching tag is a service preparation cue—not evidence that marketing consent, a gift or a permanent CRM profile segment was created.
Keep tag provenance separate from allergy consent
Staff-selected reservation tags, automatically matched occasion tags and guest-selectable tags can have different origins. Dietary and allergy declarations must follow their own explicit consent and access checks.