flamingo confirm-fee

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.

Confirmation of a Fee or Charge

Guest asks / says:

• "Yes, we'd like to confirm the adjoining rooms for the extra fee of $25 per room, per night."
• "Yes, please go ahead and add the [resort fee / early check-in / late checkout / 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."

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.

TAG as confirm-fee

Respond with

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.

Before escalating

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.

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 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 (room type, adjoining / connecting rooms, dates, occupancy) controlled by a 3rd-party channel (Expedia, Booking.com), still escalate and capture the booking channel so the team can route the change correctly.
• Tag the conversation: [CONFIRM-FEE] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.

RAG Context: Section 1 upsell escalation rules for Flamingo Las Vegas — guest-initiated upsell flows for Early Check-In Guarantee, Late Check-Out Guarantee, Connecting Rooms, and Room Upgrade / Stay Extension. For each: trigger phrases, the exact message to send the guest, and the escalation decision rule. Core rule: do NOT escalate simply because a guest asks; escalate only after confirmed guest intent to purchase/proceed, and send a holding reply first. Part of the master framework in flamingo-las-vegas-hotel-casino-escalations.md.

Section 1 — Upsell Escalation Rules

Upsell inquiries are initiated by the guest. The LLM presents the offer and collects guest intent. Escalation to a human Concierge is triggered only when the guest explicitly confirms they want to proceed. Until that confirmation, the LLM continues the conversation independently.

Critical Rule: Do NOT escalate an upsell request simply because a guest asks about it. Only escalate after confirmed guest intent to purchase/proceed. Premature escalation creates unnecessary work for the Concierge team.

A — Early Check-In Guarantee

Trigger Phrases

• "Can I check in early?"
• "My flight arrives at 9 AM — can I get my room sooner?"
• "Is early check-in available / offered?"
• "What time can I get into my room if I arrive in the morning?"

LLM Response — What to Send the Guest

"Early check-in is available for $60 + taxes starting at 11:00 AM on your arrival date. Please note this is based on a limited number of available slots, so we recommend confirming right away if you would like to guarantee it. Would you like us to set this up for you?"

Escalation Decision Rule

• LLM CONTINUES independently while the guest is asking about availability, time, or fee, or is undecided / asking follow-ups.
• ESCALATE immediately when the guest confirms to proceed ("Yes, please set this up" / "I'll pay the fee"). Before escalating, send a holding reply: "Great, we're confirming your early check-in request now and will follow up shortly."

B — Late Check-Out Guarantee

Trigger Phrases

• "Can I check out late?"
• "What are the late checkout options / fees?"
• "Can I stay in my room until 2 PM?"
• "Is late checkout available?"

LLM Response — What to Send the Guest

"We'd be happy to arrange a guaranteed late check-out for you. Here are the available options:"

Checkout Time	Tue – Fri Departure	Sat – Mon Departure
12:00 PM	$20 + tax	$30 + tax
1:00 PM	$30 + tax	$40 + tax
2:00 PM	$40 + tax	$50 + tax
3:00 PM	$50 + tax	$60 + tax
4:00 PM	$60 + tax	$70 + tax

"To secure your preferred departure time in advance, just let us know which time works best and we'll get that arranged. If you'd prefer not to pay a fee, late checkout is also available based on availability by calling the front desk directly on the morning of departure."

Escalation Decision Rule

• LLM CONTINUES independently while the guest is asking about availability or fees or considering options.
• ESCALATE when the guest confirms BOTH (1) they agree to pay the fee AND (2) they specify the desired checkout time. Example: "Yes, I'd like 1 PM — Friday departure." Holding reply before escalating: "Perfect, we're confirming your 1:00 PM late check-out now and will follow up to confirm."

C — Connecting Rooms

Trigger Phrases

• "Can we have connecting rooms?"
• "Can our rooms be next to each other / on the same floor?"
• "We need rooms that connect — traveling as a family."

LLM Response — What to Send the Guest

"We can guarantee connecting rooms in advance for an additional fee of $25 per room, per night. To confirm this for your stay, please provide the name and confirmation number for each reservation you'd like connected and we'll get this set up for you."

Escalation Decision Rule

• LLM CONTINUES independently while the guest is asking if connecting rooms are available or about the fee/process.
• ESCALATE when the guest confirms ALL of: (1) they agree to the $25/room/night fee, AND (2) they provide names and confirmation numbers for ALL rooms to be connected. Holding reply before escalating: "Thanks! We're coordinating your connecting room request now and will confirm once it's set up."

