Connect HotSOS to Claude

This is the workhorse. According to the Amadeus Service Optimization help documentation, the service orders list supports a Filter Builder panel for narrowing to specific data and a Download As Excel action that saves the filtered list as a spreadsheet.

1. In HotSOS, open the service orders list.
2. Use the Filter Builder to scope what you want to analyze: a date range, a trade, a status, a floor. Each list view keeps its own filters.
3. Click Download As Excel.
4. Start a chat with Claude, attach the file, and ask your question. For recurring analysis, create a Claude Project called something like "HotSOS weekly" and keep a standing instruction such as: Every file I upload is a HotSOS service order export. Always report completion time by trade and flag repeat locations.

The whole loop takes two or three minutes and needs no approvals. It is also the safest possible integration: read-only by construction, because Claude only ever sees a file you chose to export.

HotSOS ships a set of operational reports. The Amadeus help documentation lists them: Executive Summary, Frequency, Inspection Frequency, Inspection Log, Inspection Order Form Details, Meter Reading with Graphs, Productivity, Property PM Progress, Service Order Detail, and Work Order Form. Each report takes standard parameters; per the documentation, the date range defaults to yesterday and the time range defaults to 12:00 AM to 11:59 PM, both adjustable.

1. Tap the reports icon in the left sidebar, then Operational.
2. Pick the report. For response time and defect analysis, Service Order Detail is the dense one. For a leadership recap, Executive Summary.
3. Set the parameters and tap the Run Report icon. A notification lands in your Messages List when the report is ready.
4. Save the report output and hand it to Claude the same way as the Excel export, with a prompt about what you want pulled out of it.

Reports and exports complement each other: the export gives Claude row-level data to compute on, while a report like the Executive Summary gives it the framing your GM already recognizes. Uploading both and asking Claude to reconcile them is a genuinely useful sanity check.

The HotSOS API is real, and a live integration ecosystem runs on it. But access is gated. Pandium's connector documentation states that the connector authenticates with basic auth using an API base URL, username, and password, and says plainly: for more information on how to utilize the HotSOS API, reach out to your Amadeus Implementation Project Manager. PolyAI's integration documentation similarly lists a REST or SOAP endpoint (its example is https://ifc.emea.hot-sos.net/api/service.svc/rest) with credentials provided by Amadeus.

So the honest version of this path is:

1. Ask Amadeus first. Your Implementation Project Manager or account team is the only route to API documentation and credentials. If you are a brand or management company, this usually rides on your existing enterprise relationship.
2. Once you hold credentials, the technical lift is small: an MCP server is a lightweight program that exposes API calls to Claude as tools. Anthropic's Model Context Protocol SDKs (TypeScript and Python) make a read-only wrapper, with tools like list-service-orders and get-service-order, an afternoon of work for whoever owns your integrations.
3. Keep it read-only. HotSOS dispatches real people to real rooms. Claude should analyze the queue, not write to it, at least until your team has lived with the read-only version for a while.

We are deliberately not publishing endpoint-by-endpoint sample code here, because the HotSOS API surface is not publicly documented and pretending otherwise is how vague guides get written. If you have the credentials and the Amadeus docs in hand, our Guesty and Breezeway guides show the exact MCP server pattern to copy, tool definitions, config file and all.