Data and integrations

Give the agent a complete view of each hotel.

RealM connects hotel performance, property settings, and available market context so the pricing engine and AI agent can work from the same evidence. The PMS remains the system of record.

Read from your hotel

  • Reservations
  • Occupancy
  • Inventory
  • Cancellations
  • Booking pace
  • Room types
  • Rate plans
  • Restrictions

Available market context

  • Competitor rates
  • Public availability signals
  • Events
  • Holidays
  • School breaks
  • Regional demand signals
  • Regional benchmarks

Created inside RealM

  • Daily snapshots
  • Forecasts
  • Recommendations
  • Manager approvals
  • Overrides
  • Published rate changes
  • Measured outcomes

Misterbooking integration

In development

RealM's first PMS integration is being developed for hotel groups using Misterbooking. The first phase focuses on trustworthy read access and shadow recommendations. Controlled updates will follow only after data quality, policy controls, approval, acknowledgement, and rollback have been validated.

Additional PMS integrations will be introduced based on customer demand.

Integration scope

Exactly what RealM reads and what it can change.

RealM needs enough read access to understand demand, but its write access is intentionally limited. It cannot alter reservations, guest records, invoices, inventory counts, or distribution settings.

Read from the PMS

  • Reservations

    The booking curve for every future date is built from creation dates, not just stay dates.

  • Cancellations and missed arrivals

    Without these the forecast overstates demand on exactly the dates that matter most.

  • Inventory and availability

    Remaining rooms by type set the constraint the optimiser solves against.

  • Room types

    Rates are recommended per room type, and the relationships between them are held consistent.

  • Rate plans and codes

    Determines which rate the platform is permitted to move and which it must leave alone.

  • Existing restrictions

    Minimum stay and closed to arrival rules already in place are respected, not overwritten.

Write back to the PMS

  • Rate updates

    The core action: a new price for a room type on a date, published after it clears the policy layer.

  • Restriction updates

    Minimum length of stay and arrival rules, where the hotel has enabled them. Optional.

  • Nothing else

    No changes to reservations, guest records, invoices, inventory counts or distribution settings.

Every write is logged with the recommendation that produced it, the person who approved it where approval applied, and the PMS response. Failed updates are reported rather than failing silently.

External signals

The market context behind a recommendation.

Each external source is optional and configured by property. When a source is unavailable, RealM shows which inputs were used rather than implying that the recommendation had more context than it did.

Competitor rates

Published rates and availability across a comparable hotel set, supplied through approved market data sources where they are enabled.

Rate by room type and date, availability signals, parity across channels

Events and congresses

Conferences, trade shows, festivals and sporting fixtures within a radius of each property, weighted by expected impact rather than counted equally.

Event dates, venue distance, expected attendance band, category

Calendar signals

Public holidays and regional school holiday calendars, including local schedules that move leisure demand differently across a country from week to week.

Public holidays, school break zones, bridge days, term dates

Market demand signals

Where a hotel has access to market pace or benchmark data, it becomes an additional input. RealM labels public availability as a compression signal rather than presenting it as market occupancy.

Market pace, occupancy benchmarks, segment mix where available