This worked case is part of the guide to procurement approvals and exception workflows, which sets out the three-part test for any exception record. Here the job is narrower: one hard hospitality case, walked through decision by decision, ending with how a CX consultant can spot similar cases at a client.
The setup: a noise complaint on night one
Illustrative and invented for this page. A 600-person hotel management company runs eleven full-service properties. A guest on a four-night stay calls the front desk at 23:40 on the first night: the room sits above a ballroom where a wedding reception is running late.
| Time | What happened | Who | Record it left |
|---|---|---|---|
| Night 1, 23:40 | Guest calls about noise | Night auditor | Issue log entry in the property management system, category "noise", linked to the reservation |
| Night 1, 23:55 | No quieter room of the same type is free | Night auditor | Room availability note on the same log entry |
| Day 2, 07:10 | Guest emails the hotel's general inbox asking for compensation | Guest | Inbound message in the guest messaging tool |
At this point the case is routine. It becomes an exception the moment two people answer it separately.
Where it went wrong: two offers to the same guest
On day 2 the front desk manager replies through the messaging tool and offers a credit of one night's room rate against the folio. Forty minutes later, the group sales manager, who booked the guest as part of a corporate block, phones the guest and promises a free additional night on a future stay. Neither knows about the other's offer.
| Time | Offer | Made by | Record it left |
|---|---|---|---|
| Day 2, 09:20 | One night's rate credited to this stay | Front desk manager | Outbound message in the messaging tool |
| Day 2, 10:00 | Free night on a future stay | Group sales manager | Call note in the sales system; follow-up email to the guest |
| Day 2, 11:30 | Guest replies accepting both | Guest | Reply in the messaging tool |
This is the record pattern that matters. The two promises sit in two systems, owned by two departments, and only the reservation number connects them. A company that kept the sales call note but purged old messages would hold half the story.
The decision: one remedy approved, one voided
The guest's reply reaches the guest operations director, who reviews both offers against the company's service recovery policy. Policy allows either remedy for a disturbance the hotel caused, but not both. The director approves the folio credit, because it settles the complaint during the stay, and voids the future free night. The group sales manager is asked to tell the guest, with an apology for the mixed message, and adds a late checkout instead.
| Time | Decision | Decided by | Record it left |
|---|---|---|---|
| Day 2, 14:00 | Approve the folio credit | Guest operations director | Approval note in the manager log, citing the policy clause |
| Day 2, 14:00 | Void the future free night | Guest operations director | Same note; voided voucher in the sales system |
| Day 2, 15:15 | Explain to guest, offer late checkout | Group sales manager | Email to guest; late checkout flag on the reservation |
The approval note is the most valuable record in the case, because it holds the reason. If the director had decided by phone and written nothing, the chain would show two offers and one outcome with no explanation in between.
The outcome check: the folio and the follow-up
| When | Check | Record | What it proves |
|---|---|---|---|
| Day 4, checkout | One night's rate appears as a single adjustment | Folio adjustment with reason code and approver | Only the approved remedy was applied |
| Day 4 | No free-night voucher is active on the guest profile | Voucher status in the sales system | The voided promise did not leak through |
| Day 9 | Guest answers the post-stay survey: satisfied with the resolution | Survey response linked to the stay | The remedy was accepted |
Lined up, the four tables give a complete worked problem: a policy, a conflict, a decision with its reason, and two independent checks that the decision held.
Why the sequence teaches more than the policy
A service recovery policy says what staff may offer. It cannot show what happens when two staff members apply it at once, or how a director weighs a credit now against a voucher later. The sequence above can, because every step is dated, attributed and tied to one reservation. That is the kind of material discussed in AI agents need work data: records of real decisions and the checks that followed.
The case also carries the usual privacy weight. Names, phone numbers, email addresses and loyalty numbers in these records are personal data under the GDPR, which defines it as any information relating to an identified or identifiable person, and the EDPB lists purpose limitation, data minimization and storage limitation among the principles a controller must be able to show it follows. For a partner that means one thing: the guest details are for the company and SourceX to handle under agreed redaction rules, never for the partner to collect or see.
Spotting the same pattern at a hotel client
CX consultants, revenue managers and hospitality advisors can recognize companies with cases like this without seeing a record. Ask the guest operations director:
- Do sales, front desk and guest relations ever answer the same complaint separately? Group blocks and loyalty members make it common.
- Where are remedies approved? A manager log, an email thread or a field in the property management system each leave a different trail.
- Do the issue log, messages, sales notes and folio adjustments share a reservation number? Without one, the case cannot be rebuilt.
- How many properties and years of these records exist, and is any system being replaced?
Then introduce the person who can authorize a licensing discussion, the CEO, with the guest operations director as working contact. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Who qualifies has the full list. Management companies should also check whether their contracts with hotel owners say who controls guest records, which is a question for counsel. What stays unknown until SourceX reviews it: export options for each system, how much redaction applies, and whether buyers want these records. The hospitality operating procedures guide and the hospitality industry page cover the surrounding records, and the questions to ask a business owner work for the first conversation. Related hard cases: a timesheet correction that crosses two cutoffs and a franchise brand standard variation.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a hotel company you advise can rebuild conflicting-remedy cases like this one from its own systems, register as a partner, confirm who qualifies and read the program terms before introducing its decision-maker.