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

✓ LLM Responds Directly	⚠ Escalate to Human Concierge
Collect the additional guest's name. Explain that a valid government-issued photo ID and the card used to book are required at check-in. Note the request with full reservation details.	Guest wants to change the PRIMARY guest name. Guest wants a guarantee that another person can check in without the booker present. Any billing authorization, third-party payment, or identity mismatch.

F — Stay Modifications & Cancellations

Trigger Phrases

• "Can I change my dates?" (a same-length date shift; to ADD nights or push checkout later, see the Stay Extension note below)
• "Can I shorten my stay?"
• "I want to cancel — can I get a refund?"
• "Can I combine two reservations?"
• "Can I change my room type?"

Adding nights is NOT a modification — do not send the guest to Expedia. If the guest wants to ADD nights, stay longer, or move their checkout / departure date later, treat it as a Stay Extension upsell — ask for the best phone number and escalate when supplied. The third-party "contact Expedia" rule below applies only to shortening, cancelling, date shifts, or room-type changes.

Adding a guest's NAME is NOT a modification — handle it directly, do not send to Expedia. If the guest wants to add an additional guest's name for check-in (even on a third-party booking), follow item E — collect the additional guest's full name and explain that a government-issued photo ID and the card used to book are required at check-in (names are typically added up to 24 hours before arrival). Only a change to the PRIMARY guest name, or a cancellation, goes through the booking channel.

Before escalating — always tell the guest: If the reservation was made through a 3rd-party booking channel (Expedia, Booking.com), the guest must contact that platform's customer service directly to modify or cancel. The LLM cannot make these changes.

✓ LLM Responds Directly	⚠ Escalate to Human Concierge
Explain the modification policy based on booking channel (the guest must contact the third party to modify). Direct guest to the appropriate channel (Expedia, Booking.com, or Caesars direct). Adding an additional guest's name for check-in is handled directly — see item E.	3rd-party booking cannot process the modification. The PRIMARY guest name, dates, room type, or confirmation structure must change and the channel cannot assist. Complex booking complications requiring hotel intervention.

G — Invoice / Folio / Receipt Requests

Trigger Phrases

• "Can you send me my invoice / receipt / folio?"
• "I need an itemized folio / itemized bill / itemized receipt."
• "I haven't received my incidentals deposit back."
• "I was overcharged / there's a charge I don't recognize."

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 $20/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 / front desk	Security/front desk intervention needed; unresolved
Billing Inquiry / 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

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