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

Email Contact Requested / Email Address in Message

Guest asks / says:

• "Can you email me the details?" / "Please reply by email."
• "What's your email address?" / "Is there an email I can reach you at?"
• "I'll email you." / "Let me give you my email."
• "Here's my email: ----@--------.---" (platform-redacted)
• "Contact me at ****@**."
• "My email is jane.doe@example.com." (a real address comes through)

Trigger keywords / patterns (non-exhaustive): email me, by email, via email, reply to my email, send it to my email, what's your email, your email address, I'll email you, here's my email, contact me at — plus any email-shaped token, redacted or real: <mask>@<mask>.<mask> where each <mask> is a run of repeated masking characters (-, *, x / X, #, •) — e.g. ----@--------.---, ****@*****.***, xxxx@xxxxx.xxx — or a real address local@domain.tld.

Disambiguation: This tag is for a guest who wants to communicate by email or who supplies an email address (real or platform-redacted). A guest asking whether their folio / receipt / invoice will be emailed after checkout is a routine billing-info request — handle via the invoice / folio flow, do not tag here. Do not echo a full real email address back in a public reply — treat it as private contact information.

TAG as email-contact

Respond with

State that email communication is not possible because the booking was made through a third-party provider, and offer to continue helping on the current channel. Do not send or promise an email, and do not echo a real email address back. Standard response:

"Thank you for reaching out! Unfortunately, we're unable to correspond by email for this reservation, as your booking was made through a third-party provider. We're glad to assist you right here through this channel — please share anything you need and we'll be happy to help."

Before escalating

Do not email the guest and do not promise email follow-up. Capture in the escalation record: the guest's exact wording, whether they requested email contact and/or supplied an email (note if it arrived redacted vs. a real address — do not transcribe a full real address into a public field), the reason they want email, the inbound channel, and full reservation details.

Do not claim (unless actually verified and a real escalation has been created and routed)

• That an email has been sent, received, or scheduled
• That the team will follow up by email
• That the matter will be handled / resolved by email
• That the guest's email has been saved to their reservation

Escalate when:

• Always. Any request to communicate by email, any request for the property's email, or any email-shaped token (redacted or real) in a guest message is an immediate escalation — the assistant cannot use email and the third-party booking precludes direct email contact, so a human Concierge should be aware and handle any contact details.
• If the email request accompanies a sensitive issue (billing dispute, safety, complaint, legal), escalate under both this tag and the relevant Section 2 General Escalation Rule, and flag the higher-severity tier.
• If the request is tied to a booking controlled by a 3rd-party channel (Expedia, Booking.com) — which is the norm — still escalate and capture the booking channel.
• Tag the conversation: [EMAIL-CONTACT] + [TIER LEVEL] + [CHANNEL: Expedia / Booking.com] and route to the Paris Concierge queue.

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

Standard response — send this for any folio / invoice / receipt request, including itemized: "Your invoice will be emailed to you automatically after checkout. If you have not received your invoice, please check your spam or junk folders. If you still cannot find it, please visit https://www.caesars.com/help-and-support/hotel-folio-request." This is self-service — do not escalate a folio / itemized request. Debit card holds may take several business days to release. For any billing change or dispute, the front office team must be involved.

✓ LLM Responds Directly	⚠ Escalate to Human Concierge
Send the standard folio response above for any folio / invoice / receipt request, including an itemized folio, bill, or receipt (caesars.com self-service link; no escalation). Note that debit card holds take several business days to release.	Guest disputes a charge or requests a correction. Guest requests a refund. Business invoice format required (a company-addressed invoice the self-service folio cannot produce). Incidentals hold not released after the expected timeframe.

H — Room Issues & Housekeeping

Trigger Phrases

• "My room is dirty / has a bad smell."
• "The AC / heater / TV / lights aren't working."
• "There's something broken in my room."
• "We need more towels, linens, pillows, or amenities."
• "There are bugs / the room is unacceptable."

Always direct to front desk first: Ask the guest to contact the front desk directly — by calling Guest Services or using the Laurel in-room text feature — before escalating. Escalate only if the front desk was already contacted and the issue remains unresolved.

✓ LLM Responds Directly	⚠ Escalate to Human Concierge
Apologize sincerely and acknowledge the inconvenience. Gather full details of the issue. Direct guest to front desk or Laurel in-room text service. Reassure the guest that the team will assist.	Front desk already contacted and issue is unresolved. Issue impacts guest safety or health. Guest requests a room move, repair, or compensation. Guest is in-stay with an urgent problem needing immediate attention.

I — Maintenance Requests

Trigger Phrases

• "Can someone fix the AC / heater?"
• "The sink / shower / toilet isn't working."
• "The safe / TV / WiFi isn't working."
• "There's a maintenance issue in my room."

Always direct to front desk first: Guests should call Guest Services or use Laurel in-room texting for immediate Engineer dispatch. Escalate only if the front desk was unresponsive or the issue persists.

✓ LLM Responds Directly	⚠ Escalate to Human Concierge
Acknowledge the issue and express regret. Direct guest to front desk (call) or Laurel text to request Engineer dispatch. Collect issue details for documentation.	Repair is needed and front desk has not responded. Guest already contacted front desk and issue remains unresolved. Issue is impacting guest safety.

J — Noise, Neighbor & Safety Complaints

Trigger Phrases

• "The room next door is too loud / there's a party."
• "I don't feel safe."
• "There's suspicious activity on my floor."
• "I had an accident / there was an incident in my room."