--- title: "Your PMS was built before anyone said the word API." url: "https://referent.app/industries/travel-hospitality" description: "Referent connects to the PMS, booking engine and channel manager running your properties, including the ones with no connector. Occupancy, rates and guest answers from live data." --- Travel & Hospitality # Your PMS was built before anyone said the word API. Reservations live in one system, rates in another and the real occupancy picture in a spreadsheet somebody rebuilds every morning. Referent connects to all of them and answers across properties, in seconds. [Book a demo](/demo)[How it connects](#how-it-works) 0104How it connects ## It connects where your interface already connects. It maps the queries, the actions and the endpoints behind the interface, then connects at that level. Nothing to rebuild, nothing to migrate. Your team ### Questions and work, in plain language Chat, Slack, Teams or Telegram. Ask for a number, a report, a draft or a status. No new tool to learn. Referent ### The layer that understands your systems Maps queries, actions and endpoints. Answers from live data with citations back to the source. Executes the work on top: pulls the numbers, builds the report, drafts the follow-up. Your software ### Property systems that never opened up A PMS from a vendor that barely supports it, a booking engine with a closed interface, a channel manager that only exports and the operational spreadsheets each property keeps on the side. * Legacy PMS * Booking engine * Channel manager * Property spreadsheets * POS exports ### Standard tools too The 50+ connectors everyone advertises are included. That part is commodity. The hard systems are the point. * Microsoft 365 * Google Drive * Slack * Jira * Salesforce This is not RPA. No screen reading and no bots clicking buttons. Referent connects at the data layer, so a UI change does not break it. 0204Use cases ## Four answers that today require calling each property. Cross-property questions become one question, asked once. 01Portfolio occupancyOccupancy and pace across every property at onceToday somebody phones each property or waits for the consolidated report. Referent reads each PMS directly and answers the portfolio-level question in seconds.02Rates and availabilityRate and availability checks against live inventoryWhat is actually on sale, where, and at what price, straight from the booking engine and channel manager rather than a snapshot taken this morning.03Guest historyGuest and booking history without the system tourFront desk and reservations staff ask in plain language instead of navigating four screens. Answers come with a citation to the reservation record.04Daily ops reportThe daily operations report, produced on scheduleArrivals, departures, occupancy, revenue and exceptions, compiled across properties in the format management already reads, without anyone exporting anything. Live sessionPMS · 6 properties You: Occupancy and pace across all six properties for next weekend. * read 6 property PMS * compared against the same weekend last year Referent The portfolio is at 74% for Saturday, four points ahead of last year. One property is dragging: 51% against 79% for the rest. Portfolio occupancy 74% Pace vs last year +4 pts Strongest property 91% Weakest property 51% PMS · Occupancy · Next weekend You: Send that to the revenue call every Tuesday at 09:00. * scheduled · Tuesdays 09:00 * recipients set Referent Scheduled. It reads each property directly, so nobody has to phone round before the call. 0304Deployment ## Days, not months. There is nothing to migrate and nothing to rebuild, so the timeline is short by construction. 1. 01 ### Map the system We watch how your existing app talks to the system underneath and document the queries, actions and endpoints behind it. 2. 02 ### Connect at the data layer Referent connects directly at that level. No connector to build, no migration, no change to the software your team uses every day. 3. 03 ### Validate with your team The people who know the process check the answers against reality. Permissions are mapped to the roles you already have. 4. 04 ### Live Your team asks in plain language and gets answers from live data, with citations. Scope grows from there. Reference deployment ### A mid-market manufacturer, on a custom ERP. Mapped, connected and in production in under a week, on a system no AI product could reach. System Custom ERP Time to production One week Migration required None 0404Security ## Built to clear the security review, not to argue with it. Most AI proposals die in IT. These are the properties that get the conversation past that point. * 01 ### Single-tenant isolation Your deployment runs in its own environment. Nothing is shared with another customer. * 02 ### Zero-retention models Prompts and responses are not stored by the model providers and are never used for training. * 03 ### Your permissions, mirrored Referent respects the access rules your systems already enforce. Nobody sees what they could not see before. * 04 ### No data duplication Answers are fetched from the live system at query time. We do not build a second copy of your database. * 05 ### GDPR European data protection requirements are part of the deployment, not an afterthought. * [ Read the security detail](/security) ## See it running on a system like yours. [Book a demo](/demo)[Sign in](https://dash.referent.app/onboarding) ## Be the first to hear about Referent news.