How it works
From your scattered systems to one Master Profile per guest, in three weeks.
Casa Layer is built for hotels that cannot afford a long integration project, from an independent with returning guests to a group of thirty. Here is exactly how the record gets built, what we need from your systems and their vendors, and how fast.
We map your systems
We map every system that holds guest data: PMS, booking engine, POS, spa, F&B, OTAs, and any other source. You do not need to prepare anything. We work from a standard questionnaire and one call.
- System audit: we identify every data source and its format
- Integration plan: we propose which systems to connect first, based on where the most guest data lives
- Access approval: you review and approve the connection scope before anything is connected
We build the integration layer
Our engineers connect Casa Layer to each approved system. Where your PMS has an API, your vendor switches on access for your own account, scoped to what you approved: a support request, not a contract change or a new licence. Where a system has no API, we agree a scheduled export with that vendor in writing. We do not scrape, and we do not go around anyone’s terms to reach a database. Connecting your systems is our job, not yours: you do not need a technical person on your side.
- API connections to your PMS, POS, and booking engine, under credentials you issue and can revoke, reading only unless you grant more
- OTA feeds from Booking.com, Expedia, and others, taken through supported channels
- Historical data import: we back-fill guest history so day one is not a blank slate
We resolve guest identities
Once connected, the resolution engine runs across all your data. It matches records by name, email, phone, loyalty number, and behavioural signals, merges duplicates, and builds one verified Master Profile per guest.
- Fragments merge into one profile: every stay, cover, and treatment finally counts towards the same guest, so lifetime value is a real number
- Confidence scoring: every resolution carries a confidence level so your team knows when a match is certain versus probable
- Manual review queue: edge cases surface to your team for a human decision
Your team starts using it
The Master Profile surfaces alongside the systems your team already uses at the desk, so there is no new interface to train on. The context sits beside your PMS rather than inside it, and no part of your check-in flow comes to depend on us: if Casa Layer disappeared tomorrow, the desk would work exactly as it does today.
- No new login, no new tab: context surfaces in existing workflows
- Front-desk briefing: a daily arriving-guest list with key notes for each guest
- Team onboarding: a one-hour session for your front-desk team
Any agent or system connects
The same Master Profile is exposed through an open REST API and an MCP server, so any consumer can read it: a revenue agent, a concierge assistant, your CRM, a guest app. Three weeks from kickoff, your agents have something solid to run on.
- Open REST API and MCP server: one record serves your team, your CRM, a guest app, and any agent
- Confidence scoring and a GDPR consent ledger sit under every read
Minimal input required from your team.
We are built to handle the technical work, and we do not bill it separately: there are no integration fees, so connecting your systems is part of the licence rather than a project quote. Here is what we need from you.
A project sponsor
Typically the IT, CTO, or commercial director at the group, plus one operations contact per property. Needed for system access approvals and to answer questions about your data.
System access approval
API access to your PMS, POS, and booking engine, issued under your own vendor accounts and scoped by you. Most vendors enable it on a support request; we send you the exact wording to use.
A one-hour kickoff call
We walk through your systems, confirm the integration scope, and set a timeline.
One hour of team onboarding
For your front-desk team once profiles are live. We run the session; you just need the team in the room.
Your guest data is handled with care.
Encryption in transit and at rest
All data is encrypted using TLS 1.3 in transit and AES-256 at rest.
Access you scope, and can revoke
You decide what Casa Layer can reach in each system, under credentials you issue. Every connection live today reads only, and any write access an agent needs is granted per system by you, so nothing widens without your say-so.
UK GDPR compliance
For guest data, your hotel is the data controller and Casa Layer is the data processor, acting only on your written instruction. We are a controller only for our own website visitors and marketing contacts. Full DPA available on request.
You control the resolved data
Casa Layer holds the Master Profiles and you decide what is in them: you can delete any of them at any time, and your own systems stay the record whatever happens to this contract, because revoking the credentials you issued closes everything we can reach.
No training on your data
Your guest data is never used to train machine learning models or shared with other hotels.
Ready to walk through it with your systems?
In a 20-minute demo we will map the integration to your specific stack and show you what day one looks like.
No setup required on your side