Products / Guest Portal & Profiles

Help guests manage their visit. Help your team prepare.

Give guests a place to see their bookings and make permitted updates. Keep useful visit history, preferences and service notes close to the next reservation, so the team can prepare a more thoughtful welcome.

A guest's upcoming visit with a requirements review and party summary
Prepare for the next visitCurrent product view · Example data

Built around the working day

Keep the guest and the host informed.

01

Give guests a useful next step

Make booking details, attendance confirmation, delay updates and available booking changes easy to find.

02

Keep the useful history

Bring previous visits, known preferences and relevant service context into the guest record.

03

Prepare with the right information

Let authorised staff review the details that matter for the upcoming service.

How the work connects

One visit, with the right view for everyone.

The guest checks the reservation, confirms attendance or reports a delay. The host sees the update with useful visit context before arrival.

The guest has a clear next action and the team can prepare the welcome.

An example workflow. Explore your restaurant’s setup in a demo.
Guest booking portal

Upcoming bookings, visit history, calendar export, attendance updates and booking-management links in one place.

Changes within your policies

Amendments and cancellation follow the reservation’s status and your restaurant’s configured rules.

Restaurant guestbook

Keep contact details, visit history, relevant notes, preferences and communication permissions together.

Optional visit preparation — ask about availability

Advanced dietary, accessibility and party-sharing features require separate venue setup. Recording a request does not confirm that the restaurant can accommodate it.

A closer look at the workflow

The guest’s update becomes a better prepared welcome.

Useful self-service gives the guest a next step and gives the restaurant current information. Keep requests, confirmed arrangements and previous visit context clear.

A fictional window-table preference and a separate staff note in Findsy
Useful context for the next welcomeCurrent product view · Example data
  1. 01

    The guest checks the visit

    Booking details and management links give the guest somewhere to check the reservation, confirm attendance or report a delay before arrival.

    Guest → booking update
  2. 02

    The host reads the context

    Authorised staff review the upcoming booking with relevant visit history and practical preferences. A recorded request stays distinct from an arrangement the restaurant has confirmed.

    Host → prepared service briefing
  3. 03

    The next visit starts with memory

    Keep relevant service notes and communication preferences in the guest record. Review what remains useful so the next welcome has context the team can act on.

    Restaurant → useful guest history

Getting started

Bring your restaurant. We will help with the setup.

Start with the workflow you need. Review your current records, configure the restaurant and rehearse with the team before launch.

01 / Bring to your demo

Your starting point.

  • The guest actions your restaurant wants to permit.
  • Your standard for practical notes and confirmed requests.
  • The people who need access to guest information.
02 / With the Findsy team

From setup to first service.

  • Review portal links, booking policies and staff roles.
  • Walk through guest updates and the corresponding host view.
  • Confirm any optional visit-preparation features individually.

Your practical questions

Know how it fits before you start.

Bring any venue-specific requirement to the demo so the team can confirm the available workflow and setup.

What can a guest do in the portal?

Guests can review bookings and visit history, use calendar export and access permitted attendance, delay and booking-management actions.

Does a guest request confirm the restaurant can accommodate it?

No. The restaurant still needs to review the request and confirm the arrangement where appropriate. Optional dietary and accessibility features require separate venue setup.

Who can see the guest record?

Access follows the configured staff roles and venue scope. Review who needs the information and how notes will be maintained during setup.

Does booking create marketing permission?

A booking and a marketing preference are separate. Communication permissions and exclusions need to be recorded and reviewed for the intended use.

Your 15-minute Findsy demo

Make the next welcome more personal.

Bring one current challenge. Walk through the relevant guest and team views, then discuss your starting point.

Book a 15-minute demo →
  1. 01

    Open a guest’s booking and permitted next actions.

  2. 02

    Review the useful information available to the host.

  3. 03

    Discuss your guest-note standard and access needs.