Skip to content
casa layer
Menu
Book a 20-minute demoBook a demo
Use cases

System type · PMS

The PMS stays. Recognition sits under the stack.

The PMS guest card is not one person across the house. Recognition sits under the stack, so a switch does not rebuild the guest.

  1. Problem

    The card is not the house record.

    Reservations live in the PMS, so teams treat its guest card as the person. That card knows what the property system was told. It does not know the outlet charge, the spa booking, or the stay that arrived on another address.

  2. Outcome

    The PMS stays.

    The property system stays the system of reservation. A switch becomes a new feed, not a rebuild of the person. Outlet and booking fragments resolve to the same guest.

  3. How Casa fits

    One feed among others.

    Casa Layer reads the PMS as one feed among others and reconciles the fragments into one Master Profile per real guest. The record 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.

Beside the property system

Guest Lookup overlay, Overview tab. Search, a match list, a sample guest summary, nights, lifetime value and contact, with a floating bubble.
Guest Lookup overlay, Notes tab. Reception and housekeeping notes for a sample guest.
Guest Lookup overlay, Reservations tab. Sample stays with status, dates and amount.
Guest Lookup overlay, Reviews tab. A name-match notice, then two sample reviews.

Guest Lookup reads the resolved guest beside the PMS. It is not a property-system screen. The guest in these shots is sample data, not a customer.

  • The PMS stays. Recognition sits under the stack.
  • The same person can arrive as several cards: another name, another email, another channel.
  • You issue credentials and can revoke them. Every connection live today reads only.
  • No rip-and-replace of the property system.

See it against the PMS you already run.

Book a 20-minute demo