Guests
From the first WiFi connection to dinner. Explore how individual modules can contribute to one shared guest record. Interactive simulation · fictional guest and data.
09:12 · WiFi
09:18 · Table Reservation
09:24 · Vini
Illustrative screens with sample data.
One guest. The whole visit.
From the first WiFi connection to dinner. Explore how individual modules can contribute to one shared guest record.
Interactive simulation · fictional guest and dataThis example assumes a verified profile link, a permitted purpose and the relevant consent. Records connect only within the authorized company scope.
- 01WIFI-001
A first connection through WiFi
Sofia signs into guest WiFi through the portal and verifies her email. In this example, it creates a verified link to her profile.
What may enter the record- Source: Hotel Aurora · Guest WiFi
- Verified contact: sofia@example.test
- Session started: 09:12
Event source
Marketing consent is a separate choice, not a connection requirement in this example.
- 02TABLE-024
A table for dinner
Using the same verified profile, she reserves a table for two. Reception and the restaurant can work with the same guest record.
What may enter the record- Restaurant: Aurora Bistro
- Today at 19:30 · 2 guests
- Status: confirmed in the simulation
Event source
Identity and permissions must confirm the link; a matching name alone is insufficient.
- 03VINI-018
An interest in red wine
During an identified example session, she opens red wines and a Barolo detail page. This is interest, not a confirmed purchase.
What may enter the record- Category: red wines
- Detail: Barolo DOCG
- Event: viewing the selection
Event source
This is a proposed measurement with relevant consent. Anonymous wine-list views are not automatically linked to a guest.
- 04SPA-006
A SPA booking
Sofia books a massage at 15:00. A connected booking system could contribute the service time and status to the shared history.
What may enter the record- Service: relaxation massage · 50 min
- Today at 15:00
- Source: illustrative SPA integration
Event source
SPA is an integration scenario on request, not a confirmed shipping module. No health information is shown.
- 05VISIT-024
Arrival at the restaurant
Staff mark the reservation as arrived. The record gains a confirmed restaurant visit within the same authorized organization.
What may enter the record- Place: Aurora Bistro · table 6
- Arrival: 19:27
- Confirmed by: restaurant staff
Event source
Arrival is confirmed by a reservation or staff. This does not track the guest’s physical movements.
- 06POS-042
Dinner and a wine order
An illustrative point-of-sale connection adds a red-wine order. Only an order record can confirm the selected product.
What may enter the record- Order: dinner for 2
- Wine: Barolo DOCG
- Source: illustrative POS integration
Event source
Orders and amounts require an agreed POS integration and the appropriate permissions.
- 07WIFI-002
A return visit, the same profile
The next day, Sofia verifies her connection again. Within permitted access, the team can see the context of earlier visits.
What may enter the record- 9 November · 09:10
- Linked to the existing profile
- Service and reservation history
Event source
Retention, access and deletion follow the configured purpose and business rules.
Understand the context of each visit.
Choose the modules you need. Together we will check which events and connections are available for your business.
Explore the options in a demoWho this is for
Managers and explicitly authorized staff reviewing guest records.
Daily workflow
Illustrative scenario — not a customer case study
The manager reviews a reservation-linked guest record only where the link and permission are verified. An employee sees only the agreed scope. Confirm fields, retention and access in the demo; anonymous QR browsing is not a marketing identity.
Preparation checklist
- 01
List each guest-data source, intended purpose and the fields staff actually need.
- 02
Demonstrate a permitted record with the manager and a restricted employee role.
- 03
Agree retention and correction responsibilities before relying on linked guest information.
Questions before you decide
Can every employee see every guest record?
Do not assume this. Confirm source links, exact fields, permissions, purpose and retention for your use case. Public Guest Guide content and anonymous QR menu visits are not private identified guest records.
Where can I verify the price and billing unit?
Use the published pricing page for listed modules and packages. HR is per organization; other listed modules are per establishment. Unlisted scope and integrations require a quotation, not an assumed package inclusion.
Availability and scope
Scope, actual availability and pricing require confirmation on request. No unverified integration or universal device compatibility is promised.
Limits to check
A reservation-linked record needs verified source and permissions. Anonymous QR activity and public guides are not identified CRM records; marketing remains coming soon.
Start simply.
Guests