Reservations and Waitlists

Using Guest Notes and Tags in Your Reservation System

A practical tag list for allergies, occasions, regulars and VIPs, who adds each tag, and how servers see notes before the table sits.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Why tags beat memory
  2. A tag list you can adopt this week
  3. Allergy tags need a stricter path
  4. Regulars, VIPs and loyalty
  5. How to write a note
  6. Getting notes to the floor before the table sits
  7. Example: one guest profile across three visits
  8. Training the team to tag well
  9. Clean the list every quarter
  10. Frequently asked questions
  11. References
Reservations and Waitlists: Using Guest Notes and Tags in Your Reservation SystemArticle coverRESERVATIONS AND WAITLISTSUsing Guest Notes andTags in YourReservation SystemAva for RestaurantsInsightsReservations and Waitlists: Using Guest Notes and Tags in Your Reservation SystemArticle coverRESERVATIONS AND WAITLISTSUsing Guest Notes andTags in YourReservation SystemAva for Restaurants

Key takeaways

  • Keep a short, fixed tag list; free-text notes are for details a tag cannot hold.
  • Allergy tags must always travel to the server and kitchen with the order, not just sit in the reservation book.
  • Write notes as facts a guest would be comfortable reading, never opinions.
  • Review tags in pre-shift and clean the list every quarter.

Why tags beat memory

Every restaurant has a host or server who remembers that the couple at table 12 always order the same wine and that the man booking for Friday has a shellfish allergy. When that person is off, the knowledge goes with them. Tags and notes in your reservation system turn that memory into something the whole team can use, on every shift, in every location.

Operators increasingly see technology as part of hospitality rather than a substitute for it: 65% say technology has a positive impact on the hospitality their restaurants provide[1]. Guest notes are the clearest example. Used well, they let a new server greet a regular by name and know about an allergy before the menus land.

A tag list you can adopt this week

Keep tags few and fixed so they are applied consistently. Twelve to fifteen is plenty for most rooms. Use free-text notes only for the detail a tag cannot carry.

Example guest tag list for a full-service restaurant
TagWho adds itWhenWho must see it
AllergyAnyone who hears it; host confirmsAt booking, confirmation reply or seatingServer, kitchen, manager
Dietary preferenceHost or serverAt booking or during the mealServer
Birthday / anniversary / occasionHost at bookingAt booking or replyServer, manager
Accessibility needHost at bookingAt bookingHost when assigning tables, server
High chair / boosterHostAt bookingHost, busser
RegularManagerAfter a set number of visitsHost, server
VIPManager onlyAny timeHost, server, manager, chef
Industry guestManagerAny timeHost, manager
Seating preferenceHostAt booking or after a visitHost
Late / no-show historySystem or hostAfter the visitHost lead and manager
Do not bookGeneral manager onlyAfter a documented incidentHost lead and manager

Rule of thumb: if a tag would change what someone does at the table, it belongs on the list. If it would only be interesting to know, leave it out.

Allergy tags need a stricter path

Allergy notes are the one tag where a miss can hurt someone. When federal allergen labeling law passed, eight major allergens accounted for 90% of food allergies and serious allergic reactions in the US[2], and sesame has since been added as the ninth major allergen[2]. Guests mention these at booking more often than restaurants expect, in a confirmation reply or a passing comment on the phone.

  1. Capture it exactly

    Write the allergen and the severity in the guest's words: "Tree nut allergy, carries an EpiPen", not "nuts?"

  2. Confirm at the table

    The server confirms the allergy with the guest when they sit. The reservation note starts the conversation; it does not replace it.

  3. Put it on the ticket

    The server enters the allergy on the order so it prints in the kitchen. A note in the reservation system alone never reaches the line.

  4. Manager check

    On allergy-tagged tables, the manager or chef confirms the dish is safe before it leaves the pass.

  5. Keep the tag

    Leave the allergy on the profile for the next visit, and ask again anyway.

Regulars, VIPs and loyalty

Recognition is a reason guests return. About 52% of consumers take part in a restaurant loyalty or rewards program, and 96% of those participants appreciate them[3]. Rewards membership influences dining choices for 41% of table-service diners, less than for delivery or quick-service customers[4], which suggests that in full-service rooms personal recognition does much of the work a points card does elsewhere.

Diners whose choices are influenced by a rewards program
Diners whose choices are influenced by a rewards programBar chart. Delivery customers: 61%; Quick-service patrons: 54%; Table-service diners: 41%.Delivery customersDelivery customers: 61%61%Quick-service patronsQuick-service patrons: 54%54%Table-service dinersTable-service diners: 41%41%Diners whose choices are influenced by a rewards programBar chart. Delivery customers: 61%; Quick-service patrons: 54%; Table-service diners: 41%.Delivery customersDelivery customers: 61%61%Quick-service patronsQuick-service patrons: 54%54%Table-service dinersTable-service diners: 41%41%

Source: National Restaurant Association, 2025[4]

Show the data
ItemValue
Delivery customers61%
Quick-service patrons54%
Table-service diners41%
  • Define "regular" with a number: for example, four visits in six months. Let the system or a manager apply it, not the host's impression.
  • Reserve "VIP" for people the manager has decided to treat differently, and note what that means: a call from the chef, a preferred table, a glass of something on arrival.
  • Write preferences as actions: "Prefers booth 4", "Likes the wine list brought with menus", "Decaf after dinner".
  • Note names of family members who often join, so the server can greet them.

