πŸ’¬

Expedia Β· Message

Flamingo Las Vegas Hotel & Casino

Autorag source
flamingo-las-vegas-hotel-casino
Thread ID
77ecf40b-8874-47d0-a488-3c5a017f2bf5
Message ID
6dcc6dc4-5494-4f5e-bddc-830df2d0abcf
Event ID
1e0c9f3a-3905-4604-82b1-baeb1ab4f2a8
🧳

Guest message

Received Β· Jun 13, 2026, 8:56 p.m.

check-in-issue

I’m trying to check in with the app but is not finding my reservation with the number provided

🏨

Property Response

Sent Β· Jun 13, 2026, 8:57 p.m.

check-in-assistance

I apologize for the difficulty you're experiencing with checking in through the app.

Escalation Information
Possible escalation
Yes
Actual escalation
No
Possible escalation reason
RAG retrieval returned escalation file "flamingo-las-vegas-hotel-casino/flamingo-las-vegas-hotel-casino-customer-phone-number-escalations.md" scoring 61% (at or above the 45% escalation threshold).
Actual escalation reason
Escalation judge LLM did not indicate escalation: The guest's message does not contain a phone number or request to be called or texted, so the customer-phone-number escalation rule does not apply.
RAG Context Documents
  1. Source: 1

    Score Β· 69.91%

    flamingo-las-vegas-hotel-casino/flamingo-las-vegas-hotel-casino-caesars-rewards-app.md

    Show source text

    RAG Context: Standard response for any Flamingo 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 flamingo-las-vegas-hotel-casino-faq-casino-and-rewards.md, flamingo-las-vegas-hotel-casino-faq-services-and-amenities.md, and flamingo-las-vegas-hotel-casino-faq-hotel-policies.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 links the reservation to the guest's Caesars Rewards account at check-in. Third-party guests can still check in online via the web link emailed on arrival day.
    • Stays booked through a third party do not earn Caesars Rewards points or benefits.
    • Informational response β€” do not escalate.
  2. Source: 2

    Score Β· 60.88%

    flamingo-las-vegas-hotel-casino/flamingo-las-vegas-hotel-casino-customer-phone-number-escalations.md

    Show source text

    flamingo customer-phone-number

    RAG Context: Escalation guideline for Flamingo Las Vegas guest messages where the guest's message contains a phone number β€” i.e. the guest supplies a phone number (their own cell / mobile, a callback number, an alternate contact, or someone else's) or asks to be called or texted at a number (e.g. "Please call me at (702) 555-0199."). The Flamingo automated assistant operates on text-messaging and post-stay review channels and cannot place or receive phone calls or SMS; a guest sharing a personal phone number is requesting β€” explicitly or implicitly β€” direct human or voice contact, and is supplying personal contact information (PII) that a person must handle. Every guest message that contains a phone number is therefore an immediate, always-on escalation to a human Concierge. Maps to risk category CUSTOMER PHONE NUMBER (tag CUSTOMER-PHONE-NUMBER) in the master Flamingo Risk Management Framework (flamingo-las-vegas-hotel-casino-escalations.md). All matches require immediate escalation. Do not call or text the number, and do not repeat the full number back in a public reply β€” acknowledge and route to a human.

    Customer-Supplied Phone Number

    Guest asks / says:

    • "Please call me at (702) 555-0199."
    • "My cell is 702-555-0142 β€” call anytime."
    • "Can someone reach me at +1 555 867 5309?"
    • "Text me at 5550100123."
    • "Here's my number: 555-0188, please follow up by phone."
    • "Call my husband at 702.555.0177 to sort this out."
    • "I'd rather talk β€” my number's 555 0150."

    Trigger keywords (non-exhaustive): call me at, reach me at, text me at, my number is, my cell is, my mobile is, here's my number, you can reach me on, call my [husband / wife / assistant] at, call me back, give me a call β€” plus any digit sequence formatted as a phone number in the guest's message: (NPA) NXX-XXXX, NPA-NXX-XXXX, NPA.NXX.XXXX, 7-digit NXX-XXXX, international +CC … / +1 NPA NXX XXXX, or a bare 10-/11-digit run.

    Disambiguation: This category fires when the guest supplies or shares a phone number (or asks to be contacted at one). A guest asking for the property's phone number ("what's the front-desk / pool / spa number?") is a routine information request β€” answer from flamingo-las-vegas-hotel-casino-property-details.md, do not tag here. Do not over-trigger on non-phone digit strings: reservation / confirmation numbers, Caesars Rewards numbers, room numbers, dates, and dollar amounts are not phone numbers. Tag only when the digits are presented as a phone / contact number or paired with a call/text request. When a message both shares a number and raises another issue (billing, safety, complaint), apply both tags.

    TAG as customer-phone-number

    Respond with

    Thank the guest and let them know a team member will follow up. Send a holding reply only (e.g. "Thank you β€” I've passed your details to our team and someone will be in touch."). Never state that a call or text has been placed, returned, or scheduled for a specific time; do not call or text the number yourself; and do not echo or repeat the full phone number back in the reply β€” especially on a public review channel β€” treat it as private contact information.

    Before escalating

    Do not call or text the guest and do not promise a specific callback time. The LLM is authorized to acknowledge only. Capture in the escalation record: the guest's exact wording, the phone number provided and whose number it is (guest / spouse / assistant), any preferred call or text window, the reason they want to be contacted, the inbound channel, and full reservation details β€” so the Concierge can make voice/SMS contact.

    Escalate when:

    • Always. Any guest message that contains a phone number, or any request to be called or texted, is an immediate escalation so a human can make voice/SMS contact and handle the personal contact details β€” regardless of the reason, tone, or topic. The LLM has no ability to place or receive calls or texts.
    • If the phone number accompanies a sensitive issue (safety, injury, theft, health, harassment, legal, billing dispute), escalate under both this tag and the relevant risk-category guide, and flag the higher-severity tier.
    • Tag the conversation: [CUSTOMER-PHONE-NUMBER] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.
  3. Source: 3

    Score Β· 55.46%

    flamingo-las-vegas-hotel-casino/flamingo-las-vegas-hotel-casino-general-escalations.md

    Show source text

    RAG Context: Section 2 general escalation rules for Flamingo Las Vegas routine guest-service requests β€” Name Additions & Guest Authorization, Stay Modifications & Cancellations, Invoice/Folio/Receipt Requests, Room Issues & Housekeeping, Maintenance Requests, Noise/Neighbor/Safety Complaints, Billing Issues & Charge Disputes, and General Complaints & Compensation Requests. For each: trigger phrases and a clear split between what the LLM responds to directly versus what it escalates to a human Concierge. Safety, medical, injury, theft, and billing-dispute messages always escalate. The on-site Security Team is available 24/7 at 702-733-3523. Part of the master framework in flamingo-las-vegas-hotel-casino-escalations.md.

    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?"

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.