Guest message
Received Β· Jun 16, 2026, 12:56 p.m.
Please check and do the refund formalities asap
Expedia Β· Message
Received Β· Jun 16, 2026, 12:56 p.m.
Please check and do the refund formalities asap
Sent Β· Jun 16, 2026, 12:56 p.m.
Thank you for reaching out to us about the refund issue. We apologize for any inconvenience this has caused and will look into this matter further. A member of our team will follow up with you shortly to assist with your refund inquiry.
Source: 1
Score Β· 50.91%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 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 |
Source: 2
Score Β· 49.60%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 inparis-las-vegas-resort-casino-escalations.md.
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.
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.
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.
Source: 3
Score Β· 47.46%Trigger Phrases
| 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. |
Trigger Phrases
| 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. |
Trigger Phrases
| 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. |
Trigger Phrases
This response was 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.