Skip to content
Reserver
Start free
Module · CRM

Your guests are yours. Forever.

Every reservation builds a complete profile: visits, frequency, birthdays, allergies and notes. Segment, filter, and — when you want — export to CSV in three clicks.

Available on Free Pro Plus
  • Complete per-guest profile with full reservation history
  • Tags live on each reservation, reusable as campaign filters
  • CSV-exportable any time
  • GDPR-compliant, with unsubscribe management
Guest record

A profile your host actually wants to check.

Each guest has a record with name, email, phone, language, internal notes, and a timeline of every booking. Visit count, frequency, cancellation rate and no-show rate. When they walk in, your team knows if it’s the first time or the tenth.

  • Full reservation history (date, service, zone, party).
  • Real metrics: visits, frequency, cancellations, no-shows.
  • Internal notes visible only to your team.
  • Duplicate detection by email and phone.
Screenshot placeholder
Segmentation

Filter like a spreadsheet. With meaning.

Find every guest who came in the last 12 weeks and has no future booking. Or those whose birthday is this month. Or guests with a "gluten-free" tag on past reservations who haven’t been in 3 months. Filters combine and save as segments.

  • Filter by last visit, visit count, language, birthday.
  • Filter by tags present on the guest’s reservations.
  • Saved segments: reusable as campaign audiences.
  • Export per-segment to CSV or push directly to a campaign.
Screenshot placeholder
Tags on the reservation

Tags live on the reservation, not on the guest.

In Reserver, tags are placed on each reservation, not on the guest. "Gluten-free", "birthday", "quiet table", "hotel guest" — operators set them as the booking arrives or during service. The guest record itself doesn’t carry stuck-on tags, but campaigns can still filter by tags appearing across a guest’s reservations. The history stays honest: each visit keeps its context.

  • Free-form and predefined tags per restaurant.
  • Visible on the day’s desktop next to each reservation.
  • Reusable as audience criteria in marketing campaigns.
  • Not aggregated on the guest record: each reservation keeps its own context.
Screenshot placeholder
Privacy and GDPR

Built to comply, not to cut corners.

GDPR requires controlled data, access and deletion rights, and clear marketing consent. Reserver ships with all of that: a guest can request their data or deletion and your team resolves it in one click. Marketing consent is opt-in, not opt-out.

  • Right of access: complete profile export as PDF.
  • Right to erasure: logical delete with reservation anonymisation.
  • Separate marketing consent per channel (email/SMS).
  • Access audit: who viewed which record and when.
Screenshot placeholder
Portability

If you leave, you leave with everything.

The CRM exports to CSV in one click: name, email, phone, tags, first visit, last visit, reservation count. No locked fields, no watermarks. Your list is yours.

Screenshot placeholder
Benefits

What happens when CRM lives inside the booking system

Zero manual transfers

No exporting from one place and importing into another. The reservation feeds the record.

Honest per-guest metrics

Visits, frequency, favourite reservation type — computed from what we actually know: the bookings.

Campaigns on real data

When you send an email, the system knows who’s receiving it and why.

Frequently asked

What people usually ask

Can I import my existing guest database?

Not yet. Reserver doesn’t ship a bulk-import or migration tool: your own guest database builds from signup onwards, fed by direct bookings, the widget and marketing email capture. Keep your previous list exported in case you need it as reference.

What happens when a guest asks to be deleted?

Their record is anonymised: past reservations remain (you need them for accounting), but personal data is replaced with a generic identifier. That’s the GDPR "right to erasure" applied correctly.

Do operators see everything?

Depends on the role. On Plus, you configure roles with granular access (see guests yes, see payment data no). On Pro, all operators see the same as the owner.

How do you detect duplicates?

Exact email match, exact phone match, and fuzzy name + phone match. If we detect likely duplicates we suggest the merge; you approve.
Ready to try it

Stop lending your guest list to other people.

Run your CRM in your own system. Export whenever. No commissions in between.