Guest-facing agents and apps
AI concierges, ChatGPT and other assistants, the hotel's app and website, messaging.
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.
Channels
AI concierges, ChatGPT and other assistants, the hotel's app and website, messaging.
Concierge and front-desk assistants, operations agents, reporting and BI.
Guest requests · Staff questions and tasks
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
Each call goes to the system that owns the record
Systems of record
via the PMS's own API
The system of record for rooms and stays.
Owns
Oracle OPERA Cloud, Mews, Apaleo, Rentlio
Charges to the room folio; stay details for personalisation
via Turneo API or MCP server
The system of record for services beyond the room.
Owns
Turneo API, Turneo MCP server, Turneo Elements
via each vendor's API
Whatever else a hotel already runs as a system of record.
Owns
Turneo exchanges data directly with
Connected to Turneo
Card payments
Takes card payments for Turneo bookings.
Owns
Stripe, Square
Bookings and guest details
Receives every booking and the guest's details.
Owns
Salesforce, Microsoft Dynamics, Segment
Partner availability and bookings
Local partners keep their own reservation system; Turneo stays in sync with it.
Owns
Rezdy
Connections
Every arrow in the diagram, with what flows along it and the interface it goes through.
Rules for agents
The stack only stays correct if agents treat it as the source of truth. These rules apply whichever framework you build with.
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.
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.
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.
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.
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.
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
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.
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" --> suppliersNext