Guest message
Received Β· Jun 17, 2026, 8:35 p.m.
How do I request it ?
Expedia Β· Message
Received Β· Jun 17, 2026, 8:35 p.m.
How do I request it ?
Sent Β· Jun 17, 2026, 8:36 p.m.
Thank you for reaching out. We appreciate your inquiry about parking fees for blue badge holders.
Source: 1
Score Β· 53.26%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 inparis-las-vegas-resort-casino-escalations.md. A guest simply asking for the property's general contact info for a routine reason is handled fromparis-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.
Source: 2
Score Β· 50.37%RAG Context: Room request standardized response templates for Paris Las Vegas β quiet room requests, rooms close together, guaranteed connecting rooms ($20/room/night, confirm names and confirmation numbers), adjoining room requests ($20/room/night, confirm second reservation ID), bed type/bedding requests (bed type not guaranteed; upgrades available pre-arrival), Pet Room requests ($75/night, dogs only), view option requests, special occasion and honeymoon requests, crib and rollaway requests ($35/day), mini-fridge requests (by tower β Bordeaux standard, Versailles on request), coffee maker/microwave requests (suites only / not available), extra towels-blankets-pillows in advance, generic room requests, and room changes after check-in.
Thank you for reaching out! We've noted your request for a quiet room and will do our best to accommodate it based on availability at the time of your arrival. While we cannot guarantee specific room assignments in advance, please rest assured that we will make every effort to fulfill your preference.
Source: 3
Score Β· 50.32%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 |
This response was not escalated. Was that decision correct?
Marked correct
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.