How to write a note

Notes outlive the shift that wrote them. Write every note as if the guest could read it, because one day they may ask what you hold about them. Stick to facts that help you serve the guest.

Rewriting guest notes as useful, respectful facts
Instead ofWrite
"Difficult, complains a lot""Asked for a quieter table on last two visits"
"Big spender""Often orders from the reserve wine list"
"Old guy, slow""Prefers a table near the entrance; uses a cane"
"Nut thing??""Peanut allergy, severe, confirmed by guest 3/2"
"VIP!!!""VIP: owner's guest, manager to greet"
  • No health details beyond what the guest asked you to act on, such as an allergy or a mobility need.
  • No comments on appearance, age, ethnicity or religion.
  • No payment card numbers or full birthdates in free text.
  • Date any note that might change, such as a preference or a pregnancy-related dietary request.

Accessibility notes are practical, not personal: "needs step-free table, wheelchair user" lets the host plan. Restaurants are public accommodations under ADA Title III[5], so having a reliable way to record and act on these requests is part of serving guests well.

Getting notes to the floor before the table sits

A note nobody reads is useless. Build a routine that moves the information from the book to the people serving the table.

  1. Pre-shift: the host lead reads out tonight's allergies, occasions, VIPs and accessibility needs, with table numbers if assigned.
  2. Seating: the host tells the server about tags when seating, in a sentence: "Table 12, anniversary, shellfish allergy on the gentleman."
  3. Printed or on screen: if your reservation system and POS connect, show tags on the server's screen; if not, print a short tag sheet for the pass.
  4. After the meal: the server adds anything learned, such as a new preference or a corrected name spelling.

Tags also make your confirmations smarter. A guest tagged with an occasion can get a confirmation that acknowledges it, covered in our reservation confirmation message templates. If guests call to mention allergies or occasions, Ava can take those calls and log the detail on the reservation request so it reaches the team.

Example: one guest profile across three visits

Example: Maria books a table for two on a Thursday by phone and mentions it is her partner's birthday and that he cannot eat shellfish. The host adds the occasion tag and an allergy tag reading "Shellfish allergy (partner, Daniel), confirm at table." The confirmation text wishes Daniel a happy birthday. At pre-shift the host lead reads out table 9: birthday and shellfish. The server confirms the allergy when they sit, enters it on the ticket, and the kitchen plates a candle on the dessert.

After the meal the server adds a note: "Prefers a quieter table; liked the corner by the window." Six weeks later Maria books again online. The host sees the allergy and the preference, assigns the corner table, and the server greets them by name. On the third visit within six months, the manager adds the regular tag. Nothing here needed a loyalty program, a special budget or a memorable host. It needed three tags, one note and a pre-shift habit.

Training the team to tag well

Tags fail when only one person uses them. Make tagging part of the host and server job, with clear rules about who does what.

  • Hosts own booking-time tags: occasion, allergy, accessibility, high chair and seating preference.
  • Servers own after-meal notes: preferences learned at the table and corrections to names.
  • Managers own judgment tags: regular, VIP, industry and do not book.
  • New hires shadow a pre-shift tag briefing in their first week and add their first notes with a lead watching.
  • Spot-check once a week: pick five bookings with notes and ask whether the server knew about them before the table sat.

Praise good notes in pre-shift. A host who caught an allergy on a confirmation reply has done one of the most valuable things anyone will do that night.

Clean the list every quarter

Tag lists rot. Hosts invent new tags, notes pile up and old allergies sit next to outdated preferences. Once a quarter, a manager should merge duplicate guest profiles, delete tags nobody uses, review "do not book" entries, and check that allergy and accessibility notes still match what guests have told you. If you ever switch systems, clean tags before you migrate, not after; see how to switch reservation systems without losing bookings.

For occasion handling in depth, read how to handle special occasion reservations, and for table preferences see seating requests: booths, patios and window tables.

Frequently asked questions

What tags should a restaurant use in its reservation system?

Start with allergy, dietary preference, occasion, accessibility, high chair, regular, VIP, seating preference and late or no-show history. Keep the list short and fixed so tags are applied the same way by everyone.

Who should be allowed to add VIP or do-not-book tags?

Only managers. These tags change how guests are treated, so they need a named owner and, for do-not-book, a documented reason.

Is a reservation note enough for an allergy?

No. The server should confirm the allergy at the table and enter it on the order so it reaches the kitchen. The reservation note only starts the conversation.

Can guests see what notes we keep about them?

They may ask, so write every note as a respectful fact you would be comfortable showing the guest.

References

  1. National Restaurant Association (2026). Research Insight: The Future of Restaurant Technology (press release, November 5, 2026) (opens in a new tab) ↑

  2. US Food and Drug Administration (2004). Food Allergies (opens in a new tab) ↑

  3. National Restaurant Association (2024). Where operators plan to invest in tech (opens in a new tab) ↑

  4. National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry press release) (opens in a new tab) ↑

  5. US Department of Justice (ADA.gov) (2026). ADA Title III Regulations primer (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo