Agentic Hospitality

The agentic hotel stack

An agentic hotel needs two systems of record side by side. The PMS owns rooms and stays. Turneo owns the services guests book beyond the room: spa, activities, tours, events, sunbeds, dining, rentals, transfers, retail, vouchers and packages. Agents sit above both, behind an agent layer that checks who is asking and gets approval before anything that books, cancels or charges.

Last checked 2026-11-19. The same data is available as JSON and as Mermaid source.

The systems an agentic hotel runs on. The PMS is the system of record for rooms and stays; Turneo is the system of record for the services guests book beyond the room. Agents sit above both, behind an agent layer that handles identity, approvals and audit.

Channels

  • Guest-facing agents and apps

    AI concierges, ChatGPT and other assistants, the hotel's app and website, messaging.

  • Staff-facing agents and tools

    Concierge and front-desk assistants, operations agents, reporting and BI.

Guest requests · Staff questions and tasks

Agent layer

Agent layer

Your orchestration, or Turneo's own agents. Decides which system to ask, checks who is asking, gets approval before anything that books, cancels or charges, and logs what it did.

Owns

  • Conversation state
  • Approvals and the audit trail of agent actions

Each call goes to the system that owns the record

Systems of record

via the PMS's own API

Property management system (PMS)

The system of record for rooms and stays.

Owns

  • Room inventory, rates and room reservations
  • Stays and the guest's stay context
  • The room folio (the guest's bill)

Oracle OPERA Cloud, Mews, Apaleo, Rentlio

Charges to the room folio; stay details for personalisation

via Turneo API or MCP server

Turneo

The system of record for services beyond the room.

Owns

  • The catalogue of experiences and services, with options and prices
  • Live availability and capacity, including the staff and resources a booking needs
  • Booking orders and bookings, from request to completion
  • Retail stock and gift vouchers, from sale to redemption
  • Local partners' experiences, sold with commission
  • An activity feed of every booking change

Turneo API, Turneo MCP server, Turneo Elements

via each vendor's API

POS and specialist systems

Whatever else a hotel already runs as a system of record.

Owns

  • Restaurant checks and outlet sales (POS)
  • Accounting and other specialist records

Turneo exchanges data directly with

Connected to Turneo

  • Card payments

    Payment gateway

    Takes card payments for Turneo bookings.

    Owns

    • Card payments and payouts

    Stripe, Square

  • Bookings and guest details

    CRM and CDP

    Receives every booking and the guest's details.

    Owns

    • Guest marketing profiles and history across channels

    Salesforce, Microsoft Dynamics, Segment

  • Partner availability and bookings

    Supplier reservation systems

    Local partners keep their own reservation system; Turneo stays in sync with it.

    Owns

    • Local partners' own availability and bookings

    Rezdy

Connections

How the systems connect

Every arrow in the diagram, with what flows along it and the interface it goes through.

Guest-facing agents and apps → Agent layer
Guest requests
Staff-facing agents and tools → Agent layer
Staff questions and tasks
Agent layer → Property management system (PMS)
Stay context, room availability, room reservationsThrough: the PMS's own API
Agent layer → Turneo
Search, availability, orders, bookings, activityThrough: Turneo API or MCP server
Agent layer → POS and specialist systems
Checks, sales and anything else they ownThrough: each vendor's API
Turneo ↔ Property management system (PMS)
Charges to the room folio; stay details for personalisationThrough: Turneo's PMS integrations
Turneo → Payment gateway
Card paymentsThrough: Turneo's payment integrations
Turneo → CRM and CDP
Bookings and guest detailsThrough: Turneo's CRM integrations
Turneo ↔ Supplier reservation systems
Partner availability and bookingsThrough: Turneo's supplier integrations

Rules for agents

What every agent on this stack should do

The stack only stays correct if agents treat it as the source of truth. These rules apply whichever framework you build with.

  1. 01

    The agent asks; the systems decide

    Availability, prices and booking state come from the system that owns them, never from the model's memory or an earlier answer in the conversation.

  2. 02

    Ask the owner

    Rooms, stays and the folio: the PMS. Services beyond the room: Turneo. Restaurant checks and outlet sales: the POS. An agent that needs all three calls all three.

  3. 03

    Check again right before booking

    Read availability and price immediately before creating a booking order. A slot shown ten minutes ago may be gone, and the order is what holds it.

  4. 04

    Get a yes before booking, cancelling or charging

    Show the guest, or the member of staff, the exact service, time, party and price, and act only on their confirmation. Reading needs no approval; changing something does.

  5. 05

    Report the state you were given

    A booking order on hold is not a confirmed booking, a booking can wait for the provider to accept it, and a confirmed booking is not necessarily paid. Tell the guest what the system returned, not what you expect.

  6. 06

    Scope everything

    A Turneo API key is scoped to one partner account. Scope each agent session to one hotel and one guest, and share personal details only with the people who need them.

Machine-readable

Use the diagram in your own docs

The stack as Mermaid source, generated from the same data as the diagram above. Paste it into any Mermaid renderer, or fetch the JSON for systems, ownership and connections.

stack.json
Agentic hotel stackmermaid
flowchart TD
  subgraph channel["Channels"]
    guest_agents["Guest-facing agents and apps"]
    staff_agents["Staff-facing agents and tools"]
  end
  subgraph agent["Agent layer"]
    agent_layer["Agent layer"]
  end
  subgraph record["Systems of record"]
    pms["Property management system (PMS)"]
    turneo["Turneo"]
    other_records["POS and specialist systems"]
  end
  subgraph connected["Connected to Turneo"]
    payments["Payment gateway"]
    crm["CRM and CDP"]
    suppliers["Supplier reservation systems"]
  end
  guest_agents -- "Guest requests" --> agent_layer
  staff_agents -- "Staff questions and tasks" --> agent_layer
  agent_layer -- "Stay context, room availability, room reservations" --> pms
  agent_layer -- "Search, availability, orders, bookings, activity" --> turneo
  agent_layer -- "Checks, sales and anything else they own" --> other_records
  turneo <-- "Charges to the room folio; stay details for personalisation" --> pms
  turneo -- "Card payments" --> payments
  turneo -- "Bookings and guest details" --> crm
  turneo <-- "Partner availability and bookings" --> suppliers

Next

Build on the Turneo side of the stack