RAG Context: Amenity inquiry standardized response templates for Paris Las Vegas — atomic templates for dining, pool, spa, fitness center, casino, sportsbook, Eiffel Tower attractions, and parking.

Amenity Inquiry Standardized Responses for Paris Las Vegas:

• Dining

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.

RAG Context: Escalation guideline for Paris Las Vegas Resort Casino guest messages where the guest (a) requests a reply by email ("can you email me?", "reply to my email", "what's your email?", "I'll send you my email") or (b) sends an email address — including a platform-REDACTED token that looks like an email, e.g. ----@--------.---, ****@*****.***, xxxx@xxxxx.xxx (third-party booking channels such as Expedia / Booking.com auto-mask email addresses in guest messages, so a redacted-email token signals the guest tried to share their email). The automated assistant operates on the booking channel's text-messaging and post-stay review threads and cannot send or receive email, and because the reservation was made through a third-party provider the property has no direct email relationship with the guest — so email communication is not possible. The assistant sends the standard reply stating this (booking made through a third-party provider) and escalates to a human Concierge. Maps to tag EMAIL-CONTACT; part of the master framework in paris-las-vegas-resort-casino-escalations.md. A guest simply asking for the property's general contact info for a routine reason is handled from paris-las-vegas-resort-casino-property-details.md. Always escalate on trigger; do not email the guest and do not echo a full real email address back in a public reply.

Email Contact Requested / Email Address in Message — Escalation