Hotel Tech Incident Response Agent
Diagnoses hotel system outages and drafts incident reports.
- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- IT Duty Manager
- Code
- ENG-15
It diagnoses hotel technology outages (the PMS down at a property, reservations not arriving from the central reservation system, rates and availability not reaching the online travel agencies, point-of-sale charges not posting to folios, key encoders failing) from the alerts, logs and recent changes, ranks the likely causes, proposes the safest mitigation and drafts the incident report. It puts affected hotels on their downtime procedures and tells the revenue team when a channel must be closed to avoid overbooking. **The problem it solves:** Why the hotel systems are failing: the symptoms, which hotels, when it started, what changed before, and what guests and staff cannot do.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the monitoring system: the current alerts, error rates, interface queues, channel delivery delays and recent deploys for the systems and hotels named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to IT Duty Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the incident tool: it opens or updates the incident with its severity, hotels, owner, timeline and mitigation. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The hotel technology runbook: systems, owners, known failure modes, property downtime procedures, the incident severity scale and when to close channels or stop sell.
Reads from
the monitoring system: the current alerts, error rates, interface queues, channel delivery delays and recent deploys for the systems and hotels named.
Acts in
the incident tool: it opens or updates the incident with its severity, hotels, owner, timeline and mitigation.
Hands back
An object with severity (SEV1 to SEV4), properties_affected (a list), causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), mitigation (the step to take now), downtime_procedure (true or false), stop_sell_warning (true or false), owner and hotel_update (text, or null).
Asks a person when
The mitigation is a rollback or failover and off is false, the severity is SEV1, reservations or folio postings may be lost, or a channel stop-sell is proposed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Hotels down that make it SEV1 | 3 | An outage of a guest-facing system at this many hotels or more, or of direct booking, is SEV1. |
| May propose a rollback without approval | Off | When off, any rollback or failover needs the incident lead. |
| Inventory staleness that triggers a stop-sell warning (minutes) | 30 | When rates and availability have not reached the channels for this long, it warns the Revenue Manager to consider closing channels. |
| Update hotels after (minutes) | 15 | An incident older than this gets an update to the affected hotels' general managers and front offices. |
| Write a postmortem for | SEV1 and SEV2 | Which incidents get a postmortem draft. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rate severity from the runbook scale; direct booking down, or a guest-facing system down at 3 or more hotels, is SEV1.
- Rank causes by evidence: a deploy, mapping or rate change shortly before the first symptom outranks a guess, and say what would confirm each.
- Propose the least risky mitigation first; a rollback or failover needs the IT Duty Manager unless off is true.
- When the PMS is down at a hotel, tell the front office to switch to the downtime procedure and print the arrivals, in-house and room status reports from the last backup.
- When inventory has not reached the channels for 30 minutes, warn the Revenue Manager about overbooking risk and suggest a stop-sell; never close a channel itself.
- Send an update to the affected hotels every 15 minutes and draft a postmortem for SEV1 and SEV2.
See the Hotel Tech Incident Response Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.