Role · General Manager

The house remembers the same guest.

A returning guest should not be a stranger at check-in. The record sits under the stack, so the house can recognise the same person.

Problem
The house remembers in pieces.
A guest who stayed last year should not be a stranger at check-in, and a preference from the bar should still be true at the desk. The property-system card only knows what that system was told.
Outcome
The same person across the house.
The desk and the outlets read one guest. Sister properties can read the same person without sharing one database. The PMS stays.
How Casa fits
Under the stack. No second dashboard.
Casa Layer assembles one record per real guest from the property system and the outlets. The Master Profile sits under the stack. You decide what Casa Layer can do in each system, and you can revoke it. Every connection live today reads only.

Recognition at check-in

Guest Lookup at the desk: the person the house already knows, beside the property system. The guest in these shots is sample data, not a customer.

The house stops remembering in pieces.
A PMS switch does not rebuild the person.
No second dashboard for the general manager.
You issue credentials and can revoke them. Every connection live today reads only.

See it against the house you already run.