All chapters

Guest database

In the guest database VidiReserve automatically collects a profile for every guest who books with you — with contact details, visit history and preferences. This lets you recognise regulars, take allergies into account and prepare specifically for guests. You open the database via Guests in the sidebar.

Profiles

Guest profiles are created automatically from reservations; via Import from reservations you add existing data afterwards, and with Create Guest you record a guest by hand. Each profile shows visits, no-shows, the last visit, reviews and the birthday. You mark particularly valuable guests as VIP with a click on the star.

Tags & allergies

With Tags you group guests freely (e.g. regular, wine lover). Under Allergies / intolerances you record relevant notes — these appear as a warning in the reservation, so that kitchen and service are prepared. In the Internal notes you keep preferences and particulars that only your team sees.

Allergies, intolerances and diets such as halal or kosher are specially protected data (Art. 9 GDPR). When a guest enters them online — on your booking page, in the widget, for an event or a group request — they expressly consent to you using the information for their visit and storing it in the guest database for future visits. The consent appears in the reservation's change log (“Consent to allergy/diet information given”, followed by the version and the form). The information itself is not shown there. If a guest withdraws their consent, delete the information in the reservation and in the guest profile. Whatever your team records itself — by phone, in the back office or in the partner app — is your responsibility as the business.

History & search

Each profile keeps the complete reservation history including notes. Using the search field and the filters (tags, minimum number of visits, VIPs only, with review, flagged) you quickly find the right guest. A change log documents who changed what on the profile and when.

Not-welcome flag

If a guest has repeatedly not shown up, behaved badly or left a bill unpaid, you can mark them as not welcome in the guest profile: in the Not-welcome flag card, click Mark as not welcome, choose a reason (no-show, behaviour, payment, other) and add a short note if needed. With Remove flag you take it back there at any time. Anyone allowed to edit the guest database may set and remove it — including the front desk.

From then on every booking whose email address or phone number matches the profile carries a red Not welcome badge: in the reservation list, in the header of the booking details, on the dashboard, in the day view, in the month calendar, in the live floor plan, on the waitlist, on group requests, in an event's booking list and in the name suggestions when creating a booking. Phone numbers are matched regardless of how they are written — "+49 170 …", "0049 170 …" and "0170 …" count as the same number; numbers without a country code are assigned to your business's country. Everyone on your team who may see bookings sees the badge. The reason and the note, however, are only shown in the guest database. Emails do not mention the flag — you see it in the back office (badge and attention needed).

Under Settings → Bookings & Rules ("Booking" tab) you can additionally switch on Never auto-confirm bookings from flagged guests. Such a booking then arrives as a request even with automatic confirmation, marked "attention needed", and you decide yourself whether to confirm or reject it. Nothing is ever rejected automatically. Bookings your team creates itself (back office, partner app, walk-in) are not affected.

The guest learns nothing about the flag itself: they receive the same texts as any other guest. They only see that their booking is handled as a request and receive the usual acknowledgement — if automatic confirmation is otherwise on at your business, they may notice that difference.

Data protection: a not-welcome flag is information about a person. Keep notes factual and brief — under Art. 15 GDPR the guest can request access to the data stored about them and would then get to read the note. Do not enter details about health, religion, origin, beliefs or other special categories (Art. 9 GDPR). The flag expires automatically after 24 months and is deleted together with its note; the change log only keeps when it was set, removed or expired. The CSV export does not contain the flag.
Guest data is personal data: handle it confidentially and in line with the GDPR. You can find further guidance in our public data protection guide.

From reservations, the waitlist and the guest database you can write a guest a message directly at any time — the conversation ends up back in the messages area.

Exporting contacts as CSV

Next to the filters sits the CSV export. It downloads exactly the selection the list is showing — search term, tags, minimum visits, "VIP only" and "with review" apply to the file unchanged. It contains first name, last name, email, phone, VIP, tags, visits, last visit and the internal notes. The file opens in Excel or Numbers without the import wizard; at most 10,000 rows are written per export.

Because such a file is a complete address list of your guests, every export is logged (business, user, number of rows). Keep the file encrypted or at least access-protected, do not send it by unencrypted email, and delete it once its purpose is fulfilled — this data minimisation is exactly what the GDPR requires.