← Guides RESTAURANT

Restaurant CRM Guest Segments, Lists and Levels Explained

Distinguish guest tags, curated lists, manual segments, levels and calculated smart segments before acting on the data.

REZERVEM CRM · WITH MANAGER · Rezervem

How should a restaurant group its guests?

Use a guest tag for a specific service label, a list for a defined audience, a manual segment for an operator-maintained classification and a level for a separate guest ranking. Rezervem CRM supports these different groupings alongside Rezervem Manager. Where the feature and data are available, smart segments also summarize behavior using predefined calculations rather than manually assigned labels.

A host might identify a frequent terrace guest, while a marketing team wants to understand guests who have not returned for months. These are different questions and should not be forced into one permanent VIP label.

1. Decide what question the group must answer

Start with a use case: preparing tonight's tables, reviewing a loyalty initiative or identifying a potential win-back audience. Write the purpose, owner and expiry or review date. Do not create labels that reveal unnecessary sensitive characteristics.

2. Separate guest tags from lists and levels

Tags, segments and lists are managed as different categories in the product, and guest levels have their own management area. Check the classification type before editing or exporting. A guest list is not a legal record of permission to receive an advertisement.

3. Understand smart-segment refresh timing

Rezervem's code defines calculated groups for visit frequency, recency, meals, spending and behavior. These use a periodically calculated guest activity snapshot; they are not a promise of instant updates after every booking. Availability can depend on enabled features and completed calculations.

4. Check data quality before trusting a segment

A spend-related group depends on usable transaction amounts; a missed-visit group depends on reliable arrival recording. If the venue has not consistently marked actual visits, avoid treating the segment output as a complete assessment of an individual.

5. Exclude guests with future reservations when planning win-back

A guest who has already booked next Friday should not be invited as though they disappeared. The implemented recency catalog excludes future bookings for selected win-back groups; verify the final audience before communication.

How Rezervem divides the responsibilities

Rezervem CRM organizes guest information and groupings alongside Rezervem Manager. Connect handles eligible WhatsApp campaign delivery. Neither a smart segment nor a manually created list is proof of consent for a marketing message.

Review results with the service team

Each month, sample a few members in every important group and compare their recorded bookings with actual visits. Adjust manual group membership if the purpose changed; do not claim that the fixed smart-segment rules are freely editable.

Audit a segment against real visits

One example helps explain the difference. A 'quiet table request' is service context for a specific booking; a manually maintained 'event invitation list' is a curated group; a calculated 'not visited in 180 days' segment is a result of recorded activity. None of these is automatically the same as a marketing permission. The recipient and message purpose must be assessed again before a campaign.

Smart segments can also be unavailable when the required underlying data is incomplete. Instead of guessing what a missing total means, the manager should check the calculation status and whether arrival or spending records meet the needed quality conditions. Use a manual review when the data is too thin for an automated interpretation.

A practical monthly audit samples three guests from an important segment. Check actual booking dates, visit outcomes, the presence of a future reservation and the last calculation time. Record any exceptions rather than silently adjusting a predefined rule.