{"name":"The agentic hotel stack","description":"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.","url":"https://www.turneo.com/developers/agentic-hospitality/stack","updated":"2026-11-19","layers":[{"id":"channel","name":"Channels","summary":"Where guests and staff talk to agents. They own no records."},{"id":"agent","name":"Agent layer","summary":"Turns intent into calls, with identity, approvals and audit. Never the system of record."},{"id":"record","name":"Systems of record","summary":"The systems that decide what is true."},{"id":"connected","name":"Connected to Turneo","summary":"Systems Turneo exchanges data with directly."}],"systems":[{"id":"guest-agents","name":"Guest-facing agents and apps","layer":"channel","summary":"AI concierges, ChatGPT and other assistants, the hotel's app and website, messaging."},{"id":"staff-agents","name":"Staff-facing agents and tools","layer":"channel","summary":"Concierge and front-desk assistants, operations agents, reporting and BI."},{"id":"agent-layer","name":"Agent layer","layer":"agent","summary":"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"]},{"id":"pms","name":"Property management system (PMS)","layer":"record","summary":"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)"],"examples":["Oracle OPERA Cloud","Mews","Apaleo","Rentlio"]},{"id":"turneo","name":"Turneo","layer":"record","summary":"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"],"examples":["Turneo API","Turneo MCP server","Turneo Elements"]},{"id":"other-records","name":"POS and specialist systems","layer":"record","summary":"Whatever else a hotel already runs as a system of record.","owns":["Restaurant checks and outlet sales (POS)","Accounting and other specialist records"]},{"id":"payments","name":"Payment gateway","layer":"connected","summary":"Takes card payments for Turneo bookings.","owns":["Card payments and payouts"],"examples":["Stripe","Square"]},{"id":"crm","name":"CRM and CDP","layer":"connected","summary":"Receives every booking and the guest's details.","owns":["Guest marketing profiles and history across channels"],"examples":["Salesforce","Microsoft Dynamics","Segment"]},{"id":"suppliers","name":"Supplier reservation systems","layer":"connected","summary":"Local partners keep their own reservation system; Turneo stays in sync with it.","owns":["Local partners' own availability and bookings"],"examples":["Rezdy"]}],"links":[{"from":"guest-agents","to":"agent-layer","label":"Guest requests"},{"from":"staff-agents","to":"agent-layer","label":"Staff questions and tasks"},{"from":"agent-layer","to":"pms","label":"Stay context, room availability, room reservations","via":"the PMS's own API"},{"from":"agent-layer","to":"turneo","label":"Search, availability, orders, bookings, activity","via":"Turneo API or MCP server"},{"from":"agent-layer","to":"other-records","label":"Checks, sales and anything else they own","via":"each vendor's API"},{"from":"turneo","to":"pms","label":"Charges to the room folio; stay details for personalisation","via":"Turneo's PMS integrations","both":true},{"from":"turneo","to":"payments","label":"Card payments","via":"Turneo's payment integrations"},{"from":"turneo","to":"crm","label":"Bookings and guest details","via":"Turneo's CRM integrations"},{"from":"turneo","to":"suppliers","label":"Partner availability and bookings","via":"Turneo's supplier integrations","both":true}],"mermaid":"flowchart TD\n  subgraph channel[\"Channels\"]\n    guest_agents[\"Guest-facing agents and apps\"]\n    staff_agents[\"Staff-facing agents and tools\"]\n  end\n  subgraph agent[\"Agent layer\"]\n    agent_layer[\"Agent layer\"]\n  end\n  subgraph record[\"Systems of record\"]\n    pms[\"Property management system (PMS)\"]\n    turneo[\"Turneo\"]\n    other_records[\"POS and specialist systems\"]\n  end\n  subgraph connected[\"Connected to Turneo\"]\n    payments[\"Payment gateway\"]\n    crm[\"CRM and CDP\"]\n    suppliers[\"Supplier reservation systems\"]\n  end\n  guest_agents -- \"Guest requests\" --> agent_layer\n  staff_agents -- \"Staff questions and tasks\" --> agent_layer\n  agent_layer -- \"Stay context, room availability, room reservations\" --> pms\n  agent_layer -- \"Search, availability, orders, bookings, activity\" --> turneo\n  agent_layer -- \"Checks, sales and anything else they own\" --> other_records\n  turneo <-- \"Charges to the room folio; stay details for personalisation\" --> pms\n  turneo -- \"Card payments\" --> payments\n  turneo -- \"Bookings and guest details\" --> crm\n  turneo <-- \"Partner availability and bookings\" --> suppliers"}