Guest message
Received · Jun 15, 2026, 7:37 p.m.
Olá, a cobrança reserva que fizeram no meu cartão no dia do checkin não foi estornada, podem verificar por favor!
Expedia · Message
Received · Jun 15, 2026, 7:37 p.m.
Olá, a cobrança reserva que fizeram no meu cartão no dia do checkin não foi estornada, podem verificar por favor!
Sent · Jun 15, 2026, 7:38 p.m.
Thank you for reaching out to us about the issue with the charge on your card. We apologize for the inconvenience and will review the matter. We will assist in resolving the issue.
Source: 1
Score · 55.34%RAG Context: Escalation guideline for Flamingo Las Vegas 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: adjoining / connecting room fees, room upgrades, early check-in or late checkout 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 $25 per room, per night."). The LLM cannot process payments, apply charges, or guarantee paid add-ons or availability, so every confirmation must be handed to a human to action. Maps to risk category FEE & CHARGE CONFIRMATION (tag CONFIRM-FEE) in the master Flamingo Risk Management Framework (
flamingo-las-vegas-hotel-casino-escalations.md). All matches require immediate escalation. Do not confirm the charge is applied or the add-on secured — acknowledge and route to a human.
Trigger keywords (non-exhaustive): yes please confirm, we'd like to confirm, go ahead and charge, charge me, charge my card, add it to my bill, add it to my room, accept the fee, agree to the charge, agree to the fee, approve the fee, okay to charge, that's fine charge, proceed with the upgrade, confirm the extra fee, extra fee, additional charge, additional cost, surcharge, add-on, per night, per room, willing to pay, sounds good charge me, confirm the [adjoining / connecting] rooms.
Disambiguation: This category is for a guest accepting / authorizing a new or quoted charge (a forward-looking action that must be executed by a human). If the guest is disputing, questioning, or asking to remove an existing charge, that is a billing dispute — see General Escalation Rules §K (Billing Issues & Charge Disputes). When a message both accepts a fee and disputes another, apply both tags.
Thank the guest for confirming and acknowledge the specific fee/charge they accepted. Never state that the charge has been applied, the payment processed, or the room / upgrade / add-on secured; do not quote, adjust, or negotiate the amount, or guarantee availability. Make clear that a team member will finalize the arrangement and apply the charge. The LLM is not authorized to process payments or confirm paid add-ons.
Do not apply, process, or confirm the charge, and do not guarantee the booking change. The LLM is authorized to acknowledge and thank only. Capture the guest's exact wording in the escalation record — the specific charge accepted, the amount, the unit (per room / per night / one-time), what it is for (adjoining / connecting rooms, upgrade, pet, parking, late checkout, extra guest, rollaway, extra night), and full reservation details — so the concierge can apply the charge and confirm the arrangement.
[CONFIRM-FEE] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.Source: 2
Score · 50.57%RAG Context: Pre-stay standardized response templates for Flamingo Las Vegas guest communications — booking confirmation, check-in instructions, early check-in (guaranteed in advance for $60+tax at 11:00 AM, otherwise availability-based), express/online check-in with kiosk QR link, pre-arrival letters (standard and day-of arrival), rack/room-upgrade upsell, back-to-back stays, late arrival, stay modification/cancellation, third-party payment questions, adding guest names to a reservation, deposit explanation, Caesars Rewards third-party booking guidance, connecting-room requests (confirm names and confirmation numbers), PetStay requests, parking overview, and a phishing/suspicious-message advisory. Per merge guidance, this file does not embed the late-checkout fee tier table — that lives in the FAQ and the in-house template.
Dear [guest-name],
Thank you again for booking with us! We can't wait to welcome you to Flamingo Las Vegas in a few short days. Here's a quick reminder of what to expect during your stay:
Source: 3
Score · 49.51%RAG Context: Standard response for any Flamingo Las Vegas guest message about late check-IN or a late arrival — "can I check in late?", "we're arriving late / after midnight", "what if we get there at 2am?", "is there late check-in?", "do you have 24-hour check-in?". The front desk is open 24 hours and guests may check in at any time; guests arriving past 1:00 AM should call the front desk (702-733-3111). Informational only — no escalation. This is late ARRIVAL, NOT late check-OUT — late check-out is a separate, fee-based topic in
flamingo-las-vegas-hotel-casino-faq-hotel-policies.md. Consistent with the LATE ARRIVAL template inflamingo-las-vegas-hotel-casino-standardized-responses-pre-stay.mdand the 24-hour front desk note inflamingo-las-vegas-hotel-casino-faq-hotel-policies.md.
Any guest message asking about checking in late, arriving late, or whether there is late / 24-hour check-in gets the standard response below. This is informational — do not escalate. (Late check-out is a separate, fee-based topic — do not confuse the two.)
| Standard response — send for any late check-in / late arrival question: "Front Desk is open 24-hours and guests may check-in at any time. Please call the front desk if arriving past 1:00am." |
|---|
flamingo-las-vegas-hotel-casino-faq-hotel-policies.md.This response was not escalated. Was that decision correct?
Marked incorrect
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.