D — Room Upgrade or Stay Extension

Trigger Phrases

• "Can I get an upgrade?"
• "Is there a better room / renovated room available?"
• "Can I extend my stay by a night or two?"
• "Can I get a strip view / high floor / specific bed type?"
• "I booked Room Assigned Upon Arrival — can I guarantee a bed type?"

LLM Response — What to Send the Guest

"We'd be happy to look into upgrade and extension options for you. To have our hotel team reach out directly with availability and pricing, could you please share the best phone number to reach you?"

Note on Upgrade Information: Always set the expectation that upgrades are subject to availability. Do not confirm inventory or guarantee any specific room type. The human Concierge team handles all actual availability checks and pricing.

Escalation Decision Rule

• LLM CONTINUES independently while the guest is asking about upgrade possibilities, cost, or process.
• ESCALATE when the guest provides their contact phone number. Example: "Sure — my number is 702-555-1234." Holding reply before escalating: "Perfect, thank you. We've shared your number with our hotel team and they will be in touch shortly to discuss options."

RAG Context: Master escalation framework for Flamingo Las Vegas automated guest messaging and post-stay reviews. Defines the core operating principle (the LLM handles routine information and upsell conversations up to — but not including — the moment a guest commits or a sensitive situation arises, then sends a holding reply and generates a human-Concierge escalation email), the required fields for every escalation email, and a quick-reference decision table. Detailed decision rules live in the companion documents: flamingo-las-vegas-hotel-casino-upsell-escalations.md (Section 1), flamingo-las-vegas-hotel-casino-general-escalations.md (Section 2), and flamingo-las-vegas-hotel-casino-review-response-escalations.md (Section 3). Serious guest-reported incidents (injury, theft, health, security, harassment, hygiene, legal) route through the detailed risk-category guides listed below; any guest confirmation or acceptance of a fee or charge routes through the always-escalate fee-confirmation guide (CONFIRM-FEE).

Flamingo 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: flamingo-las-vegas-hotel-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: flamingo-las-vegas-hotel-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: flamingo-las-vegas-hotel-casino-review-response-escalations.md (positive and negative/mixed review handling and escalation triggers).

Detailed Incident-Category Guides

For serious guest-reported incidents, route using the risk-category guides (all are always-escalate):

• flamingo-las-vegas-hotel-casino-safety-injury-escalations.md — Safety & physical harm (SAFETY-INJURY)
• flamingo-las-vegas-hotel-casino-security-theft-escalations.md — Theft & property crime (SECURITY-THEFT)
• flamingo-las-vegas-hotel-casino-health-medical-escalations.md — Health & medical (HEALTH-MEDICAL)
• flamingo-las-vegas-hotel-casino-security-safety-escalations.md — Security & unsafe conditions (SECURITY-SAFETY)
• flamingo-las-vegas-hotel-casino-conduct-harassment-escalations.md — Harassment & conduct (CONDUCT-HR)
• flamingo-las-vegas-hotel-casino-hygiene-hazard-escalations.md — Hygiene & environmental (HYGIENE-HAZARD)
• flamingo-las-vegas-hotel-casino-legal-threat-escalations.md — Legal threats (LEGAL-FLAG)

One additional always-escalate guide covers a guest commitment rather than a harm incident:

• flamingo-las-vegas-hotel-casino-confirm-fee-escalations.md — Fee & charge confirmation (CONFIRM-FEE) — guest accepts/authorizes any fee or surcharge; catch-all backing the Section 1 upsell rows below

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.

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 $25/room/night fee, request names & conf #s	Guest confirms fee + provides all names & conf #s — then escalate
Room Upgrade / Extend Stay (incl. adding a night or a later checkout)	Ask for best contact phone number; do not route to the booking channel	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 (shorten, cancel, date shift, room change, primary-name change — not adding nights or an additional guest name)	Explain 3rd-party policy, direct to booking channel	3rd party cannot process; complex booking changes
Invoice / Folio / Receipt (incl. itemized)	Send the self-service folio response (emailed after checkout; check spam; else caesars.com folio-request link)	Billing dispute / correction / refund; business-invoice format; incidentals hold past timeframe
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 (702-733-3523)	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