Developer documentation

Agentic hospitality

AI agents can only act on what a system of record exposes. Rooms and stays live in the PMS. Everything else a hotel sells or runs (spa, activities, kids’ clubs, tours, events, sunbeds, dining, rentals, transfers, retail, vouchers and packages) needs its own catalogue, live availability and booking record. Turneo is that system for services beyond the room, with a REST API and an MCP server that guest-facing and staff-facing agents can call.

Why

Why hotel agents need more than the PMS

Agents turn a guest's or a colleague's request into calls. What they can do is bounded by the systems behind them.

  • Every service is its own inventory

    A massage needs a therapist and a room, a cabana is a spot on a map, a transfer needs a vehicle and a driver, a voucher is redeemed weeks later. A PMS models rooms and stays, not these.

  • Agents can't guess availability

    A model that answers from memory will offer slots that are gone and prices that changed. An agent needs a system that answers live, and that holds a slot while the guest decides.

  • Bookings don't end at confirmation

    Someone accepts, assigns staff, reschedules, charges the room, marks it done and reports on it. The same system that sold the booking has to run it, for people and agents alike.

The stack

Two systems of record, side by side

The PMS and Turneo are peers: each owns its own records. Turneo posts charges to the guest's folio in the PMS and reads the guest's stay from it.

Full stack and diagram

Property management system (PMS)

The system of record for rooms and stays.

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

Turneo

The system of record for services beyond the room.

  • 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

Services

13 service families

Each has its own inventory model and its own limits. Each card says how many of the support matrix's 11 capabilities the public API covers, in full or with limits.

Support matrix

Agents

What guest and staff agents do with the API

Reading is free; anything marked “Needs a yes” books, charges or changes a booking, so the agent confirms the details with a person first.

Guest-facing agents

A concierge in the hotel's app, website chat, WhatsApp or ChatGPT that recommends and books.

  1. 01

    Find what fits

    Search the hotel's catalogue by date, category or free text, or ask for recommendations.

  2. 02

    Check live availability and price

    Dates first, then the time slots and prices for the guest's party on the chosen day.

  3. 03

    Hold, then confirmNeeds a yes

    A booking order holds the slot for 15 minutes while the guest says yes; confirming turns it into a booking.

  4. 04

    Take paymentNeeds a yes

    Email the guest a payment link, or charge the room when the hotel allows it.

  5. 05

    Report the real state

    Read the order back and tell the guest what it says: on hold, pending the provider, confirmed, paid.

Staff-facing agents

Assistants for the concierge desk, spa reception and operations, and reporting agents.

  1. 01

    See the day

    Bookings by date, service, status or payment status, with the staff and rooms assigned to each.

  2. 02

    Act on bookingsNeeds a yes

    Accept, reject, reschedule, reassign a therapist or vehicle, cancel and refund.

  3. 03

    Close the loopNeeds a yes

    Mark bookings completed or no-show, and record payments taken at the desk.

  4. 04

    Report

    One row per booking, retail sale or voucher sale with price, currency and commission for any date range, plus a feed of every change since your last sync.

Ways in

Connect your agent to Turneo