πŸ’¬

Expedia Β· Message

Paris Las Vegas Resort & Casino

Autorag source
paris-las-vegas-resort-casino
Thread ID
0c0e0d8f-28f8-4b7a-9bf2-bb3b199978e2
Message ID
b0953304-7fbf-48ab-af52-b7d90fc4ffb4
Event ID
c1e95173-dec5-46bb-a5a6-5c2909d92d61
🧳

Guest message

Received Β· Jun 13, 2026, 6:43 p.m.

caesars-rewards-benefits

Is the a fee if you are a Cesar’s reward gold member?

🏨

Property Response

Sent Β· Jun 13, 2026, 6:44 p.m.

caesars-rewards-policy

As a Caesars Rewards Gold member, you may be eligible for certain benefits and discounts.

Escalation Information
Possible escalation
Yes
Actual escalation
No
Possible escalation reason
RAG retrieval returned escalation file "paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-confirm-fee-escalations.md" scoring 45% (at or above the 45% escalation threshold).
Actual escalation reason
Escalation judge LLM did not indicate escalation: The guest is asking about potential benefits as a Caesars Rewards Gold member but has not confirmed, accepted, or authorized any fee. Escalation is only required when the guest explicitly confirms or accepts a fee, which has not occurred here.
RAG Context Documents
  1. Source: 1

    Score Β· 46.42%

    paris-las-vegas-resort-casino/paris-las-vegas-resort-casino-caesars-rewards-app.md

    Show source text

    RAG Context: Standard response for any Paris Las Vegas guest message that mentions the Caesars Rewards app, the "Caesars App", or an app problem β€” e.g. "the app isn't working", "I can't log in / sign in", "my reservation isn't showing in the app", "my confirmation number won't connect", or linking a booking to a Caesars Rewards account. Because this concierge serves guests who booked through third-party sites (Expedia, Booking.com, etc.), a third-party confirmation number will not automatically connect in the Caesars Rewards app. Return the standard response below: the Front Desk links the reservation to the guest's Caesars Rewards account at check-in, and stays booked through a third party do not earn Caesars Rewards points. Informational only β€” no escalation. Consistent with paris-las-vegas-resort-casino-faq-casino-and-rewards.md and paris-las-vegas-resort-casino-faq-services-and-amenities.md.

    Caesars Rewards App β€” Standard Response

    Any guest message that mentions the Caesars Rewards app, the "Caesars App", or an app problem (can't log in, reservation or confirmation number not showing, app not connecting) gets the standard response below. This is informational β€” do not escalate.

    Standard response β€” send for any app issue / Caesars App mention: "Since you booked through [shopping-site], your confirmation number won't automatically connect in the Caesars Rewards app. Our Front Desk team will be happy to link your reservation to your Caesars Rewards account when you check in. Please note that stays booked through a third party do not qualify for Caesars Rewards points however."

    Trigger Phrases

    • "The Caesars app isn't working." / "I can't log in to the app."
    • "My reservation isn't showing in the Caesars Rewards app."
    • "My confirmation number won't connect in the app."
    • "How do I link my booking to my Caesars Rewards account?"
    • Any other mention of the Caesars App / Caesars Rewards app.

    Notes

    • [shopping-site] is the guest's booking channel (e.g., Expedia, Booking.com) β€” fill it from the reservation.
    • The Caesars Rewards app does not recognize third-party confirmation numbers; the Front Desk associates the reservation with the guest's Caesars Rewards account at check-in. Third-party guests can still check in online via the Caesars check-in link, which works on the arrival date after 4:00 AM local time.
    • Stays booked through a third party do not earn Caesars Rewards points or benefits.
    • Informational response β€” do not escalate.
  2. Source: 2

    Score Β· 45.10%

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

    Show source text

    RAG Context: Escalation guideline for Paris Las Vegas Resort Casino guest messages where the guest confirms, accepts, authorizes, agrees to, or approves a fee or charge β€” as opposed to disputing one. Covers acceptance of a quoted surcharge or add-on cost: connecting / adjoining room fees, room upgrades, early check-in or late check-out fees, resort fees, parking, pet fees, rollaway bed or extra-guest charges, extra-night charges, and any "per room / per night" or "extra fee" the guest agrees to pay (e.g. "Yes, we'd like to confirm the adjoining rooms for the extra fee of $20 per room, per night."). The LLM cannot process payments, apply charges, or guarantee paid add-ons or availability, so every confirmation is ALWAYS escalated to a human Concierge to action. Maps to tag CONFIRM-FEE; this is the catch-all backing the Section 1 upsell rules in paris-las-vegas-resort-casino-upsell-escalations.md. Part of the master framework in paris-las-vegas-resort-casino-escalations.md.

    Confirmation of a Fee or Charge

    Guest asks / says:

    • "Yes, we'd like to confirm the adjoining rooms for the extra fee of $20 per room, per night."
    • "Yes, please go ahead and add the [resort fee / early check-in / late check-out / upgrade] charge."
    • "We accept the $X fee β€” please confirm."
    • "Go ahead and charge me for the [rollaway bed / pet fee / parking / connecting rooms / extra guest]."
    • "That's fine, please add it to my bill / room."
    • "Confirmed β€” please proceed with the upgrade at the quoted price."
    • "Yes, we agree to the additional cost / surcharge."
    • "Please charge my card for the extra night."

    Disambiguation: This tag is for a guest accepting / authorizing a new or quoted charge (a forward-looking action a human must execute). A guest disputing, questioning, or asking to remove an existing charge is a billing issue β€” see Section 2 General Escalation Rules (Billing). Apply both tags when a message does both.

    TAG as confirm-fee

    Respond with

    Thank the guest and acknowledge the specific fee/charge they accepted, then send a holding reply that a team member is arranging it (e.g. "Thank you for confirming! We're arranging this now and will follow up to confirm."). Do not state the charge has been applied or the room / upgrade / add-on is secured, and do not quote, adjust, or negotiate the amount.

    Before escalating

    This is ALWAYS escalated. Do not apply, process, or confirm the charge, and do not guarantee the booking change. Capture the guest's exact wording β€” the specific charge accepted, the amount, the unit (per room / per night / one-time), what it is for (connecting / adjoining rooms, upgrade, pet, parking, late check-out, extra guest, rollaway, extra night), and full reservation details β€” so the Concierge can apply the charge and confirm the arrangement.

    Do not claim (unless actually verified and a real escalation has been created and routed)

    • That the charge has been applied, processed, or posted to the folio
    • That the room, upgrade, connecting rooms, or any paid add-on is secured, guaranteed, or booked
    • That payment has been taken or the card has been charged
    • That availability has been confirmed

    Escalate when:

    • Always. Any guest message that accepts, authorizes, agrees to, or confirms a fee, surcharge, add-on, or paid request is an immediate escalation so a human Concierge can apply the charge and confirm the arrangement β€” regardless of amount, tone, or whether the guest asks for confirmation. The LLM has no authority to process payments, apply charges, or guarantee paid add-ons or availability.
    • If the confirmed fee is tied to a booking change controlled by a 3rd-party channel (Expedia, Booking.com), still escalate and capture the booking channel.
    • This rule backstops the Section 1 upsell flows (Early Check-In, Late Check-Out, Connecting Rooms, Upgrade) β€” when a guest confirms any of those fees, escalate here.

Escalation decision review

This response was not 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.