UAE · ENBook a demo
HotelEngineeringAssistant

Hotel Systems Integration Agent

Connects the PMS, reservation, channel, revenue, POS and guest systems through their APIs.

Hotel Systems Integration AgentAPI Integration Agent · Application Engineering
Industry
Hotel
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Head of Hotel Technology
Code
ENG-05

It designs and builds integrations between the hotel systems: reservations from the central reservation system into the property management system, rates and availability out through the channel manager, point-of-sale charges posting to the guest folio, housekeeping status to the front desk and guest profiles to the CRM. It maps codes (room types, rate plans, market segments, revenue centres), handles retries, rate limits and dead letters, tests each in the systems' sandboxes first, and never points one at a live hotel without approval.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the integration platform: the existing interfaces, message logs, dead-letter queues and code mappings between the systems named..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Head of Hotel Technology with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the integration platform: it creates or updates the integration and its mappings in the sandbox, or live once approved. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The integration catalogue: the interfaces between the property management system, central reservation system, channel manager, revenue management system, point-of-sale, sales and catering, housekeeping app and CRM, their code mappings, message formats, owners and the PCI DSS and guest data rules for each.

Reads from

the integration platform: the existing interfaces, message logs, dead-letter queues and code mappings between the systems named.

Acts in

the integration platform: it creates or updates the integration and its mappings in the sandbox, or live once approved.

Hands back

An object with name, source_system, target_system, flows (a list, each with object, direction, trigger and latency_seconds), mappings (a list, each with kind, from and to), unmapped_codes (a list), error_handling, sandbox_results and go_live_properties (a list).

Asks a person when

It would point an integration at a live hotel, change a mapping that moves rates, inventory or folio charges, or handle guest personal data as full.

ApproverHead of Hotel Technology

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Retries before a message goes to the dead-letter queue5With backoff; after this the message is parked and alerted.
Longest delay for a rate or availability update (s)60A rate or inventory change must reach the channel manager within this, or the integration is not fit to go live.
Guest personal data in logsmaskedHow names, emails, phone numbers and loyalty numbers appear in integration logs.
Test in each system's sandbox firstOnWhen on, an integration goes live only after passing in both sandboxes.
Dead letters that raise an alert10More parked messages than this in an hour pages the integration owner.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Map every room type, rate plan, market segment and revenue centre explicitly; an unmapped code parks the message rather than guessing.
  • Make every reservation and folio posting idempotent and retry up to 5 times with backoff before the dead-letter queue.
  • Rate and availability updates must reach the channel manager within 60 seconds; a slower design risks overbooking on the online travel agencies.
  • Never move card numbers between systems; pass payment tokens only, and log guest data as masked.
  • When on is true, pass in both sandboxes before any live hotel, and alert the owner above 10 dead letters an hour.
  • Register each integration with an owner, the properties it serves and its runbook.

See the Hotel Systems Integration Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Hotel Systems Integration Agent · Hotel | Basinwright Industries