Guest message
Received Β· Jun 9, 2026, 2:10 p.m.
Hi Paris hotel, Please confirm - I had modified my reservation (adding 1 night): Checking in Friday June 12 and checking out Monday June 15th.
Expedia Β· Message
Received Β· Jun 9, 2026, 2:10 p.m.
Hi Paris hotel, Please confirm - I had modified my reservation (adding 1 night): Checking in Friday June 12 and checking out Monday June 15th.
Sent Β· Jun 9, 2026, 2:10 p.m.
Thank you for reaching out to us about your reservation modification. Since you booked through Expedia, please contact Expedia's customer service directly to confirm any changes to your stay, including the additional night. They will be able to assist you with modifying your reservation. We look forward to welcoming you to Paris Las Vegas.
Source: 1
Score Β· 64.12%Use this table as a fast lookup for any incoming guest message. Find the request type, confirm whether the LLM handles it or escalates, and identify the specific trigger that activates the escalation.
| Request / Scenario | LLM Response | Escalation Trigger |
|---|---|---|
| Early Check-In | Share $60 + tax fee, explain availability | Guest confirms they want to pay β then escalate |
| Late Check-Out | Share fee schedule, explain availability option | Guest confirms fee + desired time β then escalate |
| Connecting Rooms | Explain $20/room/night fee, request names & conf #s | Guest confirms fee + provides all names & conf #s β then escalate |
| Upgrade / Extend Stay | Ask for best contact phone number | Guest provides phone number β then escalate |
| Name Addition / Alt Check-In | Collect name, explain ID/card requirements | Primary name change, billing auth, identity mismatch |
| Stay Modification / Cancel | Explain 3rd-party policy, direct to booking channel | 3rd party cannot process; complex booking changes |
| Invoice / Folio / Receipt | Explain who issues folio, set timeline expectations | Itemization, billing correction, refund request |
| Room Issue / Housekeeping | Apologize, gather details, direct to front desk first | Front desk unresponsive; safety impact; comp requested |
| Maintenance Request | Acknowledge, direct to front desk / Laurel text | Front desk unresponsive; repair still needed |
| Noise / Safety Complaint | Acknowledge, direct to Security / front desk | Security/front desk intervention needed; unresolved |
| Billing Dispute / Refund | Acknowledge, collect details | Any correction, dispute, or refund β always escalate |
| General Complaint / Comp | Empathize, document thoroughly | Compensation requested; multiple failures; emotional guest |
| Post-Stay Review β Negative | Acknowledge publicly with empathy template | Safety, discrimination, viral-risk β escalate within 12h |
| Post-Stay Review β Positive | Respond with standard thank-you template | No escalation required |
Source: 2
Score Β· 61.98%RAG Context: Pre-stay standardized response templates for Paris Las Vegas guest communications β booking confirmation, check-in instructions, early check-in (guaranteed at 11:00 AM for $60 + tax, otherwise availability-based), online/contactless check-in, pre-arrival letter, room upgrade/extension upsell (collect best phone number), late arrival, stay modification/cancellation, adding guest names to a reservation, deposit explanation, connecting-room requests ($20/room/night; confirm names and confirmation numbers), Pet Room requests ($75/night, dogs only), parking overview, third-party payment questions, and a phishing/suspicious-message advisory.
Dear [guest-name],
Thank you for booking with us! We can't wait to welcome you to Paris Las Vegas. Here's a quick reminder of what to expect during your stay:
Source: 3
Score Β· 61.03%These rules apply to routine guest-service requests that arrive via message. The LLM should acknowledge professionally, provide any information it can, and escalate when the situation requires human action or decision-making.
Trigger Phrases
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Collect the additional guest's name. Explain that a valid government-issued photo ID and the card used to book are required at check-in. Note the request with full reservation details. | Guest wants to change the PRIMARY guest name. Guest wants a guarantee that another person can check in without the booker present. Any billing authorization, third-party payment, or identity mismatch. |
Trigger Phrases
| Before escalating β always tell the guest: If the reservation was made through a 3rd-party booking channel (Expedia, Booking.com), the guest must contact that platform's customer service directly to modify or cancel. The LLM cannot make these changes. |
|---|
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Explain the modification policy based on booking channel (the guest must contact the third party to modify). Direct guest to the appropriate channel (Expedia, Booking.com, or Caesars direct). | 3rd-party booking cannot process the modification. Dates, room type, occupancy, or confirmation structure must change and the channel cannot assist. Complex booking complications requiring hotel intervention. |
Trigger Phrases
| Useful information to provide before escalating: Folios are emailed automatically after checkout. Debit card holds may take several business days to release. For any billing changes or disputes, the front office team must be involved. |
|---|
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Explain that folios are emailed after checkout. Note that debit card holds take several business days to release. Route guest to the appropriate team and set timeline expectations. | Guest needs an itemized folio delivered. Guest disputes a charge or requests a correction. Guest requests a refund. Business invoice format required. Incidentals hold not released after the expected timeframe. |
Trigger Phrases
This response was not escalated. Was that decision correct?
Not yet assessed
Set by the preferred response below β saving a correction marks it incorrect, clearing the correction marks it correct.
Not yet assessed
Optionally provide a better response. Saving non-empty text marks the LLM response incorrect; clearing it marks the LLM response correct.