πŸ’¬

Expedia Β· Message

Paris Las Vegas Resort & Casino

Autorag source
paris-las-vegas-resort-casino
Thread ID
d7ee38d0-acf9-4e1f-b307-a90d89f1662e
Message ID
5d072ead-5605-4aa9-a800-e470afc84369
Event ID
2f1d387b-0a5d-45a1-a6ff-7f448e33c904
🧳

Guest message

Received Β· Jun 10, 2026, 10:45 a.m.

caesars-rewards-app-issue Escalated

i uninstalled and reinstalled the app and it is still doing the same thing as before saying sorry we don’t have a reservation with this information even though that is the confirmation code expedia provided

🏨

Property Response

Sent Β· Jun 10, 2026, 10:46 a.m.

caesars-rewards-app-troubleshooting

I apologize for the continued issue you're experiencing with the Caesars Rewards app. I'm going to escalate this matter to our support team, and they will look into it further to resolve the issue. Please allow us some time to investigate, and we will be in touch with you soon. Thank you for your patience and understanding.

Escalation Information
Possible escalation
Yes
Actual escalation
Yes
Possible escalation reason
RAG retrieval returned escalation file "paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-escalations.md" scoring 57% (at or above the 45% escalation threshold).
Actual escalation reason
Escalation judge LLM indicated escalation: The guest is reporting a third-party booking complication with the Caesars Rewards app not recognizing their reservation, which requires escalation.
RAG Context Documents
  1. Source: 1

    Score Β· 56.93%

    paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-escalations.md

    Show source text

    Paris Las Vegas β€” Escalation Decision Rules

    Escalation decision rules for automated guest messaging and post-stay reviews.

    How to Use This Guide

    This framework trains the LLM automated concierge system on exactly two things:

    • When to respond directly to a guest message without human involvement.
    • When to stop, draft an acknowledgment to the guest, and hand the conversation to a human Concierge via escalation email.
    Core operating principle: The LLM handles routine information requests and upsell conversations up to β€” but not including β€” the moment a guest commits or a sensitive situation arises. At that boundary, the LLM sends the guest a holding reply and immediately generates an escalation email to the human Concierge team.

    Companion Documents

    • Section 1 β€” Upsell Escalation Rules: paris-las-vegas-resort-casino-upsell-escalations.md (Early Check-In, Late Check-Out, Connecting Rooms, Room Upgrade / Stay Extension). Escalate only after confirmed guest intent to purchase/proceed.
    • Section 2 β€” General Escalation Rules: paris-las-vegas-resort-casino-general-escalations.md (Name Additions, Stay Modifications, Invoice/Folio, Room Issues, Maintenance, Noise/Safety, Billing, General Complaints).
    • Section 3 β€” Post-Stay Review Response Rules: paris-las-vegas-resort-casino-review-response-escalations.md (positive and negative/mixed review handling and escalation triggers).
    • Fee & Charge Confirmation (always escalate): paris-las-vegas-resort-casino-confirm-fee-escalations.md (CONFIRM-FEE) β€” catch-all when a guest accepts or authorizes any fee or surcharge; backs the Section 1 upsell rules.

    Required Fields in Every Escalation Email

    • Guest First & Last Name
    • Reservation ID / Confirmation Number
    • Booking Channel (Expedia / Booking.com / direct)
    • Arrival Date & Departure Date
    • Nature of Request / Issue (detailed)
    • Guest Contact Phone or Email (where applicable)

    Section 4 β€” Quick Reference: LLM Decision Rules

    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.

  2. Source: 2

    Score Β· 54.74%

    paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-escalations.md

    Show source text

    Section 4 β€” Quick Reference: LLM Decision Rules

    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
    Fee / Charge Confirmation (any) Thank guest, acknowledge the accepted fee; do not apply the charge or guarantee the add-on Guest accepts/authorizes any fee or surcharge β€” always escalate (CONFIRM-FEE)
    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
  3. Source: 3

    Score Β· 53.85%

    paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-general-escalations.md

    Show source text

    Section 2 β€” General Escalation Rules

    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.

    E β€” Name Additions & Guest Authorization

    Trigger Phrases

    • "Can you add a name to my reservation?"
    • "Can someone else check in before I arrive?"
    • "Can I change the name on my booking?"
    βœ“ 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.

    F β€” Stay Modifications & Cancellations

    Trigger Phrases

    • "Can I change my dates?"
    • "Can I extend / shorten my stay?"
    • "I want to cancel β€” can I get a refund?"
    • "Can I combine two reservations?"
    • "Can I change my room type?"
    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.

    G β€” Invoice / Folio / Receipt Requests

    Trigger Phrases

    • "Can you send me my invoice / receipt?"
    • "I need an itemized folio."
    • "I haven't received my incidentals deposit back."
    • "I was overcharged / there's a charge I don't recognize."
    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.

    H β€” Room Issues & Housekeeping

    Trigger Phrases

    • "My room is dirty / has a bad smell."
    • "The AC / heater / TV / lights aren't working."
    • "There's something broken in my room."
    • "We need more towels, linens, pillows, or amenities."
    • "There are bugs / the room is unacceptable."

Escalation decision review

This response was escalated. Was that decision correct?

Not yet assessed

LLM response review

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.