Guest message
Received Β· Jun 17, 2026, 10:20 p.m.
Hola buenas tardes estuve hospedada en este hotel pero se han aplicado cargos a mi targeta en los cuales no estoy de acuerdo
Expedia Β· Message
Received Β· Jun 17, 2026, 10:20 p.m.
Hola buenas tardes estuve hospedada en este hotel pero se han aplicado cargos a mi targeta en los cuales no estoy de acuerdo
Sent Β· Jun 17, 2026, 10:20 p.m.
Thank you for reaching out to us about the charges on your card. We apologize for any inconvenience this has caused. A member of our team will be in touch with you to discuss this further and assist you in resolving the issue.
Source: 1
Score Β· 50.27%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 |
Source: 2
Score Β· 48.99%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 Β· 48.51%Trigger Phrases
| Security Team β available 24/7: Guests with immediate safety concerns should be directed to the Security Team, reachable from the in-room phone (Security or Guest Services button) or by calling the property at (702) 946-7000. The property has EMTs on staff and can contact EMS for transport if needed. All safety, medical, and injury incidents must also be escalated to the hotel team regardless of whether the guest has already contacted Security. |
|---|
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Acknowledge the seriousness of the concern immediately. Direct guest to the front desk or Security (via the in-room phone or (702) 946-7000) for immediate help. Express empathy and reassure the guest. | Any safety, medical, or injury incident β always escalate. Noise/security issue where front desk intervention is needed. Front desk or Security unreachable or issue unresolved. Any message mentioning injury, theft, or property damage. |
Trigger Phrases
| Rule β always escalate billing disputes: The LLM does not have authority to adjust charges, issue refunds, or confirm billing corrections. Any billing-related complaint must be escalated to the hotel team. |
|---|
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Acknowledge the concern professionally. Gather relevant billing details and document them. Remind the guest that debit holds take several business days to release. | Any billing correction, dispute, or refund β always escalate. Unrecognized charges or request to remove a fee. Incidentals deposit not returned within the expected timeframe. |
Trigger Phrases
| β LLM Responds Directly | β Escalate to Human Concierge |
|---|---|
| Empathize sincerely with the guest's experience. Apologize without assigning fault or making promises. Document the issue thoroughly. | Compensation of any kind is requested. Multiple service failures are described. Guest is emotionally escalating or expressing distress. Guest threatens to leave a public review about the issue. |
This response was escalated. Was that decision correct?
Not yet assessed
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.